“If we built this in-house, most engineers would look at this and say ‘feature rollout, it’s not that hard’. But when you think about having multiple environments, having a UI, conditional filters, an impression data pipeline, all that—it’s a whole team working for a very long time to be able …

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

"To balance rapid development with the high availability our customers demand, we needed total control over releasing new functionality. To build and maintain such a system would have taken extensive time and resources. With Split, we're getting the features we need today along with the help of a team of …

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

"Split has made us more confident in our release process and also more confident in our data decisions."

"Before Split, our feature releases were cumbersome and time-consuming, requiring our product managers to make special requests to developers every time we wanted to launch new functionality."

"Split's controlled release capability provides us a non-disruptive and dynamic way to ship features for testing and deployment. More importantly, it provides the data we need to quickly iterate on our product features in an informed manner.”

“The integration with Amazon S3 helps us track all the events that happen offline. In our case, an example is someone investing money on our own bank account. That cannot be tracked through Segment, but we obviously aware of when someone sends us the money. An integration with Amazon S3 …

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

"One of our first experiments was a great learning experience. It prevented us from introducing something that we thought was good, but actually would have likely given us a negative impact. We’re now doing another iteration to get it right."

"We use feature flags and run experiments a lot more because it’s easier now with Split. We can target a random sample size. We can increment the size of that sample really easily, and we can toggle it off immediately if there’s an issue."

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

“By decoupling experimentation decision-making from engineering Resources [with Dynamic Configuration], product teams become empowered to make fast and flexible changes to the product with little to no technical knowledge.”

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