Qdrant Hybrid Cloud
Product · Self-hosted / on-prem software · Sales by Qdrant
Your Data, Your VPC, One Managed Console
Qdrant Hybrid Cloud allows businesses to run a managed vector database inside their own Kubernetes clusters for total data sovereignty. It is ideal for enterprises with strict residency requirements that want the convenience of a managed service without their data leaving their network.
Category: Database
- Integrations
- Kubernetes, AWS, GCP, Azure, Vultr
- Supported Kubernetes
- EKS, GKE, AKS, and conformant distributions
- Management Plane
- Qdrant Cloud Console (cloud.qdrant.io)
- Data Plane Location
- Customer VPC or On-premise
- Outbound Port
- 443 (HTTPS/gRPC)
- Connectivity Type
- Outbound only (No inbound ports)
- Data plane runs in your own Kubernetes cluster (EKS, GKE, AKS)
- Managed through the central Qdrant Cloud Console
- No user data leaves your environment; only metadata is shared
- No inbound ports or cloud credentials required for setup
Overview
It allows organizations to run the Qdrant data plane within their own Kubernetes infrastructure on AWS, GCP, Azure, or on-premise, while utilizing Qdrant's managed control plane for operations. This architecture ensures that vectors, indexes, and backups remain entirely within the customer's network, as Qdrant only receives operational metadata like cluster health and resource usage. The solution is managed through the central Qdrant Cloud Console, providing a unified interface for provisioning and scaling clusters across different environments.
Deployment and Privacy
- Local Data Plane: The data plane runs entirely in the customer's own Kubernetes cluster on AWS, GCP, Azure, or any conformant distribution.
- Centralized Management: Clusters are provisioned and managed from the central Qdrant Cloud Console, providing a single interface for every deployment type.
- Data Sovereignty: Qdrant Cloud receives only operational metadata such as cluster health, resource usage, and collection names; no user data leaves the environment.
- Secure Connectivity: The Cloud Agent in the cluster opens outbound connections to port 443, requiring no inbound ports or cloud credentials to be shared.
Operations and Infrastructure
- Kubernetes Native: Supports any standard-compliant Kubernetes distribution, including EKS, GKE, and AKS.
- Regional Control: Allows placing data in specific cloud accounts and regions to meet residency and compliance requirements.
- Managed Operator Service: Qdrant operates the Kubernetes Operator and container registry that delivers container images to the cluster.
- Infrastructure Ownership: The customer remains responsible for the Kubernetes environment, storage provisioning, and load balancers.
Use cases
- Regulated industries keep sensitive vectors and backups within their own infrastructure while using a managed control plane.
- Platform teams manage multiple Qdrant clusters across different cloud providers from a single centralized console.
- Developers deploy low-latency AI retrieval by placing the data plane in the same region as their application.
Specifications
- Deployment
- Customer-owned Kubernetes cluster (AWS EKS, Google GKE, Azure AKS, or conformant)
- Integrations
- Kubernetes, AWS, GCP, Azure, Vultr
- Supported Kubernetes
- EKS, GKE, AKS, and conformant distributions
- Management Plane
- Qdrant Cloud Console (cloud.qdrant.io)
- Data Plane Location
- Customer VPC or On-premise
- Outbound Port
- 443 (HTTPS/gRPC)
- Connectivity Type
- Outbound only (No inbound ports)
- Storage Ownership
- Customer-managed block storage
- Control Plane Provider
- Qdrant Cloud
How it works
- Start Setup in Console: Open the Qdrant Cloud Console and initiate the Hybrid Cloud enrollment flow.
- Deploy Operator and Agent: Run the generated install command to deploy the Qdrant Operator and Cloud Agent into your Kubernetes cluster.
- Provision Hybrid Cluster: Create a Qdrant cluster and select your registered Hybrid Cloud environment as the target for deployment.
FAQ
Does Qdrant have access to my data in Hybrid Cloud?
No. The data plane runs inside the customer's Kubernetes environment, and Qdrant Cloud only receives operational metadata like cluster health and resource usage.
Who is responsible for Kubernetes operations and storage?
The customer is responsible for the Kubernetes environment, storage, and load balancers, while Qdrant manages the control plane and Kubernetes Operator.
Added by AntSpace from public sources (qdrant.tech).