Alternatives to ClickHouse
Other Data warehouses and databases vendors we measure, sorted by how much they publish that ClickHouse does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from ClickHouse on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ClickHouse has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and ClickHouse does not” is the one that closes them.
| Vendor | Score | Publishes, and ClickHouse does not | ClickHouse publishes, and they do not | |
|---|---|---|---|---|
| Aivenaiven.io | 78/100 | 5 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +2 | 1 Certifications named | Compare |
| Timescaletimescale.com | 74/100 | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | nothing | Compare |
| Databricksdatabricks.com | 61/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 2 Public pricing, Certifications named | Compare |
| InfluxDatainfluxdata.com | 57/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | 2 Data location stated, Named privacy contact | Compare |
| Neonneon.tech | 52/100 | 4 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| ScyllaDBscylladb.com | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Snowflakesnowflake.com | 52/100 | 3 Data processing agreement, Status page with history, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Dragonflydragonflydb.io | 35/100 | 3 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | Compare |
| Fireboltfirebolt.io | 30/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Exasolexasol.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 5 Data location stated, Public pricing, Certifications named, +2 | Compare |
| CockroachDBcockroachlabs.com | 39/100 | 1 HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| SingleStoresinglestore.com | 39/100 | 1 HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | 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.