Ship It Off, Turn It On Later
Decide what is live from your dashboard instead of from a deploy pipeline. Switch a feature on, open it to part of your traffic, or turn it off the moment something looks wrong.
Three steps, no redeploy
Flags are configured in the dashboard and read by your site at runtime.
Create the flag
Give the flag a key and a default value. Your code reads the key; the value lives in Zenovay rather than inside your bundle.
Add targeting rules
Decide who gets it: everyone, nobody, or a share of traffic. Rules are evaluated per visitor.
Toggle it whenever you need to
Change the value in the dashboard and your site picks it up on the next load. No build, no deploy, no waiting for a release window.
What you actually get
Remote config with targeting: the part of a flag system most teams use every week.
Feature flag capabilities
Everything the flag system does, described the way it actually works.
Remote Configuration
Flag values live in Zenovay and are read by your site at runtime, so behaviour changes without a new build. Hide unfinished work behind a key, keep a risky change one click away from being switched off, or open a beta to a group before everyone else sees it. Because the value is remote, the same build can behave differently for different visitors without shipping a conditional.
Targeting Rules
Roll a flag out to a percentage of traffic or scope it to a defined audience instead of settling for an all-or-nothing switch.
Instant Toggle
Switch a flag off from the dashboard the moment something looks wrong. Nobody has to find the person who deployed the code.
Works Alongside Experiments
Use a flag to control who can reach a feature and an experiment to measure whether it changed anything. Both live in the same dashboard, on the same data.
Honest About Scope
This is remote config with targeting rules. It does not include approval workflows, environment-scoped audit reviews or a governance layer. If your release process requires those, a dedicated flag platform is the better fit.
Which plans include feature flags?
Feature flags are available on Pro and above. They are not included in the Free plan.
How is a feature flag different from an A/B test?
A flag controls who can see something. An experiment measures whether it made a difference. Use a flag to roll a feature out safely, and an experiment when you want a conversion result with a confidence interval on the lift.
Do flag changes require a deploy?
No. Values are read at runtime, so changing a flag in the dashboard changes behaviour on the next page load without shipping code.
Separate Release From Deploy
Put the switch in the dashboard, where you can actually reach it.
Pro and above • No redeploy to flip a flag • Cancel anytime