Feature Flag Rollout Planner

Plan staged feature flag rollouts with users per stage, guardrails and a deterministic bucketing simulator.

Plan

Proceed if

Every condition must hold before the next stage.

Roll back if

Any condition turns the flag off.

Stages

  1. Stage 1
  2. Stage 2
  3. Stage 3
  4. Stage 4
  5. Stage 5

The final stage may have no observation time.

Rollout

Stages
5
Total observation
6d 0h
Final rollout
100%
Audience
—
  • 0 errors
  • 0 warnings
  • 4 notes
  1. Stage 1

    5%Observe: 24h
    Users on
    —
    New users
    —
    Cumulative exposure
    —
  2. Stage 2

    10%Observe: 24h
    Users on
    —
    New users
    —
    Cumulative exposure
    —
  3. Stage 3

    25%Observe: 48h
    Users on
    —
    New users
    —
    Cumulative exposure
    —
  4. Stage 4

    50%Observe: 48h
    Users on
    —
    New users
    —
    Cumulative exposure
    —
  5. Stage 5

    100%Observe: Final stage
    Users on
    —
    New users
    —
    Cumulative exposure
    —

Criteria for every stage

Proceed if

None defined

Roll back if

None defined

Checks

  • Info

    Audience size not set

    audience-missing

    Users per stage and cumulative exposure need the total audience.

    Consider: Enter the number of users the flag can reach.

  • Info

    Flag key not set

    flag-key-missing

    The simulator and the checklist use the flag key.

    Consider: Enter the key from your flag service, for example checkout-redesign.

  • Info

    No proceed criteria

    guardrails-empty

    Nothing defines when it is safe to move to the next stage.

    Consider: Add metrics such as error rate or p95 latency under "Proceed if".

  • Info

    No rollback conditions

    rollbacks-empty

    Nothing defines when to turn the flag off.

    Consider: Add at least one condition under "Roll back if".

Plan updated: 5 stages, 6d 0h of observation.

What does the Feature Flag Rollout Planner do?

It turns a staged release into a concrete plan: users per stage, new and cumulative exposure, observation windows, the total timeline, and the conditions to proceed or roll back. It validates the plan (duplicate or descending percentages, missing observation time, values over 100%) and exports it as Markdown, JSON, YAML, a checklist or a compact AI context block.

How to use
  1. 1.Enter the feature name, flag key, owner and audience size, or load an example.
  2. 2.Choose a preset or edit the stages: rollout %, observation time and an optional note.
  3. 3.Add "Proceed if" guardrails and "Roll back if" conditions.
  4. 4.Review the stages and checks, then test user IDs in the Simulator.
  5. 5.Copy or download the plan from Export.
How the assignment simulator works

Each user gets a bucket from murmur3_x86_32 of "flagKey:userId" with seed 0, reduced to 0.00–99.99. A user is ON when the bucket is below the stage percentage, so the same user keeps the same bucket and stays ON as the percentage grows. Changing the flag key reshuffles everyone. This is a generic deterministic simulation; LaunchDarkly, Unleash, GrowthBook and other services use their own hashing, salts and bucket ranges, so their assignments differ.

Privacy and limits

Planning, simulation and exports run in your browser. The plan is not saved; only the selected export format is remembered. Plans hold up to 20 stages and 12 conditions per list, and the simulator accepts up to 1,000 user IDs (64 KB).

CodingTool is officially live on

Launched on StartupBaseCodingTool.dev - Free, Fast & Easy Developer Tools in One Place | Product HuntCodingTool - Featured on Startup FameFazier badgeListed on Turbo0Featured on Twelve ToolsFeatured on Findly.toolsLaunchpadly Startup DirectoryCodingTool.dev — Featured on Smol Launch