Skip to main content
Skip to main content

Qdrant

Qdrant on Zerops provides a fully managed vector database solution designed for AI applications. Focus on building vector search features while we handle infrastructure maintenance, high availability, and data protection.

Supported Versions

Currently supported Qdrant versions:

  • 1.12
  • 1.10

Import configuration version:

  • qdrant@1.12
  • qdrant@1.10

Deployment Modes

Non-HA Mode

  • Single node setup ideal for development and non-production projects
  • Simple deployment and management

HA Cluster

  • Automatically configured with 3 nodes
  • Recommended for production environments
  • Built-in data replication across nodes
  • By default (automaticClusterReplication=true), automatically creates replicas of all shards across all three nodes
    • Can be disabled by setting automaticClusterReplication to false
  • Automatic cluster recovery and node replacement in case of failures

Data Backup

Qdrant backups are created using native snapshotting:

  • Format: .snapshot (compressed)
  • Tooling: Native snapshotting
  • Source: Taken from the primary node (leader in HA clusters)

For backup configuration, scheduling, retention policies, and management options, see the Zerops Backups documentation.

Restoring Backups

To restore a Qdrant backup:

  1. Download the backup file (.snapshot) from the Zerops UI
  2. Prepare your target environment (clean existing collections or use a new instance)
  3. Restore using the Qdrant API. Use the snapshot restore endpoint to import the snapshot file. Follow the official Qdrant documentation for detailed snapshot restore procedures.

For assistance with the restoration process, contact Zerops support.

Network Architecture & Access

Qdrant can be accessed only from services within the same project, public access is not available.

API Keys

API key authentication is required for both HTTP and gRPC API calls. Include the key in your request headers. The keys are automatically generated when the Qdrant service is created and can be found in the service's environment variables:

  • apiKey: Full access API key for administrative operations (creating collections, indexing)
  • readOnlyApiKey: Restricted API key for search operations

HTTP API

  • Port: 6333
  • Connection String: Available as connectionString environment variable or construct using http://${hostname}:${port}

gRPC API

  • Port: 6334
  • gRPC Connection String: Available as grpcConnectionString environment variable or construct using tcp://${hostname}:${grpcPort}

Support

For advanced configurations or custom requirements: