Skip to main content

The Anatomy of Unleash

This guide's purpose is to give you a conceptual overview of how Unleash works. It covers the various components that exist within our system and how they interact with each other and with external applications. The diagrams help you understand the fundamental building blocks, such as projects, environments, variants and of course, feature flags.

The end of this guide presents a short use case, explaining how you might configure Unleash to start working with feature flags.

The root level​

Some things in Unleash are configured and defined on the root level. These options apply across the entire Unleash instance. The most important root configuration options for day-to-day operations are:

Projects​

Projects contain feature flags and their configurations, and a set of active environments.

All Unleash instances must have at least one project at any given time. New instances get a project called “Default”.

Pro and Enterprise customers can create, rename, and delete projects. Open Source users have a single project called 'Default'.

A square labeled 'project' containing another square, labeled 'environment'.
Unleash projects contain one or more environments.

Environments and project environments​

Feature flags can be activated or deactivated independently in different environments. For instance, a feature flag can be active in the development environment, and deactivated in the production environment. Even if their configuration is otherwise identical, deactivated feature flags will never be considered enabled.

Environments in Unleash let you change how a feature flag works in your application’s different environments. For instance, while you are developing a feature, it’s likely that you’ll want it to be available in your development environment, but not in your production environment: environments let you do that. You might also want to enable a feature for only some users in your development environment, but no users in your production environment: environments let you do that.

Environments exist on two different levels within Unleash. The set of all available environments is defined on the root level. Additionally, each project can choose which of these root environments should be available on the project level. The set of environments available to any given project is always a subset of the set of all available environments at the root level.

Each project must always have at least one active environment.

Enterprise users can create and remove environments. Open Source and Pro customers get access to two environments: development and production.

Environments are adjacent to feature flags in Unleash: neither one contains the other, but they come together to let you define activation strategies.

You can use different activation strategies and constraints in different environments. For instance, you can show a feature only to select user IDs in development, but roll it out to 25% of your user base in production.
Environments and API keys

When connecting an SDK to Unleash, it's the API key that decides which environment to fetch features for. For legacy reasons, all Unleash SDKs accept a configuration option called environment, but this does not affect the environment at all. It is an Unleash context field and a holdover from before Unleash had native environments.

Features (feature flags)​

Feature flags are at the heart of Unleash’s functionality. Feature flags belong to projects and live next to project environments. In and of itself, a feature flag doesn’t do anything. You must assign activation strategies to it for it to start taking effect.

When creating a feature flag, you must assign a unique (across your Unleash instance) name, a feature flag type, a project it belongs to, and an optional description. Everything except for the name can be changed later.

A hierarchy showing a project containing an environment containing a feature flag configuration.
Feature flag states are evaluated independently in each environment.

Activation strategies​

A hierarchy displaying an environment containing a feature flag configuration with an activation strategy.
Activation strategies are applied to feature flags on a per-environment basis and decide whether a feature is enabled or not.

Activation strategies (or just strategies for short) are the part of feature flags that tell Unleash who should get a feature. An activation strategy is assigned to **one **feature flag in **one **environment.

When you check a feature flag in an application, the following decides the result:

  1. Is the flag active in the current environment? If not, it will be disabled.
  2. If the flag is active in the current environment, the flag’s strategies decide the result. As long as at least one of a flag’s strategies resolves to true for the current context (user or application), then the flag will be considered enabled. In other words, if you have a hundred strategies and ninety-nine of them resolve to false, but one of them resolves to true, then the flag is enabled.

Activation strategies tie feature flags and environments together. When you assign an activation strategy to a feature flag, you do so in one environment at a time. You can assign the same strategy to the same flag in different environments, but they will be different instances of the same strategy and do not stay in sync. Unleash also lets you copy strategies from one environment to another.

Unleash comes with a number of built-in strategies. All strategies can be further augmented by strategy constraints.

Feature flags exist across environments and can have different activation strategies in each environment.
Feature flag activation strategies can be copied between environments. You can also create new strategies in each environment.

Strategy constraints​

Strategy constraints (or just constraints) help you fine-tune your strategies. They are an extra layer of prerequisites that help you narrow the audience of a strategy down. Strategy constraints are applied to activation strategies.

For example, if you wanted to roll a feature out to 50% of users with **a specific email domain **(such as “@mycompany.com”), then strategy constraints would let you target only users with that email domain.

Constraints can also be used for more general purposes, such as timing feature releases or releasing features in specific regions.

An activation strategy can have as many constraints as you want. When an activation strategy has multiple constraints, then **every constraint **must be satisfied for the strategy to be evaluated. So if you have two constraints: one that says users must have an “@mycompany.com” email address and one that says users must have signed up for a beta program, then the strategy would only be evaluated for users with @mycompany.com emails that have signed up for the program.

Strategies and constraints

Feature flag strategies are permissive: As long as one strategy resolves to true, the feature is considered enabled. On the other hand, constraints are restrictive: for a given strategy, all constraints must be met for it to resolve to true.

We can exemplify this difference with the logical operators AND and OR:

  • For a feature flag, if Strategy1 OR Strategy2 OR .. OR StrategyN is true, then the feature is enabled.
  • For a strategy, it can be evaluated if and only if Constraint1 AND Constraint2 AND .. AND ConstraintN are met.

