Ship the code. Turn the feature on later.
Each flag has its own value per environment, with targeting rules, percentage rollouts and a kill switch. A change reaches every server in about a second, with no new deploy.
What you get
Four kinds of value
Boolean, string, number or JSON. For features, experiment copy or settings.
Environments and branches
Production, preview and development each have their own config, and a preview branch can have its own.
Targeting rules
By email, plan or any attribute you pass: equals, contains, starts with, in a list and more. The first rule that matches wins.
Percentage rollouts
Give a feature to a share of users. A user always gets the same answer, and raising the share only adds users.
Segments
Make lists of users (staff, early testers, large customers) and use them in any flag's rules.
Kill switch
Send a broken feature back to its off value everywhere with one click.
History and rollback
Every change is kept with who made it. Go back to any version, even of a deleted flag.
env.FLAGS with no network call
In functions and apps, flags are read from a local copy, not from a remote service.
Outside the platform
A mobile app, a web page or another server reads flags with the standard OpenFeature SDKs and a flag key; a browser key sees only the flags marked visible to browsers.
Dashboard, CLI, API and MCP
Create and change flags from any of them; they all call the same API.
A rule, a percentage, one line of code
Create the flag from the CLI and read it in code.
cloudhost flags add new-checkout --type boolean
cloudhost flags rule add new-checkout email ends_with @acme.ir --value true --environment production
cloudhost flags rollout new-checkout 10 --value true --environment productionIncluded in the plans
Flags come with every project. The number of flags, rules and segments depends on the plan; reads from outside the platform are counted as flag requests (100,000 a month free). See the pricing page.
Questions
About a second, and nothing restarts.
env.FLAGS returns the default you passed in code.
Nowhere. Your code passes them when it reads the flag, they are evaluated there, and nothing is stored.
Create your first flag
Code today, the feature when it is ready.
Sign-up is by invite for now. If you have a code, create your account.
Sign up withEmail codeSMS code