Feature Split Testing for Financial Services
Free Up Engineering Resources to Produce Features that Benefit Your Customers
Read WePay’s Story
“Adopting Split means we can keep releasing code but make features accessible only when we need them to be, and with the click of a button.”Chris Conrad, VP of Engineering, WePay (Chase)
Split Solves This
Split helps teams move faster by separating code deployment from release. Rather than having to release features to all of your users at once, you can run small scale experiments to determine if the feature will benefit your users before rolling it out to your entire userbase.
Deploy features to subsets of your users through advanced targeting capabilities.
Conduct experiments to understand the impact a new feature will have before rolling out to your entire userbase.
Split Management Console
Teams can control features without requiring complex technical knowledge.