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