From qdrant
Guides selection among Qdrant deployment options: local mode, Docker, self-hosted, Qdrant Cloud (zero-ops), and Qdrant EDGE for lowest latency.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qdrant:qdrant-deployment-optionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
Use when: building a prototype, running tests, CI/CD pipelines, or learning Qdrant.
Use when: you need full control over infrastructure, data residency, or custom configuration.
Use when: you want managed infrastructure with zero-downtime updates, automatic backups, and resharding without operating clusters yourself.
/sys_metrics, managed resharding, pre-configured alertsUse when: network round-trip to a server is unacceptable. Edge devices, in-process search, or latency-critical applications.
npx claudepluginhub qdrant/skills --plugin qdrantGuides Qdrant scaling decisions for data volume, query throughput, latency, and query volume. Use when data doesn't fit on one node, cluster is slow, or capacity needs assessment.
Guides vector database selection for embeddings and semantic search, compares managed options like Pinecone and self-hosted like pgvector/Milvus, explains ANN algorithms like HNSW.
Guides decisions between managed and self-hosted services like Kubernetes, databases, caches, and monitoring for small teams under 50 engineers. Evaluates operations tax and self-hosting justifications.