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