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