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.
Branching, on request
Database branching is live on 9 engines today, and the same copy-on-write mechanism spans the whole fleet. Want it on Qdrant? Reach out and we will look at switching it on for your account.
Request branchingTry Qdrant free for 7 days
Qdrant runs always-on from your Pro pool, so it lives on the Pro plan. Start a 7-day Pro trial to spin one up: a card is required, you are charged $0, and you can cancel before it converts to $15/mo. One trial per account.
Start the Pro trialWhat 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
Pin a database to your always-on pool to prevent 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.
Native HTTPS endpoint
Engines whose own wire protocol speaks HTTPS. Every database, including this one, is also queryable over the platform's HTTPS query API and web console.
Serverless driver
Drop-in HTTP driver for edge runtimes (Upstash REST, PlanetScale, or the engine-native client).
IP whitelisting
Restrict access to specific IPs or CIDR ranges.
Automatic backups
Scheduled dumps and volume snapshots with one-click restore on paid plans. Free tier includes a manual backup slot.
Why Layerbase
Predictable pricing, no cloud setup
Qdrant on Layerbase Cloud is priced the same way as every other engine: a flat monthly plan with nothing metered behind it.
A fixed monthly price
Plans are flat: Free at $0, then $5/mo Solo and $15/mo Pro. No per-hour compute meter, no per-database line items, and no bill that changes shape when your traffic does.
No bandwidth charges
Reads and writes are not metered. There are no ingress or egress fees, so moving data in and out of your database never adds to the bill.
No cloud account to wire up
You do not need an AWS, GCP, or Azure account. Sign up, create a database, and connect. Layerbase runs the infrastructure, so there is no cloud provider to configure or pay separately.
Side by side
Hosted Qdrant, compared
| Provider | Free tier | Billing |
|---|---|---|
| Qdrant Cloud | 1 GB free cluster | Paid clusters are usage-metered hourly |
| Layerbase | Qdrant is a Performance engine on Pro | $15/mo flat as 1 of 10 databases, always-on from your pool. No meters. |
Qdrant Cloud
- Free tier
- 1 GB free cluster
- Billing
- Paid clusters are usage-metered hourly
Layerbase
- Free tier
- Qdrant is a Performance engine on Pro
- Billing
- $15/mo flat as 1 of 10 databases, always-on from your pool. No meters.
Competitor facts as of July 2026, from public pricing pages.
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"
More on Qdrant
All articles- August 6, 2026
Qdrant 1.18 is on Layerbase, and the Headline is Quantization
Qdrant 1.18 is the new default line on Layerbase. Here is what a vector database is actually doing, why quantization decides what your index costs to run, and what landed between 1.16 and 1.18.
Read - June 20, 2026
Run Postgres, Valkey, and Qdrant in one Lovable app
A serious Lovable app usually needs more than one database: durable state, a cache, and vector search. Here is how to wire all three in, the correct way, from a browser SPA that has no server of its own.
Read - June 14, 2026
Branching with any database
Neon branches Postgres. PlanetScale branches MySQL. Layerbase branches all of them, because branching happens at the filesystem, not inside the engine. Here is how it works.
Read - May 25, 2026
Add vector search to a Lovable app with Qdrant
AI-powered Lovable apps eventually need vector storage for RAG, semantic search, or recommendations. Here is the working version with Qdrant on Layerbase Cloud.
Read - March 12, 2026
Full-Text Search vs Vector Search
Learn when to use full-text search, vector search, or both by running the same queries against Meilisearch and Qdrant side by side.
Read
FAQ
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.