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