Self-host Qdrant on a VPS
A vector similarity search engine for storing, searching, and managing embeddings.
levelrail-cli templates deploy qdrant --name my-qdrantSpecification
- Status
- Listed
- Category
- Database Tools
- Services
- qdrant
- Ports
- 6333
- Volumes
- 1
- Memory
- about 512 MiB
- arm64
- image published
- amd64
- image published
- Settings to fill in
- none
- License
- Permissive license, Apache-2.0
About Qdrant
A vector similarity search engine for storing, searching, and managing embeddings. Runs as a single container from the qdrant image, listening on port 6333; data is kept in named volumes.
What it deploys
Qdrant runs as one service in a single Compose app, listening on port 6333, with 1 named volume mount.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| qdrant | qdrant/qdrant | v1.12.4 | 6333 | qdrant_data -> /qdrant/storage |
Before you install
- CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
- Host ports. It publishes port 6333 directly on the host, so open them in the VPS firewall only if you want that.
Settings and environment
You do not have to fill in anything. 1 secret is generated at deploy and stored encrypted. Values are never shown here.
| Service | Variable | Value |
|---|---|---|
| qdrant | QDRANT__SERVICE__API_KEY | Generated at deploy |
Install Qdrant on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get qdrant -
Deploy it
This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.
levelrail-cli templates deploy qdrant --name my-qdrant
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Qdrant.
Docs and upstream
More in Database Tools
- QuestDBA fast time series database with SQL, a web console, the PostgreSQL wire protocol on 8812 and InfluxDB line protocol ingestion on 9009. The console and the PostgreSQL port share one generated password. Only the console is offered a domain.
- PostgreSQL with pgwebA PostgreSQL 17 server paired with the pgweb browser console, already wired together. The database is not published on the host, so other services in this project reach it at db:5432. pgweb opens straight into the database with the generated credentials, so keep its address private.
- RedisThe Redis in-memory data store on the BSD licensed 7.2 line, with append-only persistence and a generated password. It is not published on the host, so reach it from other services in this project at redis:6379.
- PostgreSQLThe PostgreSQL relational database server on the official Alpine image, with a persistent volume and a generated password. It is not published on the host, so reach it from other services in this project at postgres:5432.
- Redis CommanderA web interface to browse and edit Redis keys. It comes with its own Redis service, and both the Redis password and the web login password are generated for you and shown in the deployment variables.
- Redis InsightA GUI for exploring keys, running commands, and profiling workloads on any Redis-compatible server.