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