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