qdrant-deployment-options

# 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](https://skills.qdrant.tech/md/documentation/quickstart/) - 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](https://skills.qdrant.tech/md/documentation/quickstart/?s=download-and-run) ## 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](https://skills.qdrant.tech/md/documentation/quickstart/?s=download-and-run) - You own operations: upgrades, backups, scaling, monitoring - Must set up distributed mode manually for multi-node clusters [Distributed deployment](https://skills.qdrant.tech/md/documentation/scaling/distributed_deployment/) - Consider Hybrid Cloud if you want Qdrant Cloud management on your infrastructure [Hybrid Cloud](https://skills.qdrant.tech/md/documentation/hybrid-cloud/) ## Going to Production (Zero-Ops) Use when: you want managed infrastructure with zero-...