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