Alternatives to Umami
Other Web analytics vendors we measure, sorted by how much they publish that Umami does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from Umami on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Umami has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Umami does not” is the one that closes them.
| Vendor | Score | Publishes, and Umami does not | Umami publishes, and they do not | |
|---|---|---|---|---|
| Amplitudeamplitude.com | 74/100 | 7 Data processing agreement, Data location stated, Status page with history, +4 | nothing | Compare |
| Mixpanelmixpanel.com | 85/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | nothing | Compare |
| PostHogposthog.com | 85/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | nothing | Compare |
| Contentsquarecontentsquare.com | 61/100 | 6 Subprocessor list, Status page with history, Certifications named, +3 | nothing | Compare |
| FullStoryfullstory.com | 57/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | 1 Public pricing | Compare |
| Fathom Analyticsusefathom.com | 65/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | nothing | Compare |
| Plausibleplausible.io | 48/100 | 5 Data processing agreement, Data location stated, No third-party tracking before consent, +2 | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Matomomatomo.org | 52/100 | 4 Data processing agreement, Data location stated, Certifications named, +1 | nothing | Compare |
| TelemetryDecktelemetrydeck.com | 43/100 | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | 1 Public pricing | Compare |
| Parse.lyparse.ly | 39/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 1 Public pricing | Compare |
| Cabinwithcabin.com | 33/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | nothing | Compare |
| Chartbeatchartbeat.com | 26/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 Public pricing, HTTPS enforced with HSTS | 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.