Usage & billing
Flagon's managed service is priced on what you use, not how many people use it. Adding teammates never changes the bill. You pay for the billable events your usage generates, drawn against a single credit shared across every product.
This is the managed service
Billing applies to the hosted service at flagon.io. Self-hosting is free, source-available, and has no user limit or usage metering: you run it on your own infrastructure.
What you're billed for
Each product meters its own billable event, and only the billable event counts. For Feature Flags, that event is an exposure: a record that a real user was served a flag. Evaluating a flag (a "check") is always free and unlimited, whether you evaluate one flag or run millions of checks a second. You're billed only for the exposures behind those checks.
Exposures are logged automatically when you evaluate remotely, and are deduped per user, flag, and variant per hour, so a user reloading a hot page counts once an hour, not once per request. That keeps the bill tied to real usage rather than raw traffic, and matches how the larger platforms meter. You can turn auto-logging off per client key, or log exposures yourself from cached evaluation. See Record exposures for the details.
As more products land, each brings its own billable event, and they all meter into the same credit.
Plans
| Plan | Base | Included | Past the allowance |
|---|---|---|---|
| Hobby | Free | A free monthly allowance | Metering stops (events are refused); a single user, a single organization |
| Pro | $50 / month | Your monthly usage | Overage billed at the metered rate |
| Enterprise | Contract | A negotiated envelope | Trued up against the contract |
Pro is $50/mo and includes your monthly usage across every product before any overage. That included usage is shared: every product's events draw from the same allowance, so you're never rationing per-product limits. You pay $50 until your usage exceeds what the plan includes, then only the difference at the metered rate. Your current rate and allowance are always shown on the usage page in the app.
Hobby is a hard cap
The free Hobby tier stops metering once you pass its free monthly allowance:
further exposure ingest is refused with a 403. Flag evaluation keeps working
(checks are always free), only the recording of new exposures stops. You get
warning emails at 80% and 100%, so the cap never arrives unannounced. Upgrade to
Pro to keep recording.
Analytics history (retention)
Every exposure and goal event is metered when you send it, but how far back you can analyze it (flag impact and experiment results) is a plan lever. Hobby analyzes the last 7 days, Pro the last 30 days, and you can buy extended retention or run Enterprise for a custom window. Sending the data is never wasted: widen the window (upgrade or add retention) and past history becomes analyzable again, so you can even spin up an experiment long after a rollout went live and see it instantly.
Watching your usage
The console's Usage page shows the current cycle: a breakdown by product, flag, environment, and evaluation reason, plus where you stand against your allowance. Read the same numbers from the API:
GET /v1/orgs/{org}/usageIt returns the usage breakdown and an entitlement object with your plan, the
included and used events, and any overage. Any member can read it.
Managing your plan
| Action | Endpoint |
|---|---|
| Start a Pro checkout | POST /v1/orgs/{org}/billing/checkout |
| Read the billing summary | GET /v1/orgs/{org}/billing/summary |
| Open the billing portal | POST /v1/orgs/{org}/billing/portal |
Checkout and the billing portal are handled by our payment processor; Flagon never sees full card numbers. A lapsed Pro subscription locks the organization's management surface (with a reactivation prompt) rather than silently downgrading it, so nothing is lost while you sort out billing.