Plagued by time consuming emergency rollbacks, 'merge hell' and the inability to limit the blast radius of releases? Feature flags are the answer, but most developers are using homegrown solutions which are fragile, resource intensive to maintain and hard to scale.
What if you had a feature flag management solution with robust deployment rules, audience segmentation and a testing framework for progressive delivery?Read the Datasheet
Gradually introduce features based on user segments to reduce the risk of exposing the entire user base to code that hasn't been battle-tested.
Toggle off features with a kill switch
Gradually rollout and rollback
Pre-production and live testing
Decouple feature releases from code deployments with GitOps style feature flags. When every feature is released behind a flag you can commit directly to the mainline branch - speeding development and releasing at will.
Commit incomplete code to master
Test live, in production
Test values locally before code merge
Parallelize release changes
Receive fast feedback so that developers can iterate on features quickly. You'll know whether your feature is loved before it's released to the majority of end users in production.
Segment users dynamically or statically by any property in the code
Create rich segment rules
View all flags on a central dashboard
Integrate with any analytics, APM or observability tool
Support A/B and beta testing, canary and blue-green deployments
Drive increased governance, visibility, traceability and auditability to reduce risk.
Treat your feature flags the same way that configuration as code treats applications
Document changes and versioning for feature flags in the same way the pull request tracks changes and versioning for application changes in the SCM
Push changes to the main branch - CloudBees Rollout understands how to update the YAML file configuration to the desired state for the feature flag
CloudBees Rollout is the only solution that uses private/public keys to verify that the data received by the SDK is indeed the data sent by the CloudBees Rollout system, securing the platform against man-in-the-middle attacks.
No access to or ability to save end user data - including any end user's Personally Identifiable Information (PII)
Secured via 128 bit SSL, using a 2048 bit RSA encryption key
2FA, AES 256 hash and random salt encrypted, backend only accessible via VPN with internal credentials (2FA and private access keys)