Budgets that pause.
Nothing is deleted.
Set a budget on an account, an organization, a project or a service. It alerts on actual and forecast cost, and with a cap Frazer pauses its own compute in that scope at 100 %. Workloads on your servers, databases and data keep running.
From metered usage to a pause.
Checked every 5 minutes.
Frazer meters usage itself: your servers by the hour while they are accepted, fleet resources by the second. Each hour is rated against your price book into cost lines, and budgets are checked every 5 minutes on estimated cost, so an alert or a cap acts before the invoice does.
What a cap pauses.
And what it never touches.
At 100 % of a capped budget, Frazer pauses what this table says and nothing else. Running out of prepaid credit and a failed payment use the same pause.
| In the capped scope | At the cap | Data |
|---|---|---|
| Workloads on your own servers | Never stopped. Only new billable items are refused: rentals, fleet resources, more servers. | Untouched |
| Rented servers | Never powered off during the paid term; new orders are refused. | Untouched |
| Frazer-run compute | Stopped: agent sessions suspend, runner jobs stay queued, devboxes and GPU pods stop, and LLM gateway calls are refused with a plain message. A training job writes a checkpoint first when it can within 5 minutes. | Volumes, snapshots and checkpoints kept at least 30 days |
| Serverless endpoints | Scale to zero; requests get HTTP 402 with a plain message. | Models and caches kept |
| Buckets, volumes, backups | Keep serving. Writes are blocked only after 30 days past due, and deletion needs a separate 30-day notice. | Kept |
| Monitoring above the allowance | Sampled down to the allowance; alerts are never dropped. | Kept |
Every enforcement is recorded with the resources it touched, in the audit log and as a banner on each paused resource.
One account, many organizations.
Rights on both sides to link.
A billing account sits outside your organizations. One holding account can pay for Acme and Pellwyn, with an invoice section for each, while the two stay separate organizations.
- Owned by one, pays for any
- One organization owns the account, and it can pay for projects in any organization. An organization may exist only to hold billing accounts.
- Rights on both sides
- Linking needs a right on the account and a right on the project. The plan says what the payer will see: cost lines, never resources.
- One account at a time
- Every project has exactly one billing account, and each cost line keeps the account that paid for it.
- Unlinking pauses, never deletes
- A project left without an account is paused like a capped one until you link it again.
- Servers bill where they live
- Server fees go to the project that holds the servers; one currency per account, in US dollars.
Budgets in one command.
Every change a plan first.
The CLI, the API and the console call the same methods, and each change can show its plan before it applies. An agent may prepare a link; only a person applies it, and no agent can lift a cap.
# Alert at 50, 90 and 100 % and on the forecast; pause at 100 %
$ frazer billing budgets create --account 01F3A2-7C9B4E-D2851A \
--project acme-staging --amount 500 \
--thresholds 50,90,100,100:forecast --cap pause
# Lift it, with a reason the audit log keeps
$ frazer billing caps lift <budget> --reason "approved overrun"# Needs a right on the account and one on the project; --dry-run shows what the payer will see
$ frazer billing projects link acme-production \
--account 01F3A2-7C9B4E-D2851A --section "Acme" --dry-run
$ frazer billing orgs set-default acme --account 01F3A2-7C9B4E-D2851A --dry-run$ frazer billing costs query --account 01F3A2-7C9B4E-D2851A --month 2026-11 \
--group-by org,project,service --format=json
# Hourly FOCUS files, as Parquet, to a bucket you pick
$ frazer billing export set --account 01F3A2-7C9B4E-D2851A \
--bucket s3://holding-billing --format focus-parquetOne bill you can read.
Down to the SKU.
Accounts across organizations
One billing account pays for projects in any organization you choose.
Invoice sections
Acme and Pellwyn as two sections of one invoice.
Budgets on any scope
An account, an organization, a project, a service or a label; a fixed amount or last month’s spend.
A cost table that equals the invoice
One invoice month, project › service › SKU, credits and tax per project, to the cent.
Reports and forecast
Cost by day or month, by organization, project, service, SKU or label; list and net; CSV.
Usage export
Hourly files in the open FOCUS format, as Parquet, to a bucket you pick.
Credits and commitments
Free tier, promotional and prepaid credit; spend commitments pooled across the account.
Card, ACH or invoice
Card details go straight to our payment processor and never touch the Frazer API.
Who pays, who caps, who lifts.
With the defaults stated.
Who may do what
- Billing Account Administrator
- Payment methods, invoices, export, budgets and caps, links and roles on the account. No project resource.
- Costs Manager
- Budgets, caps and lifting them, reports and export. No payment methods, no links.
- Billing Account User
- Links projects to the account, together with Project Billing Manager on the project.
- Billing Account Viewer
- Reads costs, credits, invoices and prices.
- Agents
- Read-only billing tools. Never lift a cap, change a payment method or link an account.
What is logged
- Every cap enforcement, with the resources it paused, who lifted it and why; a banner on each paused resource.
- Every link and unlink, with the account that paid each cost line.
- A price book other than the list price needs two Frazer staff approvals, in the audit log.
- Corrections are reversal rows, never edits; a closed month is corrected by a credit on the next invoice.
At the cap
- Default alerts at 50, 90 and 100 % of actual spend, and at 100 % of the forecast.
- Checked every 5 minutes on estimated cost, so alerts and caps act before the invoice does.
- A cap is a pause, not a ceiling on the bill: usage in the minutes before the pause lands is billed as usual.
- At 100 % of a capped budget, Frazer-run compute pauses and new billable items are refused. Nothing is deleted.
- Lifted with a reason; service is designed to resume within 5 minutes.
- A failed card payment: 7 days of grace, then the same pause.
Every price is public.
Readable before you sign in.
Frazer rates every hour of usage against one price list, and anyone can read it without signing in. Every price and the estimator are on the pricing page.
See every priceBilling and budgets, answered.
Does a cap ever delete anything?
No. A cap pauses Frazer-run compute and refuses new billable items in its scope. Volumes, snapshots and checkpoints are kept at least 30 days, storage keeps serving, and deleting stored data needs a separate 30-day notice.
Will a cap stop my production database or my own servers?
No. Databases, disks and everything on your own servers keep running, and rented servers stay on through their paid term. A cap pauses only fleet compute: runners queue, agent sessions suspend and serverless endpoints scale to zero.
Can one account pay for several organizations?
Yes. An account is owned by one organization and can pay for projects in any organization, with an invoice section for each. Linking needs a right on the account and a right on the project, and the plan says what the payer will see: project names, services, SKUs and labels on cost lines, never resources.
How current are budgets?
Budgets are checked every 5 minutes on estimated cost: the hours already rated, plus the usage since then, priced at your price book. Estimates are labeled as such until the month closes. Because a check runs every few minutes, a capped budget can end a little above its amount: usage before the pause lands is billed.
Who can lift a cap?
A Billing Account Administrator or a Costs Manager, with a reason. An agent never can. Service is designed to resume within 5 minutes of the lift, and both the pause and the lift are recorded with the resources they touched.
Does the cost table match the invoice?
Yes, to the cent. The PDF has one line per product family per invoice section; the attached cost table has every project, service and SKU behind it, with credits and tax per project.