"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.”

"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. …

“We had the intention to change the password field, but we didn’t have a way to know how good it was effectively, and to be able to control it in-house, within our product team. Split allowed us to do all of that and more.”

"It’s powerful to think about all features launched before Split and how many of those must have cost us money that we don’t know about."

“Split provides so much more than just a tool set change in that respect. You know, it sounds simple, feature toggles, but it’s transformative in nature. It’s transformative in terms of the teams, in terms of the culture that we adopt.”

“We have in total about 14 teams working on our digital asset management platform. All of the teams are using Split."

"Split has transformed the way that we deliver software. Granular targeting of features to customers has made us more responsive, and data from Split gives us an audit trail in case any issues arise."

"Split is incredibly empowering for product managers. The web console consolidates and provides transparency into every release, while also enabling teams to make changes dynamically without relying on engineering. With Split, engineering and product teams can collaborate to more efficiently to create, manage, and complete rollouts that much faster.”

“Split provided the platform and integrations we needed to run full stack experiments for key technical and customer experience questions.”

“Without Split, rollbacks could take a couple hours to a day. And after that, there might still be a lot of code cleanup. Split helped us increase our engineering velocity and code stability.”

"Split has enabled us to move much faster. We can ship code straight through to Production knowing that our users won’t see it until we’re ready to show them.”

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

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

"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)."