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