Deploy Qdrant
Qdrant vector database with API key, persistent volume and Web UI
Just deployed
/qdrant/data
Deploy and Host Qdrant on Railway
Qdrant is an open-source vector database and similarity search engine written in Rust. It stores embeddings with JSON payloads and finds the nearest neighbours fast, with filtering, hybrid dense and sparse search, and quantization. Developers use it as the retrieval layer for RAG, semantic search and recommendations, through a REST or gRPC API.
About Hosting Qdrant
Hosting Qdrant means running one stateful server that keeps its collections on disk, so the data directory needs persistent storage that survives restarts and redeploys. The HTTP API and its built-in Web UI must be protected with an API key before they are exposed to the internet, and the server needs enough memory for the vectors you load. This template builds the official Qdrant image (pinned by version and digest) from a GitHub repo, puts storage and snapshots on a Railway volume, generates a 48-character API key, serves the REST API and Web UI on a public HTTPS domain, and checks /readyz before traffic switches over.
Common Use Cases
- Retrieval-augmented generation (RAG): store document embeddings and fetch relevant context for an LLM
- Semantic and hybrid search over products, documentation or support tickets
- Recommendations, deduplication and similarity matching on text, image or audio embeddings
Dependencies for Qdrant Hosting
- Qdrant v1.20.1, the official
qdrant/qdrantimage - A Railway volume for collections and snapshots
Deployment Dependencies
- Qdrant documentation: https://qdrant.tech/documentation/
- Qdrant releases: https://github.com/qdrant/qdrant/releases
- Template source and changelog: https://github.com/aalfath/qdrant-railway-template
Implementation Details
- The API key is in the service variable
QDRANT__SERVICE__API_KEY. Send it as theapi-keyheader (orAuthorization: Bearer) on every request. Openhttps://YOUR-DOMAIN/dashboardand paste the key to use the Web UI. - Other Railway services connect over the private network:
QDRANT_URL=http://${{Qdrant.RAILWAY_PRIVATE_DOMAIN}}:6333andQDRANT_API_KEY=${{Qdrant.QDRANT__SERVICE__API_KEY}}. gRPC is on port 6334 on the same private host. - Collections live in
/qdrant/data/storageand snapshots in/qdrant/data/snapshots, both on the volume. - Any other Qdrant setting can be added as a
QDRANT__SECTION__KEYvariable, for exampleQDRANT__SERVICE__READ_ONLY_API_KEYorQDRANT__TELEMETRY_DISABLED=true. - Updates: a new Qdrant version in the template repo shows up as an "update available" notice in your project. Take a snapshot first, and upgrade one minor version at a time.
Why Deploy Qdrant on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Qdrant on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content

