Serverless Qdrant
Production-grade vector search with a real REST endpoint. Web search console, the same Qdrant client libraries, cloud or self-host.
/collections/products/points/searchBody
Response200 OK · 6ms
Where to run it
Cloud, desktop, or self-host
One database, three places it can live. Pick the speed you want and move between them when you outgrow it.
What you get
Production features, free tier included
Every Qdrant database ships with the same primitives: TLS, web console, hibernation, and a real dashboard. No tiered features hidden behind a sales call.
Web IDE
Query console in the dashboard, no extra client to install.
TLS by default
All connections encrypted. No setup required.
Always-on connections
Optional keep-alive add-on prevents hibernation.
Scale to zero
Hibernates when idle. Wakes on the next connection.
Connection pooling
Pooled endpoint for serverless and edge workloads.
Direct connections
Bypass the pooler for migrations and replication.
HTTPS access
HTTP-native engines reachable over port 443.
Serverless driver
Upstash REST or PlanetScale serverless drivers supported.
IP whitelisting
Restrict access to specific IPs or CIDR ranges.
Automatic backups
Scheduled point-in-time backups with one-click restore.
Quick start
Connect with any Qdrant client
Vector search for RAG and semantic search, embedding-backed recommendations, multimodal retrieval, and apps that need real Qdrant features (payload filtering, hybrid search, recommendations).
- Stand up a Qdrant for a RAG prototype without managing a node
- Move from local Qdrant Docker to a hosted endpoint without changing client code
- Multi-tenant vector search where each tenant gets isolated collections
- HTTPS-only access from serverless or edge runtimes
- Self-host on your own hardware with SpinDB when latency requires it
curl -H "api-key: YOUR_TOKEN" "https://your-host.cloud.layerbase.dev/collections"Questions
Common Qdrant questions
REST or gRPC?+
REST works out of the box on every plan. gRPC support is in active rollout (see status updates); REST covers the same operations with comparable latency in most cases.
Will my Qdrant Python client work?+
Yes. The official qdrant-client (Python, Node, Go, Rust) connects to the published HTTPS endpoint with the dashboard-provided API key.
How do I manage collections?+
Through the dashboard search console or via your client library directly. The console is a thin layer on the REST API and shows the same shape your code will see.
IP whitelisting?+
Yes. The firewall panel in the dashboard accepts IPs and CIDR ranges and locks the endpoint to those sources.
Can I run Qdrant locally?+
Yes. SpinDB and Layerbase Desktop both run Qdrant with the same one-command install and the same dashboard UI.