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