Qdrant Cloud
qdrant.tech · Databases and KV · 1 record · JSON
Qdrant Cloud Databases and KV
★ qualifiesemailno cardDper-object-cap
| Free tier | free tier cluster with 1 GB RAM and 4 GB disk, no high availability, one cluster unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Per-object cap | 4 GB disk per cluster |
| Retention | no deletion clock and no exhaustion behaviour is published; the FAQ says only that if data growth exceeds the free tier you 'can easily upgrade'. Nothing states what happens to a cluster that reaches 1 GB of RAM |
| Egress | not published on the pricing page; recorded as a gap |
| Identity | email email or GitHub signup; no card on Free |
| Limits | |
| Binding | per-object-cap |
| Interface | rest, cli a REST API and gRPC; Python, JS and Rust clients |
| Tooling | the qdrant-client libraries over gRPC or REST |
| Composes with | the largest free vector storage by disk, and the closest thing to a self-managed index without a host |
| Reliability | no high availability on the free tier, so the single node is the availability |
| Notes | 4 GB of disk at 768 dimensions and 4 bytes per component is roughly 1.4 million vectors before index overhead; the census's ~1M estimate is in the right order but was arithmetic rather than a measurement. What happens at 1 GB of RAM is not published: the page offers an upgrade and says nothing about a refusal, a throttle or a deletion. That is a documented absence and it is recorded as one rather than read as headroom. |
| Evidence rung | documented the pricing FAQ was read today; the numbers are in the page's own answers. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | qdrant.tech/pricing/ | 'The free tier includes 1GB RAM and 4GB disk storage'; the free tier is 'limited to 1GB RAM and 4GB disk without high availability' |
Unknown or withheld values (1)
$.egress.meteredegress-unknown