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