Feature Flags / Toggles

Separate Code Deployment From Feature Release

Why Feature Flags?

As engineering teams increasingly adopt continuous delivery best practices, many find that there is a gap in how to manage the customer experience. Feature flags, or feature toggles, are a best practice that solves the problem of controlling the user experience, while still empowering developers to integrate code as soon as it is ready to deploy.

Why Split?

As a key enabling technology for continuous delivery, Split solves the feature flag gap. And, Split goes beyond simple on/off feature toggling, providing granular targeting capabilities to expose a feature to exactly the right users, based on any attribute and with sophisticated regex matching. This enables more comprehensive feature management and gives product teams the flexibility to ensure exactly the right user experience.

Release Features Faster with Less Risk

Split enables feature flag driven deployment and helps engineering teams control
what code executes or stays hidden for end users.

Global User Segments

Define groups that can be used in whitelists in any feature definition. Typically used to define beta users, VIP customers, or internal employees.

Customer Targeting

Be extremely specific in selecting the customers to be included in a release by custom segments, real-time attributes or percentage.

Full-Stack Feature Control

Manage features anywhere in your codebase, across any language, and deliver in any deployment environment.

Android
Go
iOS
Java
JavaScript
.NET
Node.js
PHP
Python
Ruby
Ruby on Rails

Additional Features

Multi-Variate Feature Flags

Manage and control whether segments of code execute for end-users, and define multiple treatments (i.e. variations) of a feature. Configure any number of treatments.

Kill Switch

Disable problematic code while keeping the rest of the feature release intact.

Granular Rollouts

Create focused on/off feature release plans or release multiple versions of the same feature all at once.

Audit Logs

Track every change that takes place, who made them, and what exactly was added or removed from your feature configuration.

Traffic Type Definition

Configure multiple ways for an app to identify a user to Split to determine what version of a feature to show. For example, B2B companies can target users by user ID, or by customer account.

Impression Data

View and extract the event data generated every time a Split feature flag tells your app what treatment to execute.

Benefits to Your Team

  • Ship code directly to production as soon as a feature is complete.
  • Decouple feature release from code deployment so new features can reach the right users without waiting to be bundled together into one release.
  • Expose a new feature to exactly the right group of users.
  • Mitigate risk by incrementally rolling out features to your users.
  • Instantly make problem code invisible to users without needing to recall a deployment or issuing a patch.

Introducing Decisions October 2 San Francisco Learn more