Usage & allowances
Alongside credits (which fund AI features), every plan includes generous monthly allowances for platform usage — the GitHub model: use what's included for free, and nothing is billed beyond it unless you explicitly turn overage on.
The included allowances
Each allowance covers one usage meter and resets on the 1st of every month (UTC). Launch allowances by plan:
| Meter | Unit | Free | Pro | Business | Enterprise |
|---|---|---|---|---|---|
| Runs | runs | 500 | 5,000 | 25,000 | Unlimited |
| Log ingestion | GB | 1 | 10 | 50 | Unlimited |
| Object storage writes | GB | 1 | 10 | 100 | Unlimited |
| Custom events | events | 30,000 | 300,000 | 3,000,000 | Unlimited |
Live positions — including a projection of where the month is heading — are on Settings → Billing under Usage & allowances.
When an allowance runs out
What happens next is governed by your monthly spending limit, which defaults to $0:
- Spending limit $0 (the default) — the allowance is a hard stop. Usage of that meter pauses until the next monthly reset (or until you raise the limit). You can never be billed for overage you didn't opt into.
- Spending limit above $0 — usage continues past the allowance and overage is billed to your subscription, up to the limit per month. Raising the limit requires a paid plan, since overage is collected through your subscription's payment method.
Overage prices
Overage is metered transparently at public prices:
| Meter | Overage price |
|---|---|
| Runs | $2.00 per 1,000 runs |
| Log ingestion | $0.50 per GB |
| Object storage writes | $0.25 per GB |
| Custom events | $1.00 per 100,000 events |
Overage is billed in whole price units (rounded up), accrues against your spending limit during the month, and is collected on your next subscription invoice after the month closes. Each month's itemized position is kept as an allowance statement, visible in the same panel.
Threshold notifications
The platform emits a billing.allowance.threshold event when a meter
crosses 75%, 90%, and 100% of its included allowance. Create a
notification rule for that event type (Settings → Notifications) to get an
email or Slack message with the current position and a link to the meters
panel — each threshold fires once per cycle, so a steady position never
re-pings.
Allowances vs. credits
The two systems are deliberately separate:
- Credits (opaque, prepaid) fund AI work — agent sessions, the workspace assistant, blueprint bootstraps.
- Allowances (transparent, included) cover platform usage — runs, logs, storage, events — with public overage prices.
A spending limit never draws from your credit balance, and credits are never consumed by allowance overage.