Which Qdrant Deployment Do I Need?
Start with what you need: managed ops or full control? Network latency acceptable or not? Production or prototyping? The answer narrows to one of four options.
Getting Started or Prototyping
Use when: building a prototype, running tests, CI/CD pipelines, or learning Qdrant.
- Use local mode (Python only): zero-dependency, in-memory or disk-persisted, no server needed Local mode
- Local mode data format is NOT compatible with server. Do not use for production or benchmarking.
- For a real server locally, use Docker Quick start
Going to Production (Self-Hosted)
Use when: you need full control over infrastructure, data residency, or custom configuration.
- Docker is the default deployment. Full Qdrant Open Source feature set, minimal setup. Quick start
- You own operations: upgrades, backups, scaling, monitoring
- Must set up distributed mode manually for multi-node clusters Distributed deployment
- Consider Hybrid Cloud if you want Qdrant Cloud management on your infrastructure Hybrid Cloud
Going to Production (Zero-Ops)
Use when: you want managed infrastructure with zero-downtime updates, automatic backups, and resharding without operating clusters yourself.
- Qdrant Cloud handles upgrades, scaling, backups, and monitoring Qdrant Cloud
- Supports multi-version upgrades automatically
- Provides features not available in self-hosted:
/sys_metrics, managed resharding, pre-configured alerts
Need Lowest Possible Latency
Use when: network round-trip to a server is unacceptable. Edge devices, in-process search, or latency-critical applications.
- Qdrant EDGE: in-process bindings to Qdrant shard-level functions, no network overhead Qdrant EDGE
- Same data format as server. Can sync with server via shard snapshots.
- Single-node feature set only. No distributed mode.
- Chose EDGE and want to build on it? See the
qdrant-edge skill (BM25, snapshot sync, app-side fusion).
What NOT to Do
- Use local mode for production or benchmarking (not optimized, incompatible data format)
- Self-host without monitoring and backup strategy (you will lose data or miss outages)
- Choose EDGE when you need distributed search (single-node only)
- Pick Hybrid Cloud unless you have data residency requirements (unnecessary Kubernetes complexity when Qdrant Cloud works)
1---2name: qdrant-deployment-options3description: Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.4---56# Which Qdrant Deployment Do I Need?78Start with what you need: managed ops or full control? Network latency acceptable or not? Production or prototyping? The answer narrows to one of four options.91011## Getting Started or Prototyping1213Use when: building a prototype, running tests, CI/CD pipelines, or learning Qdrant.1415- Use local mode (Python only): zero-dependency, in-memory or disk-persisted, no server needed [Local mode](https://skills.qdrant.tech/md/documentation/quickstart/)16- Local mode data format is NOT compatible with server. Do not use for production or benchmarking.17- For a real server locally, use Docker [Quick start](https://skills.qdrant.tech/md/documentation/quickstart/?s=download-and-run)181920## Going to Production (Self-Hosted)2122Use when: you need full control over infrastructure, data residency, or custom configuration.2324- Docker is the default deployment. Full Qdrant Open Source feature set, minimal setup. [Quick start](https://skills.qdrant.tech/md/documentation/quickstart/?s=download-and-run)25- You own operations: upgrades, backups, scaling, monitoring26- Must set up distributed mode manually for multi-node clusters [Distributed deployment](https://skills.qdrant.tech/md/documentation/scaling/distributed_deployment/)27- Consider Hybrid Cloud if you want Qdrant Cloud management on your infrastructure [Hybrid Cloud](https://skills.qdrant.tech/md/documentation/hybrid-cloud/)282930## Going to Production (Zero-Ops)3132Use when: you want managed infrastructure with zero-downtime updates, automatic backups, and resharding without operating clusters yourself.3334- Qdrant Cloud handles upgrades, scaling, backups, and monitoring [Qdrant Cloud](https://skills.qdrant.tech/md/documentation/cloud-quickstart/)35- Supports multi-version upgrades automatically36- Provides features not available in self-hosted: `/sys_metrics`, managed resharding, pre-configured alerts373839## Need Lowest Possible Latency4041Use when: network round-trip to a server is unacceptable. Edge devices, in-process search, or latency-critical applications.4243- Qdrant EDGE: in-process bindings to Qdrant shard-level functions, no network overhead [Qdrant EDGE](https://skills.qdrant.tech/md/documentation/edge/edge-quickstart/)44- Same data format as server. Can sync with server via shard snapshots.45- Single-node feature set only. No distributed mode.46- Chose EDGE and want to build on it? See the `qdrant-edge` skill (BM25, snapshot sync, app-side fusion).474849## What NOT to Do5051- Use local mode for production or benchmarking (not optimized, incompatible data format)52- Self-host without monitoring and backup strategy (you will lose data or miss outages)53- Choose EDGE when you need distributed search (single-node only)54- Pick Hybrid Cloud unless you have data residency requirements (unnecessary Kubernetes complexity when Qdrant Cloud works)
om-scogo