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