Transparency alternatives to Mida
Other Feature flags and experimentation vendors we measure, sorted by how much we found at them and not at Mida. This is a comparison of disclosure, not of features or fitness.
12 shown of 28 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 “Found there, not found at Mida” is the one that closes them.
| Vendor | Score | Found there, not found at Mida | Found at Mida, not found there | |
|---|---|---|---|---|
| VWOvwo.comSee also Transparency alternatives to VWO | 70/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 2 Status page with history, Public pricing | Compare |
| Reflagreflag.comSee also Transparency alternatives to Reflag | 61/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 2 Status page with history, Named privacy contact | Compare |
| LaunchDarklylaunchdarkly.comSee also Transparency alternatives to LaunchDarkly | 57/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Statsigstatsig.comSee also Transparency alternatives to Statsig | 57/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| GrowthBookgrowthbook.ioSee also Transparency alternatives to GrowthBook | 48/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data location stated, Status page with history | Compare |
| Unleashgetunleash.ioSee also Transparency alternatives to Unleash | 48/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 2 Data location stated, Status page with history | Compare |
| ConfigCatconfigcat.comSee also Transparency alternatives to ConfigCat | 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 |
| Harnessharness.ioSee also Transparency alternatives to Harness | 48/100 | 3 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Public pricing | Compare |
| Splitsplit.ioSee also Transparency alternatives to Split | 35/100 | 3 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Public pricing | Compare |
| CloudBeescloudbees.comSee also Transparency alternatives to CloudBees | 30/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Public pricing | Compare |
| DevCycledevcycle.comSee also Transparency alternatives to DevCycle | 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 |
| Flagsmithflagsmith.comSee also Transparency alternatives to Flagsmith | 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.