Qdrant

license

Apache-2.0(OSI, engine core)

source

public(Rust)

managed-tier

Qdrant Cloud (hosted, paid + free tier)

core-gated

ungated(no ee/ path no second license and zero repo-wide hits for enterprise or license key. The two engine features the pricing table marks absent from OSS are both in the open tree - GPU indexing as the lib/gpu crate and resharding across four lib/collection modules with eight consensus tests - so what is sold is control plane rather than engine)

Nothing in the engine is held back, so this scores 5. The managed Qdrant Cloud tier sitting on top is not a gate under this rubric, and a read of the repository and the pricing page finds no gating mechanism anywhere: a code search across the whole repository for `enterprise` returns zero hits and one for "license key" returns zero, there is a single Apache-2.0 LICENSE at the root, and there is no ee/, enterprise/ or second-licensed path in the tree. The pricing table is where a careless read goes wrong. It marks GPU Indexing and Shard Splitting as absent from the open source build, and both are in the open engine: GPU indexing is its own crate at lib/gpu (Cargo.toml, src/, nvidia_icd.json) beside segment, quantization and sparse, and resharding is implemented and consensus-tested at lib/collection/src/collection/resharding.rs, lib/collection/src/shards/resharding.rs, lib/collection/src/shards/shard_holder/resharding.rs and lib/collection/src/shards/transfer/resharding_stream_records.rs, with eight tests/consensus_tests/test_resharding*.py files. What the table actually compares is the managed offering: uptime SLAs, managed backup and disaster recovery against the "custom automation" you would run yourself, multi-AZ topology, disk encryption with customer keys, and Enterprise SSO on the Qdrant Cloud console. Hybrid Cloud is described as running "managed Qdrant clusters on your own infrastructure" - the same engine, operated by someone else. A managed service sold beside a complete open core is not a gate.

• https://github.com/qdrant/qdrant/blob/master/LICENSE recorded 2026-06-04

  Apache-2.0 license text

• https://github.com/qdrant/qdrant recorded 2026-06-04

  v1.18.2 (4 Jun 2026); Qdrant Cloud managed tier with free option

• https://api.github.com/repos/qdrant/qdrant/contents recorded 2026-08-12

  Root tree: one LICENSE beside Cargo.toml, config, docs, lib, openapi, pkg, src, tests and tools. No ee/, enterprise/, commercial/ or proprietary/ path and no second license file, so no part of the engine ships under different terms.

• https://api.github.com/repos/qdrant/qdrant/contents/lib recorded 2026-08-12

  The engine's crates: api, blobstore, bm25, collection, common, edge, gpu, macros, posting_list, quantization, segment, shard, sparse, storage, trififo, uio-grpc-client, wal. GPU indexing is the gpu crate, published here, which is the first of the two features the pricing table marks as absent from OSS.

• https://qdrant.tech/pricing/ recorded 2026-08-12

  Read for a mechanism and found none. Its OSS-versus-paid comparison is control plane: no uptime SLA for OSS against 99.5% free tier and 99.9% (99.95% multi-AZ) on Standard/Premium, "custom automation" backups against managed backup and disaster recovery, multi-AZ topology, disk encryption with custom keys on AWS/GCP, and "Enterprise SSO Authentication" on Premium+. It also marks GPU Indexing and Shard Splitting as absent from OSS - both are in the open tree, so those rows describe the managed offering rather than the engine. Hybrid Cloud is "Run managed Qdrant clusters on your own infrastructure"; Private Cloud is a "Dedicated, isolated deployment".