Controlled rollout

At Split, we “dogfood” our own product in so many ways. Our engineering and product teams are using Split nearly every day. It’s how we make Split better.

Every tech company, should be using a robust feature flag system. A well-built system will provide a host of value-adds and efficiencies for your dev team

Controlled rollouts, also called canary releases, or percentage rollouts, are a vital part of software releases. With controlled rollouts, you can release your new feature to a small subset of users, verify proper functionality, and then slowly roll the feature out to your entire user base once you know it…

Feature launches in leading engineering teams increasingly look like a ramp rather than a one time switch, going through dogfooding, debugging, max power ramp, scalability and learning phases.

Canary releases (also called “canary deployments”) and feature flag rollouts are two common feature release strategies for testing in production, increasing the safety of continuous delivery, deploying faster and more often. Both aim to reduce the “blast radius” of unforeseen problems and build confidence in a new release. Both gradually…

The shift-left testing emphasizes test execution early and often, providing rapid feedback to development teams for each new code commit. Shift-right extends application testing into the production environment. Learn about the benefits and recommended best practices of using feature flags to support Testing in Production.

For any company to be successful the entire team needs to work together and push towards a set of unified of goals, which often evolve into a series of vital business KPIs. For SaaS businesses, these goals may align with metrics like the number of logos, number of seats, account utilization, and total MRR. Marching towards these goals can be challenging when trying to understand how team and individual contributions impact movement in these key metrics.