Test

Ship features behind a flag.

Turn features on or off, roll them out to a slice of users, and test in production without a redeploy.

if (await shovelbase.flags.isEnabled("new_scorecard")) {
renderNewScorecard()
}
// on for 5% of users · flip it from the console
Flip in real time

Toggle a feature from the console — the change takes effect instantly, no deploy.

Gradual rollout

Ship to 5% of users, then 50%, then everyone — or roll it back in a click.

Test in production

Try an idea on real users before you commit to it, without branching your code.

1Feature Flags

Flip a feature in real time

Turn something on or off from the console and it takes effect instantly — no redeploy, no waiting for a build.

  • Instant on, instant off Toggle it and the change is live.

  • Roll back in a click Changed your mind? Flip it right back.

new_scorecard
dark_mode
beta_export
2Feature Flags

Roll it out a slice at a time

Ship to 5% of users, then 50%, then everyone — try an idea on real people before you commit to it.

  • Gradual by percent Widen the rollout when you're ready.

  • Test in production On real users, without branching your code.

new_scorecard50%
5%25%50%100%

What you'd build with it

The kind of problem Feature Flags is there to solve.

Use case
Try the redesign on a few users first

Roll the new home screen out to 5% of people and watch how it lands before everyone sees it.

Use case
Kill a broken feature without a redeploy

Something goes wrong at launch? Flip it off from the console and the fire’s out in a click.

Use case
Ship it dark, turn it on later

Merge the code now and keep it hidden, then flip the flag on the day you launch.

No LaunchDarkly to bolt on. Feature flags come with the project, evaluated right next to your data.

Compare shovelbase →

The rest of the stack