Transparency alternatives to Crunchy Data
Other Data warehouses and databases vendors we measure, sorted by how much we found at them and not at Crunchy Data. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Crunchy Data on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Crunchy Data has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Crunchy Data” is the one that closes them.
| Vendor | Score | Found there, not found at Crunchy Data | Found at Crunchy Data, not found there | |
|---|---|---|---|---|
| Aivenaiven.ioSee also Transparency alternatives to Aiven | 78/100 | 5 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +2 | 1 Certifications named | Compare |
| Prismaprisma.ioSee also Transparency alternatives to Prisma | 65/100 | 5 Data processing agreement, Status page with history, Uptime SLA with a figure, +2 | 1 Data location stated | Compare |
| Tiger Datatigerdata.comSee also Transparency alternatives to Tiger Data | 74/100 | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | nothing | Compare |
| Supabasesupabase.comSee also Transparency alternatives to Supabase | 70/100 | 4 Data processing agreement, Uptime SLA with a figure, security.txt (RFC 9116), +1 | nothing | Compare |
| SurrealDBsurrealdb.comSee also Transparency alternatives to SurrealDB | 65/100 | 4 Data processing agreement, Subprocessor list, security.txt (RFC 9116), +1 | 1 Data location stated | Compare |
| Weaviateweaviate.ioSee also Transparency alternatives to Weaviate | 61/100 | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | 2 Data location stated, Named privacy contact | Compare |
| Dremiodremio.comSee also Transparency alternatives to Dremio | 57/100 | 4 Data processing agreement, Status page with history, No third-party tracking before consent, +1 | 2 Data location stated, Named privacy contact | Compare |
| PlanetScaleplanetscale.comSee also Transparency alternatives to PlanetScale | 43/100 | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| Redisredis.ioSee also Transparency alternatives to Redis | 65/100 | 3 Subprocessor list, security.txt (RFC 9116), Notice before subprocessors change | nothing | Compare |
| Snowflakesnowflake.comSee also Transparency alternatives to Snowflake | 65/100 | 3 Data processing agreement, Status page with history, security.txt (RFC 9116) | nothing | Compare |
| Dragonflydragonflydb.ioSee also Transparency alternatives to Dragonfly | 57/100 | 3 Data processing agreement, Uptime SLA with a figure, No third-party tracking before consent | 2 Certifications named, Named privacy contact | Compare |
| InfluxDatainfluxdata.comSee also Transparency alternatives to InfluxData | 57/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 2 Data location stated, 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.