"It’s inherently collaborative and transparent, a rigorous and sound process based on the hard data we know about."

"Split allows us to safely merge code with confidence."

"A/B testing is a side effect of controlled release. That’s what I love most about Split."

"Split gives me a lot of confidence in our releases as we are able to customize our rollouts, and even roll back quickly if needed. It also allows us to target certain segments that we’d like to release to prior to others.”

"Leveraging Split with our existing tool stack, we’ve been able to consolidate our agile deployment strategies to deliver every three weeks from an original 1.5 months."

"Without Split it was hard to time the release of our web app, API, and mobile app – given app store approvals. Now we can group a change behind a feature flag, do a production dry run, and toggle it on for users."

"Split gives us an easy and fast way to pull the plug if something goes wrong without a heavy involvement from engineers."

“Split has allowed Vida to test our mobile application in a way we wouldn’t be able to do otherwise.”

“If we build it we have to test it to make sure it’s doing the right thing. When we conduct backend experiments, we have to know the system will remain reliable. We have to make sure the backend behaves in a way that doesn’t impact the user experience.”

"Thanks to Split, we were able to learn that the risky version actually had the highest adoption by our customers while keeping overall signup conversion steady."

"The system is very reliable, it has a good number of integrations already in place and works nicely with CDPs. The support team is amazing and they answer questions in a very timely manner. Also very helpful are the governance tools. The python Admin API has also been very helpful …

"With Feature Monitoring, our engineering team can deploy rapidly while ensuring that new functionality won’t negatively impact our core KPIs such as page load time and errors per user."

"90% of our changes are behind a split (feature flag)."

"The kill button is super easy. Now I just, ‘whoop’, kill it. If we are seeing something wonky, it makes it so easy to turn off. When we’ve triaged the feature we can go back and re-enable it."

"At the point engineers make deployments live, they want to understand how the features are performing, from a customer experience, user value, and system standpoint. We know that one of the big challenges developers face in understanding impact is how to get all of the data in the first place. …