Alternatives to DevCycle
Other Feature flags and experimentation vendors we measure, sorted by how much they publish that DevCycle does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from DevCycle on at least one criterion we measured for both. Public transparency score, not a product or security rating.
DevCycle has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and DevCycle does not” is the one that closes them.
| Vendor | Score | Publishes, and DevCycle does not | DevCycle publishes, and they do not | |
|---|---|---|---|---|
| Statsigstatsig.com | 70/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| GrowthBookgrowthbook.io | 61/100 | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| LaunchDarklylaunchdarkly.com | 57/100 | 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| Splitsplit.io | 52/100 | 4 Data location stated, Status page with history, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Harnessharness.io | 48/100 | 4 Data location stated, Status page with history, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Reflagreflag.com | 61/100 | 3 Data processing agreement, Subprocessor list, Data location stated | 1 security.txt (RFC 9116) | Compare |
| Optimizelyoptimizely.com | 39/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Flagsmithflagsmith.com | 35/100 | 3 Status page with history, Uptime SLA with a figure, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Midamida.so | 35/100 | 3 Data location stated, Status page with history, Named privacy contact | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Convertconvert.com | 39/100 | 2 Data processing agreement, Data location stated | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Omniconvertomniconvert.com | 38/100 | 2 Data location stated, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Kameleoonkameleoon.com | 35/100 | 2 Data location stated, Named privacy contact | 2 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.