Transparency alternatives to Unleash
Other Feature flags and experimentation vendors we measure, sorted by how much we found at them and not at Unleash. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 that differ from Unleash on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Unleash has 6 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Certifications named, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Unleash” is the one that closes them.
| Vendor | Score | Found there, not found at Unleash | Found at Unleash, not found there | |
|---|---|---|---|---|
| VWOvwo.comSee also Transparency alternatives to VWO | 70/100 | 4 Subprocessor list, Data location stated, Certifications named, +1 | 2 Public pricing, Uptime SLA with a figure | Compare |
| Reflagreflag.comSee also Transparency alternatives to Reflag | 61/100 | 3 Subprocessor list, Data location stated, Certifications named | 3 Uptime SLA with a figure, Notice before subprocessors change, Named privacy contact | Compare |
| LaunchDarklylaunchdarkly.comSee also Transparency alternatives to LaunchDarkly | 57/100 | 3 Subprocessor list, Status page with history, Certifications named | 2 Data processing agreement, Uptime SLA with a figure | Compare |
| Statsigstatsig.comSee also Transparency alternatives to Statsig | 57/100 | 3 Subprocessor list, Status page with history, Certifications named | 2 Data processing agreement, Uptime SLA with a figure | Compare |
| Harnessharness.ioSee also Transparency alternatives to Harness | 48/100 | 3 Data location stated, Status page with history, Certifications named | 3 Data processing agreement, Public pricing, Uptime SLA with a figure | Compare |
| CloudBeescloudbees.comSee also Transparency alternatives to CloudBees | 30/100 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | Compare |
| Webtrends Optimizewebtrends-optimize.comSee also Transparency alternatives to Webtrends Optimize | 26/100 | 3 Data location stated, Status page with history, Certifications named | 6 Data processing agreement, Public pricing, Uptime SLA with a figure, +3 | Compare |
| GrowthBookgrowthbook.ioSee also Transparency alternatives to GrowthBook | 48/100 | 2 Subprocessor list, Certifications named | 2 Data processing agreement, Uptime SLA with a figure | Compare |
| Kimchikimchi.devSee also Transparency alternatives to Kimchi | 35/100 | 2 Data location stated, Certifications named | 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 | Compare |
| Midamida.soSee also Transparency alternatives to Mida | 35/100 | 2 Data location stated, Status page with history | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | Compare |
| Splitsplit.ioSee also Transparency alternatives to Split | 35/100 | 2 Status page with history, Certifications named | 3 Data processing agreement, Public pricing, Uptime SLA with a figure | Compare |
| ConfigCatconfigcat.comSee also Transparency alternatives to ConfigCat | 26/100 | 2 Certifications named, security.txt (RFC 9116) | 4 Data processing agreement, Uptime SLA with a figure, 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.