For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
13.5kProductPricingSign inStart free trialBook a demo
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
    • Home
  • Get started
    • Quickstart
    • Introduction to feature flags
    • Unleash architecture overview
  • Core concepts
    • Overview
      • Release management overview
      • Release templates
      • Impact metrics
    • Import and export

Unleash reduces the risk of releasing new features, drives innovation by streamlining the software release process, and increases revenue by optimizing end-user experience. While we serve the needs of the world's largest, most security-conscious organizations, we are also rated the “Easiest Feature Management system to use” by G2.

GitHubGitHubLinkedInLinkedInX (Twitter)X (Twitter)SlackSlackStack OverflowStack OverflowYouTubeYouTube

Server SDKs

  • Node.js
  • Java
  • Go
  • Rust
  • Ruby
  • Python
  • .NET
  • PHP
  • All SDKs

Frontend SDKs

  • JavaScript
  • React
  • Next.js
  • Vue
  • iOS
  • Android
  • Flutter

Feature Flag use cases

  • Secure, scalable feature flags
  • Rollbacks
  • FedRAMP, SOC2, ISO2700 compliance
  • Progressive or gradual rollouts
  • Trunk-based development
  • Software kill switches
  • A/B testing
  • Feature management
  • Canary releases

Product

  • Quickstart
  • Unleash architecture
  • Pricing
  • Product vision
  • Open live demo
  • Open source
  • Enterprise feature management platform
  • Unleash vs LaunchDarkly

Support

  • Help center
  • Status
  • Changelog
Made in a cosy atmosphere in the Nordic countries.Copyright © 2026 Unleash
LogoLogo
13.5kProductPricingSign inStart free trialBook a demo
On this page
  • Overview
  • Create a release template
  • Configure a gradual rollout with release templates
  • Apply a release template to a feature flag
  • Perform a release using a release plan
  • Start the release
  • Pause the release
  • Progress to the next milestone
  • Revert to a previous milestone
  • Edit strategies
Core conceptsRelease management

Release templates

||View as Markdown|
Was this page helpful?

Last updated April 9, 2026

Previous

Impact metrics

Next
Built with
v7.2 Enterprise

Overview

Release templates help you standardize your approach to rolling out new features. By predefining a set of release milestones, you can ensure consistency across all your feature rollouts.

Instead of manually configuring the same activation strategies across different feature flags, you can define release templates once and apply them to any feature flag to initiate a rollout.

Milestones rely on activation strategies to give you full flexibility when it comes to customizing your release templates. Each milestone executes sequentially, ensuring a structured release process.

For example, you might define 3 milestones for a release:

  • Milestone 1: Enable the feature for internal teams to test functionality and resolve initial issues.
  • Milestone 2: Expand the rollout to 20% of beta users to gather feedback and monitor performance.
  • Milestone 3: Release the feature to all users after confirming stability and addressing earlier feedback.

Release template

A predefined sequence of milestones that structures a feature release.

Milestone

Sequential stages within a release template. Each milestone must contain at least one activation strategy, which determines when a feature flag is enabled. You can combine multiple activation strategies in a single milestone. Unleash evaluates each strategy independently, enabling the flag if any strategy resolves to true.

Release plan

An instance of a release template applied to a specific feature flag in a specific environment. You can combine a release plan with additional activation strategies.

Create a release template

For this action, you must be an Editor or have a custom root role with release templates permissions.

To create a release template, do the following:

  1. In the Admin UI, go to Configure > Release templates, and click New template.
  2. Enter the template name and an optional description.
  3. For the first milestone, click Add strategy.
  4. Choose a strategy type and configure your strategy.
  5. Click Add strategy.
  6. Optional: Add, rename, or reorder milestones as needed.
  7. Click Create template.

Configure a gradual rollout with release templates

Milestones are designed to be flexible and do not inherit the configurations of previous milestones. To build a gradual rollout where each milestone expands on the previous one, you must manually configure the progression of the strategies and their constraints.

For example, suppose you want to structure your rollout as follows:

  • Milestone 1: Enable the feature for 50% of users on the Basic plan.
  • Milestone 2: Keep the same 50% of Basic users from Milestone 1 and add 25% of Premium users.

To achieve this, you need to:

  1. Create Milestone 1 with a strategy to target the 50% of Basic plan users.
  2. Create Milestone 2 and keep the ‘50% Basic plan’ strategy. Add a new strategy to target 25% Premium plan users.

The configuration would look something like this:

Example of progressive milestones

Apply a release template to a feature flag

To apply a release template to a feature flag, do the following:

  1. In the Admin UI, open a feature flag and select your target environment.
  2. Click Use template and select one of the available release templates.
  3. Click Add release plan.

If the environment is enabled, the first milestone starts automatically.

Perform a release using a release plan

Release plans apply per feature and environment. To add a release plan, apply a release template.

Start the release

If the environment is enabled, the first milestone begins automatically upon adding the release plan. Otherwise, enable the environment to start the first milestone.

Pause the release

Pause the release at any time by disabling the environment for the feature flag.

Progress to the next milestone

To progress to the next milestone, click Start on the milestone you want to run.

Revert to a previous milestone

To return to a previous stage of the rollout, click Restart on the milestone you want to revert to.

Edit strategies

v7.6

After a release template is applied to a feature flag, you can edit the activation strategies in the resulting release plan. You can update the configuration, constraints, variants, rollout percentage, or set the strategy status to Inactive, just as you would with any standalone strategy. Edits apply only to that release plan and do not change the underlying release template.