Deploy Qdrant

Deploy and Host Qdrant on Railway

Qdrant is a high-performance vector database built for semantic search, embeddings, recommendation systems, Retrieval-Augmented Generation (RAG), and other AI workloads. It provides REST and gRPC APIs, persistent vector storage, filtering, authentication controls, and a built-in Web Dashboard for managing collections and exploring data.

About Hosting Qdrant

Hosting Qdrant on Railway gives you a self-hosted vector database that can run alongside AI agents, backend services, embedding pipelines, and RAG applications.

This template uses the official Qdrant Docker image and stores vector data in persistent Railway storage. The REST API and Web Dashboard are available through port 6333, while gRPC is available on port 6334 for applications that prefer a higher-performance protocol.

The template also enables API-key authentication by default, including separate administrator and read-only credentials. Qdrant supports JWT-based granular access control when more advanced collection-level permissions are required.

Common Use Cases

• Semantic search and similarity search
• Retrieval-Augmented Generation (RAG)
• Embedding storage and retrieval
• Recommendation systems
• AI agents with long-term or searchable memory
• Document and knowledge-base search
• Image, product, or content similarity applications

Dependencies for Qdrant Hosting

• Official qdrant/qdrant:latest Docker image
• Persistent Railway volume mounted at /qdrant/storage

Implementation Details

Qdrant stores collections, vectors, indexes, and related database state under:

/qdrant/storage

The Railway service exposes:

6333 - REST API and Web Dashboard
6334 - gRPC API

The built-in dashboard is available after deployment at:

https://your-qdrant.up.railway.app/dashboard

Qdrant officially exposes its REST API and Web UI on 6333, with gRPC on 6334.

API Authentication

This template generates two credentials:

• Admin API Key — full access to collections and operations
• Read-Only API Key — allows queries and read operations while preventing modifications

Qdrant supports both credentials simultaneously, allowing applications that only perform search operations to use a lower-privilege key.

Authenticated requests use the api-key header:

curl \
  -H "api-key: YOUR_API_KEY" \
  "https://your-qdrant.up.railway.app/collections"

JWT and Granular Access Control

JWT-based RBAC is disabled by default in this template to keep the initial deployment simple.

Qdrant can optionally enable JWT-based granular access control for scenarios such as:

• Restricting users to specific collections
• Providing read-only access to selected collections
• Providing read-write access to selected collections
• Multi-tenant applications

JWT tokens are signed using the configured administrator API key and can contain collection-level access rules.

Qdrant vs Similar Vector Databases

Qdrant is particularly attractive when you want a relatively lightweight self-hosted vector database with REST and gRPC access, persistent storage, a built-in dashboard, and straightforward API-key security without deploying a larger supporting stack. Qdrant documents native admin, read-only, and JWT-based granular API access controls for self-hosted deployments.

Weaviate supports self-hosting, REST and gRPC APIs, authentication, and more extensive module-based integrations, while its management console is a separate interface rather than the embedded database dashboard model used by Qdrant.

Milvus also supports REST and gRPC and includes a built-in Web UI in recent versions, but its production architecture can involve more infrastructure components than a basic single-node Qdrant deployment.

Pinecone provides REST and gRPC access but is primarily delivered as a managed cloud vector database rather than a self-hosted database that you deploy into your own Railway project.

Getting Started After Deployment

1. Deploy the Qdrant template.
2. Open the Qdrant service in Railway.
3. Generate a public domain for port 6333.
4. Open /dashboard to access the Qdrant Web UI.
5. Retrieve the generated administrator API key from Railway variables.
6. Create your first collection.
7. Connect your application, AI agent, or RAG pipeline using the REST API or gRPC interface.
8. Use the read-only API key for services that only need search access.

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.