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