Deploy and Host Milvus REST on Railway

Milvus is an open-source vector database for similarity search, embeddings, retrieval-augmented generation, recommendation, and other high-dimensional workloads.

About Hosting Milvus

This template deploys Milvus Standalone v2.6.21 with persistent etcd v3.6.14, MinIO RELEASE.2025-09-07T16-13-09Z, and a Caddy 2.11.4 REST proxy. Only the REST proxy receives a public domain; Milvus, etcd, and MinIO communicate through Railway private networking.

Milvus authentication is enabled with a generated root password. Milvus data, etcd metadata, and MinIO objects each use a separate persistent volume, and generated MinIO credentials are passed through Railway references.

Common Use Cases

Store and search embedding vectors through the Milvus REST v2 API
Build semantic search and recommendation services
Run ANN similarity queries for images, text, or multimodal data
Evaluate a protected standalone Milvus deployment without Kubernetes

Dependencies for Milvus Hosting

Milvus Standalone v2.6.21
etcd v3.6.14
MinIO RELEASE.2025-09-07T16-13-09Z
Caddy 2.11.4 proxy image v2.11.4-r3
Persistent volumes for all three stateful services
Sufficient memory for Milvus Standalone; start with at least 4 GB for nontrivial workloads

Deployment Dependencies

Implementation Details

Send HTTPS requests to the generated milvus-rest-proxy domain. Read COMMON_SECURITY_DEFAULTROOTPASSWORD from the standalone service and authenticate with the REST header Authorization: Bearer root:YOUR_PASSWORD.

For example, list collections with POST /v2/vectordb/collections/list and a JSON body containing {"dbName":"default"}.

Railway public HTTP domains currently do not preserve native gRPC end to end to the container. This template therefore supports the official REST v2 API, not native gRPC SDK connections such as PyMilvus. Do not add an unauthenticated public TCP proxy as a workaround; it would expose database traffic without Railway-managed TLS.

Why Deploy Milvus on Railway?

Railway provides persistent volumes, private service discovery, HTTPS, generated credentials, health checks, and centralized logs for a compact authenticated Milvus REST topology.