SaaS Ranking

Alternatives to Percona

Other Data warehouses and databases vendors we measure, sorted by how much they publish that Percona does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 26 that differ from Percona on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Percona has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Percona does not” is the one that closes them.

VendorScorePublishes, and Percona does notPercona publishes, and they do not
Aivenaiven.io 78/100 8 Data processing agreement, Subprocessor list, Public pricing, +5 1 Certifications named Compare
Timescaletimescale.com 74/100 7 Data processing agreement, Subprocessor list, Public pricing, +4 nothing Compare
Databricksdatabricks.com 61/100 6 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +3 1 Certifications named Compare
Neonneon.tech 52/100 6 Subprocessor list, Public pricing, Uptime SLA with a figure, +3 1 Data location stated Compare
Snowflakesnowflake.com 52/100 6 Data processing agreement, Status page with history, Public pricing, +3 1 Data location stated Compare
InfluxDatainfluxdata.com 57/100 5 Data processing agreement, Status page with history, Public pricing, +2 1 Data location stated Compare
ScyllaDBscylladb.com 52/100 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 nothing Compare
Dragonflydragonflydb.io 35/100 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 2 Data location stated, Certifications named Compare
CockroachDBcockroachlabs.com 39/100 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact nothing Compare
SingleStoresinglestore.com 39/100 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact nothing Compare
Xataxata.io 39/100 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact nothing Compare
ClickHouseclickhouse.com 35/100 3 Public pricing, security.txt (RFC 9116), Named privacy contact 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.