---
title: "Deploy self-hosted-qdrant-example"
description: "Deploy a private Qdrant vector database with a sample app on Railway"
category: "AI/ML"
url: https://railway.com/deploy/self-hosted-qdrant-example
---

# Deploy self-hosted-qdrant-example

Deploy a private Qdrant vector database with a sample app on Railway

**[Deploy self-hosted-qdrant-example on Railway](https://railway.com/template/self-hosted-qdrant-example)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/self-hosted-qdrant-example/manifest.json

- **Creator:** William Raphaelson's Projects
- **Category:** AI/ML
- **Total deploys:** 1

## Template content

### qdrant

- **Image:** qdrant/qdrant:v1.20.1
- **Health check:** /readyz

### qdrant-demo-app

- **Source:** https://github.com/WillRaphaelson/railway-vector-search-qdrant
- **Start command:** `node server.mjs`
- **Health check:** /health
- **Public domain:** Yes

## Documentation

# Deploy and Host a Private Qdrant Vector Database and Demo App on Railway

## About Hosting Qdrant and the Demo App

This template deploys one Qdrant service, a Railway Volume mounted at `/qdrant/storage`, and a small Node.js app that can seed and query a sample four-dimensional collection. The app reaches Qdrant through Railway private networking. Qdrant is not exposed publicly. The demo app receives a public HTTPS endpoint so you can use its seed and search controls in a browser.

## Why Deploy Qdrant and the Demo App on Railway?

Keep the application and its vector database in one Railway project environment. The volume persists Qdrant files through restarts and deployments; the internal service reference keeps database traffic on the private network. The demo app makes the connection, seed, and query path easy to inspect.

## Common Use Cases

- Try a private Qdrant service beside a small application.
- See how persistent database files differ from the app container's temporary filesystem.
- Test application-level integration before choosing an embedding model and production topology.

## Dependencies for Qdrant Hosting

- Qdrant `v1.20.1`, using the official `qdrant/qdrant` image.
- A Railway Volume mounted at `/qdrant/storage`.
- A Railway API service built from the template repository.
- One generated Qdrant API key shared with the application through a Railway service reference.

### Deployment Dependencies

- Railway creates a new project and environment for the deployment.
- The app and Qdrant services must remain in the same environment for their private network reference to resolve.
- The app's public URL is for the sample interface. Qdrant stays private.
- This is a single-node demonstration. Volume-backed services cannot use Railway replicas, and Qdrant redeploys have a short interruption.

## Use the Demo

Open the app's generated HTTPS URL, click **Seed sample data**, then click **Search sample data**. The example uses fixed vectors and does not call an embedding model.

## Source and Documentation

- Source repository: https://github.com/WillRaphaelson/railway-vector-search-qdrant
- Qdrant installation: https://qdrant.tech/documentation/install/
- Railway private networking: https://docs.railway.com/networking/private-networking
- Railway volumes: https://docs.railway.com/volumes


## Similar templates

- [Chat Chat](https://railway.com/deploy/-WWW5r) — Chat Chat, your own unified chat and search to AI platform.
- [Weaviate](https://railway.com/deploy/weaviate-1) — Vector database with hybrid search and an API key-protected API
- [Möbius Personal AI OS](https://railway.com/deploy/mobius-v01-personal-ai-os) — Self-hosted AI agent that builds and runs apps for you, with memory.

Open this page in a browser: https://railway.com/deploy/self-hosted-qdrant-example
