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