Billing & usage

What is metered

Four Meters, one price list for every plan:

Never metered: collection (the SDKs, capture, replay, Reporters), the queue, Handoff, dispatch Runs, and tokens on your own key or subscription. Seats are free — invite the whole team.

• The Brief rate follows the analysis model an Owner picks in Settings → Automation: a Brief written by Claude Opus 5 or GPT-6 Astra is rated at the frontier rate.
• Every hosted Run bills its sandbox minutes — a fix Run, a Retry, an environment check, and a Run that fails or is cancelled alike. There is no per-Run fee, and time spent waiting at the review gate is never sandbox time.
• A Run on your own key or subscription bills only its sandbox minutes. Its tokens are recorded so Usage can show them, but they are never billed.

Plans

• Free is where every new workspace starts: $5 of usage to try the whole product — Briefs and hosted Runs included — granted once, with no card.
• On Pro and Team the Included usage renews on the 1st of each month and never rolls over. Tokens on Fixback's key are never covered by Included usage.
• Scale is a yearly commitment with a volume discount — Talk to us at hello@fixback.dev.

On-demand usage and the cap

Past its Included usage, a workspace keeps working at the same rates — on-demand usage — up to an on-demand cap the Owner sets. Each plan starts with the default cap above; Edit cap on Billing changes it (up to $100,000). Without a card on file the cap is $0: the Included usage is all a workspace can spend until someone adds one.

When usage reaches the cap, the workspace's spend gate closes. It also closes when there is no card and the Included usage is spent, or when an invoice stays unpaid. While it is closed:

• New Briefs pause. The Issue is still filed with its Evidence, grouped with repeats of the same error, and pointed at its code area — only the model-written parts wait. It reads Brief paused (spend cap), with a line naming what lifts the pause and which Owners can.
• New hosted Runs are refused — Ship, Retry and the environment check say New hosted Runs are paused (spend cap), before the Ship dialog even opens. Regenerating a Brief is refused too, and the current Brief stays.
• A Run that is already running finishes.
• Collection, the queue and Handoff never pause. Reports keep arriving and you can still hand an Issue to your own agent or dispatch a Run to it.

The gate reopens when an Owner raises the cap, adds a card or settles the invoice, when the plan changes, or when a new month begins. Paused Briefs are then written on their own — within about ten minutes — with no one having to retry them.

Project caps

On Team and Scale, an Owner can also give each Project its own monthly Project cap — so an agency can hold each client to what it rebills. A Project cap counts all of that Project's usage this month at list rates, its share of Evidence storage included, before any Included usage: the Project's cost on Usage. Included usage stays pooled across the workspace.

• When a Project's usage reaches its cap, that Project's gate closes, exactly as the workspace's does: its new Briefs pause, its new hosted Runs and Regenerates are refused, a Run already running finishes, and collection, the queue and Handoff go on. The paused Issue and the Ship dialog say this project reached its cap, and which Owners can raise it. The workspace's other Projects carry on.
• The workspace's on-demand cap still applies on top: when it closes, every Project pauses, whatever its own cap.
• A $0 Project cap pauses the Project's metered work outright. Raising or removing a cap, or a new month, resumes its paused Briefs.
• Owners are emailed once a month for each Project that pauses at its cap.
• On Free and Pro Project caps can't be set and aren't enforced. Caps set on Team are kept through a downgrade — shown on Billing, each removable — and apply again on a move back.

Settings → Billing

Billing belongs to the workspace's Owners. A Collaborator has no Billing row in Settings; one who follows a link to it sees which Owners hold it.

• The strip — this month at a glance: the Plan (with Change plan), Included usage spent, On-demand usage against the cap (with Edit cap), and what is due so far, with the month's forecast.
• The statement — this month's lines per Meter, updating live, with View usage and a CSV export.
• Project caps — on Team and Scale, every Project with what it used this month against its cap, and Set cap or Edit to change it (Project caps).
• Payment — Add a card, or the card on file; the billing email; the tax ID. Edit opens Stripe's customer portal.
• Invoices — the three most recent, each Paid, Due, Failed or Void; All lists every one, with Pay or View on the page Stripe hosts.

Changing plan

Change plan opens every plan side by side, each with what this month would cost on it. Payments go through Stripe, in US dollars. Until payments are open for a workspace, the dialog shows the estimates and says plan changes open later.

• From Free, a paid plan is Continue to checkout — Stripe Checkout takes the card, and Billing shows the new plan a moment after you return.
• Between paid plans, Switch now, prorated — the change applies at once.
• Back to Free, Switch when the month ends — you keep the paid plan until the 1st.
• Scale is Talk to us.

Invoices and failed payments

A paid plan is invoiced monthly, on the 1st: the plan fee and one line for the month's on-demand usage (the statement carries the split per Meter). When on-demand usage reaches $50 within a month, it is charged early on an interim invoice. If a payment fails, Stripe retries it and nothing pauses — Billing offers Update card. Once the retries run out, the invoice is unpaid and the cap is $0 until it is paid; Pay invoice settles it.

Settings → Usage

Usage is every Member's, not only the Owners'. It shows what the workspace used, per Meter and per Project:

• a Project filter (All projects by default) and a date range — month to date by default, with presets or a custom range;
• a tile per Meter — Briefs, Sandbox minutes, Model tokens, Evidence storage — and a chart of cost or of any one Meter over the range, with the month's forecast;
• a By project table with each Project's cost and mix — on Team and Scale, for a range inside this month, its Cap instead: what it used this month against its Project cap, the bar turning amber when the month's forecast nears it and red at it.

Every usage event is stamped with its Project when it is recorded, so the per-Project split — and the statement's CSV — is what an agency needs to rebill each client. The view lives in the URL, so a link reopens the same range and filter.

The Founding 100

The launch offer: Pro free for 12 months — its $35 of Included usage every month, with on-demand usage billed normally. Apply on fixback.dev; an accepted application gets a claim link. The slot is confirmed once the workspace is live — the SDK installed and a first Issue in — within 14 days, or it goes back to the pool. When the 12 months end, the workspace moves to Free, or stays on Pro at $19/month if a card is on file.

Workspaces in the beta

Workspaces created before billing existed stay in the beta. Their plan reads Beta · $0: usage is recorded and shown at list rates on Billing and Usage, but nothing is billed, nothing pauses, and no billing email is sent. A workspace in the beta can't claim a Founding slot — claim it for a new workspace instead.