Alternatives to Mida
Other Feature flags and experimentation vendors we measure, sorted by how much they publish that Mida does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from Mida on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Mida has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Mida does not” is the one that closes them.
| Vendor | Score | Publishes, and Mida does not | Mida publishes, and they do not | |
|---|---|---|---|---|
| Statsigstatsig.com | 70/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| GrowthBookgrowthbook.io | 61/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 Status page with history | Compare |
| Reflagreflag.com | 61/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 2 Status page with history, Named privacy contact | Compare |
| LaunchDarklylaunchdarkly.com | 57/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| ConfigCatconfigcat.com | 30/100 | 4 Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Splitsplit.io | 52/100 | 3 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Public pricing | Compare |
| Harnessharness.io | 48/100 | 3 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Public pricing | Compare |
| CloudBeescloudbees.com | 30/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Public pricing | Compare |
| DevCycledevcycle.com | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Convertconvert.com | 39/100 | 2 Data processing agreement, Certifications named | 2 Status page with history, Named privacy contact | Compare |
| Optimizelyoptimizely.com | 39/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| Flagsmithflagsmith.com | 35/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 1 Data location stated | 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.