Beta testing

Also called: beta program, beta release

Last updated:

Beta testing is a release stage where a feature goes to a defined group of real users while everyone else carries on without it. You are trying to learn from usage you cannot simulate. Real users arrive with data shapes and hardware no test suite covers. With feature flags the beta cohort is a targeting rule rather than a separate build, so joining or leaving the beta is a configuration change and the code ships once.

How a beta cohort is defined

The cohort is whoever a targeted rollout rule matches. Common shapes are an opt-in attribute your app sets when someone clicks "join the beta", a plan tier, an allowlist of accounts, or a segment you reuse across several flags. Membership is re-checked on every evaluation, so a user who opts out stops seeing the feature on their next request and nothing needs redeploying. The targeting guide covers the rule model and the operators available.

Beta testing and the stages either side of it

Dogfooding comes first, using your own staff. The feedback is expert and the tolerance for breakage is high. A beta widens that to real users who agreed to be early. They bring variety your own team cannot produce. With a canary release the question changes, because sampling ordinary traffic checks that the change is safe without asking anyone what they think of it. Most teams run all three on the same flag, widening the rule at each step.

Want the full picture? Read the concept guide: Targeting →

Try it in your own app

Free Solo plan covers 10 flags and 2 environments. No credit card, no demo call — sign up and ship.