The Split Blog

It’s easy to think of the user interface as the primary target for new functionality, with product teams eagerly watching important business metrics such as conversion rates and user engagement for improvements after each release. But behind the scenes, engineers are continually working on server-side innovations such as changes in…

Canary releases (also “canary deployments”) and feature flag rollouts are two common feature release strategies for testing in the production environment, 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…

Product teams that don’t take into account a user communication and user feedback collection strategy as part of their experiments risk not getting enough data to evaluate results. This article walks through a couple key communication steps that products should follow to ensure effective and timely product experiments.

Brian Bell joins Split as CEO and discusses the opportunity to drive forward software innovation.

Split named as a 2019 CNBC Upstart 100 most promising startup based on rapid customer and revenue growth.

Providing an always-on and highly secure feature flagging and experimentation platform is core to making product decisions with Split. From the beginning, we have designed and built our infrastructure and practices with security and reliability as a top priority and are excited to validate this with SOC 2 Type 2 certification.

Audit logs make it easy to stay compliant and find feature flag changes made by your team. We’ve now made it easy to diff, comment, and find your logs.

APM tools are great at monitoring your app, but they struggle to find errors in features post-release. Feature Monitoring helps you find the root cause.

Use measures of impact, absolute value, and error margins to analyze whether an A/B test was a success.

Intrigued by Progressive Delivery, the idea of moving faster & more safely by decoupling deploy from release? Watch or read Safe at Any Speed!

Over the past few months we’ve been out in the field, chatting with development and operations teams from more than 100 different organizations around the U.S. We wanted to know how they get software to market. How often do they release new features to their users? How often do they…

We had an amazing time at this year’s AWS re:Invent in Vegas. We were able to chat with more than 2,000 developers, operators, and cloud architects that stopped by. A few observations: Feature flags were a hot topic. We chatted with quite a few organizations that are already getting value…

Kicking off an internally developed feature flagging system is standard practice for many companies today as feature flags help engineering teams release faster at lower risk. As use cases for feature flags grow, so do the challenges of building an in-house system. This article will explore 10 challenges of building an in-house feature flagging solution.

This is one post in a series about managing the breakup of a monolithic architecture into a small service. In the first post of the series we looked at some fundamental techniques which allowed us to perform this sort of broad architectural shift as a series of small, safe steps. We started off…

This blog posts describes the sequence of changes a team can use to extract a chunk of functionality out from a monolith while continuing to deliver features and functionality in parallel.