How can Qdrant be run from local development through production, and how do the deployment options differ?

For local development, the simplest option is a single Qdrant process, commonly run with Docker. It is fast to start, easy to destroy and recreate, and suitable for learning, development, and small experiments.

For production, you can self-host Qdrant, including a distributed deployment on infrastructure such as Kubernetes, or use Qdrant Cloud as a managed service. Self-hosting gives you control over networking, storage, upgrades, capacity, and compliance, but your team owns the operational work.

Qdrant Cloud moves much of that operational burden to the provider. The trade-off is less infrastructure control and a managed-service cost. I would choose based on availability requirements, compliance, expected scale, operational expertise, and whether the organization already has a mature Kubernetes platform.

A common mistake is assuming that putting the same Docker container on a production VM is equivalent to a production deployment. Persistence, backups, security, resource sizing, observability, upgrades, and failure recovery still have to be designed.