Billing & limits

Ozone separates capacity from consumption. Usage is metered at the same rate on both tiers and billed monthly; a plan buys throughput, seats and support, and nothing else. No paid plan bundles a recurring usage allowance — you pay the Pro fee, if selected, plus what you actually ran.

Usage is measured in dollars. Every run reports its billable cost, and the figure Ozone shows is the figure that reaches your invoice.

Getting started#

Every team starts on Standard, which has no monthly fee. Connect your first repository and you get $100 of review credit for 30 days — no card required. The credit arrives at that first connection, not at sign-up, and it does not renew. Ozone grants one per GitHub user or GitHub organization, so creating another workspace won't earn either identity a second one.

When the credit is used or expires, reviews pause. Add payment details and Standard carries on — you are billed monthly for the usage you run, at the same rate Pro pays. If you subscribe within the 30-day window, remaining credit is applied before the first usage charge.

Standard gives three seats, two runs at once and 20 review runs in a rolling 24 hours, with or without a card. There is no queue: a review that cannot start right away is skipped rather than held, so a burst of pull requests beyond your two slots goes unreviewed. Capacity is what Pro adds.

Plans#

Both tiers pay the same for usage. Paid Standard is one metered usage subscription; Pro is a capacity add-on on that same subscription, with more parallelism, a queue, more seats and priority support. There is only one billing cycle and invoice.

Agent usage is billed on the same monthly invoice as the subscription. Admins change plan from Settings → Plan & billing; Stripe’s portal handles payment methods, invoices and cancellation.

Some models carry a separate long-context rate. Ozone applies the rate to each request by its input size and records the cost on the run and usage pages.

Delete a project or repository and Ozone stops new work at once, then keeps it recoverable for 30 days. Review, activity, and billing records remain after that window.

Spend limits#

Once you have payment details on file you get a monthly spend limit — a brake, not a quota. Reach it and new runs stop starting until the month rolls over or an admin raises it. Nothing else changes. Standard defaults to $500 and Pro to $1,000; admins adjust either from Settings → Plan & billing, up to $10,000. Need more? Contact us.

Before you add a card there is nothing to brake: your remaining credit is the wall, so the control stays hidden.

Spend alerts email the owners and admins when spend crosses a share of that limit — on by default at 80%, adjustable or off. They apply once you are being billed, where the limit is what stops you.

Before that, two emails can reach you about the credit itself. One goes out about a week before any unspent credit expires, so a deadline never passes unseen. The other arrives when you spend the last of it: reviews pause, and adding payment details resumes them. Credit that expires unspent also pauses reviews, but sends no email of its own — the lapse is recorded in your activity log instead.

Queues and review limits#

On Pro, two limits make work wait rather than fail:

• Runs at once. Above your plan's ceiling, a Pro run sits queued until a slot frees up. Standard has no queue — see below.
• The rolling 24-hour allowance. This counts automatic PR reviews, manual reviews, and scheduled analyses started in the preceding 24 hours. Answers to @ozone questions and assistant turns don't count. Nothing resets at midnight — a slot returns exactly 24 hours after the run that took it started.

Two reject the run outright:

• No room to start. Pro can hold 20 runs waiting behind its 10 slots. Standard holds none: at two runs at once, the next one is refused rather than queued. The platform's own queue can also be full.
• No money to spend — spent credit, lapsed billing, or a reached spend limit.

Ozone checks the platform queue, then billing, then your queue, then your balance.

When a run cannot start:

• Dashboard, API, and Run now: the request gets HTTP 429 with error: limit_exceeded, a reason, and the limit. A scheduled run is skipped and logged instead.
• Automatic PR reviews: GitHub gets a successful webhook response and Ozone records the skip. When you can act on the cause — spent credit, lapsed billing, a reached spend limit, or a full queue of your own — Ozone posts one explanatory note on the PR as it opens, reopens, or leaves draft. A full platform queue passes in silence, and repositories set to dashboard-only get no note either way.
• PR mentions: Ozone reacts with 😕.

A skipped review creates no Ozone check run: that check appears only once a review starts.

When payment fails#

A failed renewal doesn't cut you off overnight. Stripe retries, Ozone emails the admins, and the org keeps working for a two-week grace period. If payment still can't be collected, reviews pause until you sort it out.

Watching your usage#

Settings → Usage shows this month's spend, what it went on, and which project it came from, and every run page shows its own billable cost. Assistant turns are billed the same way and count toward the month's total, though those breakdowns cover runs only. The assistant answers usage questions too — "what did we spend this month, and on what?"