Plans and limits
Four plans, one rule: a plan limits what you can add, never what is already serving your customers. A new organization starts on Free.
The plans#
Flags are unlimited on every plan. Beyond the numbers below, the kill switch, SDK access, export of your configuration and safe fallback behaviour are on every plan, and basic targeting (named users, accounts and devices, and one rule with one condition) is free.
| Free · Pro · Business · Enterprise | Description |
|---|---|
| Price | Free $0. Pro $29 a month or $290 a year. Business $99 a month or $990 a year. Enterprise is priced by agreement, so contact us. |
| Projects | 1 · 5 · 25 · no cap |
| Members (people plus open invitations) | 2 · 5 · 15 · no cap |
| Environments | 2 · no cap · no cap · no cap |
| API keys (not revoked) | 5 · 22 · 40 · no cap |
| SDK requests included a month | 150,000 · 450,000 · 1,000,000 · by agreement |
| Alert rules | 0 · 5 · 50 · no cap |
| Notification channels | 0 · 2 · 10 · no cap |
| Beyond the allowance | Free: notices only. Pro: $3 per extra million. Business: $2 per extra million. Enterprise: by contract. Estimated on the plan page, not charged yet. |
| History (audit log, flag activity) | 7 days · 30 days · 365 days · no cap |
| Roles that can be given | Developer · Developer and Viewer · all built-in · all built-in plus custom |
| Feature | From plan | Description |
|---|---|---|
| Percentage rollouts, advanced targeting, segments | Pro | Free keeps 0% and 100%, named people and one simple rule. |
| Scheduled releases, alert rules, configuration import | Pro | Configuration export is free on every plan. |
| Approval workflows, audit export, outcome analytics | Business | Not on Free or Pro. |
| Custom roles | Enterprise | Built-in roles are on the plans above. |
When an action is not in your plan#
The server refuses a gated action with HTTP 402 and a message written for people. The console shows an upgrade prompt, and a lock badge (“Pro”, “Business”) beside controls the plan does not include.
| Code | Description |
|---|---|
| FEATURE_NOT_IN_PLAN | The plan does not include the capability, for example approvals on Pro. |
| PLAN_LIMIT_REACHED | The plan includes it but you are at the cap, for example a sixth project on Pro. |
| DOWNGRADE_BY_CANCELLING | A payment for a smaller plan on top of a bigger one is refused. Cancel instead; see Billing. |
402 is deliberately not 403, so a client can offer a way forward. Permission is checked first: someone without the permission hears “forbidden”, not “upgrade”. SDK delivery endpoints never answer 402; a limit never stops your flags being served.
Controls follow the plan#
A button the plan cannot use is disabled with the reason as its tooltip, and a menu link to a page the plan does not include is hidden. This is a convenience: the server refuses the action either way. A partial rollout percentage is the one control left enabled, because 0% and 100% are free; 1 to 99 is refused with an explanation.
Downgrades never change what is served#
- Flags, rollouts and releases that already exist keep serving exactly as configured. Nothing is deleted.
- Over a new cap, you keep what you have and cannot add more.
- A flag already using a gated feature can still be toggled and edited elsewhere. Touching the gated part needs the plan.
- An environment already set to require approval keeps requiring it. Existing alert rules keep evaluating.
- Alerts, Segments, Releases and a flag's targeting still open and show what is there; only adding is refused.
- Outcome analytics becomes read-only for a flag that already has data: nothing new is recorded, the report shows what was collected, and a flag that never had data is still refused.
- History beyond the window is hidden, not deleted.
Plan and billing belong to the owner#
The Plan and usage page, its menu entry, the plan summary in Settings and the payment history are for the organization's owner only. Everyone else sees lock badges and, on a refused action, “ask the owner”. The owner upgrades from the plan cards; Pro and Business open a secure payment page, and Enterprise is by agreement and links to an email address. See Billing.
Changes can take a few seconds
A plan change reaches every server instance within 10 seconds.