Note that even if all the constraints are met, the strategy itself might not resolve to true: that will depend on the strategy and the provided context.

You can define constraints on whatever properties you want in your Unleash context.

Constraints are applied to individual strategies and do not stay in sync with each other. When you need to have the same constraints applied to multiple strategies and need those constraints to stay in sync, use segments.

A hierarchy drawing showing a constraint applied to an activation strategy.
Constraints can be applied to strategies, allowing you to narrow a feature's audience.

Segments​

Segments add extra functionality on top of strategy constraints. A segment is a reusable collection of strategy constraints with a name and an optional description. When you apply a segment to a strategy, the strategy will be evaluated as if all of the segment's constraints were applied to it.

Segments let you apply a set of constraints to multiple strategies and keep the constraints in sync between those strategies. Whenever you apply a segment to a strategy, you essentially create a reference to that segment. This means that whenever you change the segment by adding, removing, or changing constraints, this change propagates to all the strategies that reference this segment.

You can apply multiple segments to a strategy. Much like with constraints, every segment needs every constraint to be satisfied for the strategy to be evaluated. If you also have other constraints on the strategy, then those must also be satisfied.

Segments are only available to Pro and Enterprise users.

Segments are reusable lists of constraints that can be applied to a strategy instead of or in addition to constraints.

Variants and feature flag payloads​

By default, a feature flag in Unleash only tells you whether a feature is enabled or disabled, but you can also add more information to your flags by using feature flag variants. Variants also allow you to run A/B testing experiments.

Feature flags are designed to let you decide which users get access to a feature. Variants are designed to let you decide which version of the feature a user gets access to. For instance, if user A is part of your beta testing program and gets access to a new beta feature, then you can use variants to decide whether they should get the red version or the green version of the feature.

When you create new variants for a feature, they must be given a name and a weighting indicating how many users should see this particular variant of the feature. They can also be given a payload.

You can use the variant payload to attach arbitrary data to a variant. Variants can have different kinds of payloads.

A feature flag can have as many variants as you want.

Variants and environments​

Prior to 4.21, variants were independent of environments. In other words: if you're on 4.19 or lower, you’ll always have the exact same variants with the exact same weightings and the exact same payloads in all environments.

Before Unleash 4.21, feature flag variants were the same for all environments.

As of version 4.21, a feature can have different variants in different environments. For instance, a development environment might have no variants, while a production environment has 2 variants. Payloads, weightings, and anything else can also differ between environments.

From Unleash 4.21 on, a feature flag can have different variants in each environment.

Use case: changing website colors​

Using the concepts we have looked at in the previous sections, let’s create a hypothetical case and see how Unleash would solve it.

Problem statement: You have an existing website with a red color scheme, but you’re feeling a bit adventurous and would like to try and see if changing it to a blue color scheme would be better.

Current state: You have an existing website that gets server-side rendered and you have a newly created instance of Unleash.

Configuring Unleash for development​

Assuming you have a brand new Unleash instance, you already have the “Default” project and the “Development” and “Production” environments available. That’s going to be all you need for now.

First things first, in the Default project, you create a new feature flag, called “new-color-scheme” (flag names have to be URL-friendly, so no spaces allowed!).

Because you’d like to see the new color scheme while you’re developing it, you assign a “standard” strategy to the new-color-scheme flag in the development environment and turn it on.

In your application​

You configure an Unleash SDK for your server to communicate with Unleash. When rendering the page, you check the state of the new-color-scheme feature and render a different stylesheet based on the results.

In pseudocode (loosely based on the Node.js SDK), that might look like this:

if (unleash.isEnabled(“new-color-scheme”)) {
  // load stylesheet with the new color scheme
} else {
  // load stylesheet with the old color scheme
}

And with that, the new color scheme is now live in your development environment. Because there aren’t any strategies defined in the production environment yet, the feature is not active, and everything is as it was.

Rolling out the feature to users​

When you’re happy with the new color scheme, you decide to start rolling it out to users. But you want it to go out to only a small number of users at first so that you can get some feedback while rolling out.

You decide to add a gradual rollout strategy to the new-color-scheme feature in the production environment. Because you want to start small, you set the rollout percentage to 5%.

As soon as you enable the production environment, the feature gets rolled out to 5% of your users (assuming you’ve deployed the code to production).

Adding variants​

While you were developing the new color scheme, you also dabbled a bit with other colors in addition to blue: green and purple might be nice too! So you decide to create two extra color schemes that you’re happy with. But you’d like to hear what your users think too, so you need to roll it out to them somehow.

You decide to use feature flag variants to differentiate between the different themes, creating three variants: blue, green, and purple. You want each of them to roll out to the same number of users, so you leave them equally weighted.


const theme = unleash.getVariant(“new-color-scheme”).name;

if (theme === “green”) {
  // load stylesheet with green color scheme
} else if (theme === “blue”) {
  // load stylesheet with blue color scheme
} else if (theme === “purple”) {
  // load stylesheet with purple color scheme
} else {
  // load stylesheet with old color scheme
}

Now users that are included in the gradual rollout will get one of the three themes. Users that aren’t included get the old theme.