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