Alternatives to Qdrant
Other Data warehouses and databases vendors we measure, sorted by how much they publish that Qdrant does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Qdrant on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Qdrant has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Qdrant does not” is the one that closes them.
| Vendor | Score | Publishes, and Qdrant does not | Qdrant publishes, and they do not | |
|---|---|---|---|---|
| Aivenaiven.io | 78/100 | 6 Data processing agreement, Subprocessor list, Public pricing, +3 | 1 Certifications named | Compare |
| Timescaletimescale.com | 74/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | nothing | Compare |
| Databricksdatabricks.com | 61/100 | 4 Subprocessor list, Status page with history, security.txt (RFC 9116), +1 | 1 Certifications named | Compare |
| InfluxDatainfluxdata.com | 57/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 2 Data location stated, Named privacy contact | Compare |
| Neonneon.tech | 52/100 | 4 Subprocessor list, Public pricing, Uptime SLA with a figure, +1 | 1 Data location stated | Compare |
| Snowflakesnowflake.com | 52/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 1 Data location stated | Compare |
| Dragonflydragonflydb.io | 35/100 | 3 Data processing agreement, Public pricing, Uptime SLA with a figure | 3 Data location stated, Certifications named, Named privacy contact | Compare |
| ScyllaDBscylladb.com | 52/100 | 2 Data processing agreement, Notice before subprocessors change | nothing | Compare |
| ClickHouseclickhouse.com | 35/100 | 2 Public pricing, security.txt (RFC 9116) | 1 HTTPS enforced with HSTS | Compare |
| DoubleClouddouble.cloud | 30/100 | 2 Subprocessor list, Public pricing | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Fireboltfirebolt.io | 30/100 | 2 Status page with history, Public pricing | 2 Data location stated, Named privacy contact | Compare |
| Tursoturso.tech | 22/100 | 2 Public pricing, security.txt (RFC 9116) | 3 Data location stated, Certifications named, Named privacy contact | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.