Qdrant
1. Overview
The Qdrant add-on deploys an instance of Qdrant, a high-performance vector database. It stores embeddings (vectors) and runs similarity/semantic search over them.
Use it when your product needs vector search — retrieval for RAG (Retrieval-Augmented Generation), recommendations, deduplication, or any case that involves indexing and querying vectors. For relational data use PostgreSQL; for in-memory key/value, Cache (Valkey).
Catalog tags: Database, Vector, AI, Qdrant.
2. Prerequisites
- A squad and an environment already selected on the Add-ons screen.
3. Deploy step-by-step
The Qdrant deploy wizard has 2 steps:
Step 1 — General
| Field | Required | Description |
|---|---|---|
| Add-on Name | Yes | Add-on name within the environment. Lowercase letters, numbers and hyphens only. Example: my-qdrant. |
| Admin Public | No | When on, the native Qdrant dashboard is publicly reachable. Off by default (access restricted by the platform). |
The API key is generated automatically by the platform at creation time, stored encrypted and injected into the instance — you don't set it during deploy.
Step 2 — Resources
Defines the compute resources allocated to the instance.
| Field | Default | Suggestion/Maximum |
|---|---|---|
| Memory Limit | 1Gi | 2Gi |
| CPU Limit | 500m | 2000m |
| Storage Size | 10Gi | 20Gi |
Clicking Deploy Add-on starts the deployment. The add-on then appears on the environment's My Add-ons tab.
4. After Deploy
The add-on panel on the platform offers a reduced set of everyday actions, organized in tabs:
- Overview — instance health (aggregate collection status), number of collections, points, vectors and indexed vectors.
- Connect — reveal/copy the API key, export the connection to a platform secret, and rotate the key (see below).
- Collections — list, create (a guided wizard: vectors, distance, payload indexes), inspect (config + points) and delete collections.
- Console — send raw REST requests to the instance for anything the panel doesn't cover.
- Settings — resources (memory/CPU/storage — storage only grows) and the Private/Public visibility of the native dashboard.
Beyond the reduced panel, the native Qdrant dashboard is available at the add-on's adminUrl (served under /dashboard), with the full feature set. When Admin Public is off (default), access is gated behind the platform session.
Connecting a flow to Qdrant
Flows connect to Qdrant over gRPC, using the Qdrant connector. Connection credentials should live in secrets:
- On the Connect tab, use Export to secret — the platform writes
host,port(gRPC),apiKeyanduseTlsinto a secret (new or existing). - In the flow connector, reference those properties as
{$.env.<secret>.<prop>}.
Export is a convenience: you can also configure the connector manually using the add-on's internalUrl plus the API key.
5. FAQ
How do I access the Qdrant API key?
On the panel's Connect tab, use Reveal to show and copy the current key, or Export to secret to write it (along with host/port) into a platform secret your flows reference.
What happens when I rotate the API key?
The platform generates a new key and the instance switches to it; the old key stops working immediately. Any secret you already exported still holds the old key — re-export (or update) that secret so your flows keep connecting.
Does the add-on back up the data?
Backups (snapshots) are not managed by the add-on yet.