Increase your feature flag usage to improve release collaboration and visibility
Remove development bottlenecks around code deployments and even test in production
Tightly control and improve specific product experiences through progressive delivery
Deployments and Releases happen as a singular event across the entire userbase.
Releases are progressively delivered to specific user segments with feature flags.
Instead of building their own homegrown feature flag solution, see why Doist chose CloudBees Feature Flags over other platforms.
Read how PetDesk gets better sleep at night knowing they run less risk with their releases using feature flags.
Simple, lightweight, effective.
"In a few hours, I was able to set it up and start setting up A/B testing in our staging environment from specs provided by our product team. Can't ask for much more than that!"Nick K.Lead React Native Mobile Developer, Stadium Goods
"The UI is very friendly and even people with non-technical background can use it without issues. I love the statistics after rolling out an experiment because they accurately reflect how many users have access to each feature. And last but not least I am happy that there’s an easy way to “roll-back” on unsuccessful features."
"Rollout makes it easy to create in code feature flags and has a simple to navigate interface for enabling/disabling those feature flags."
"Easy to use and interface friendly. Everyone (from developer to project manager) can use it easily. The sync with a Github repository is great for audit and platform as code."
Rethink your software delivery strategy by decoupling code releases and feature releases - allowing teams to work on their own schedules without interrupting users.
Control which user segments gain access to new builds and features, easily enabling your team to perform Canary or Blue/Green deployments, and beta releases.
Get the most accurate testing feedback by giving production access to your QA or Testing teams - Never miss a bug again from a poorly replicated testing environment.
Grant access to certain types of users and customers (like trialers, subscribers, premium members, etc) to different features or sections of your product.
Immediately kill, or turn off, features running in production without having to roll back versions or make a change to code. Stop dealing with reverted builds on the weekends.
Gain valuable feedback about how actual users are using features. Have something baked out just enough for beta testing? Roll it out to a small select user base instantly.
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
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)
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