Billing
Four meters, no seats, and a card-less start.
View as MarkdownYou are billed for what you store and move, on four meters. There is no per-seat charge and no plan tier that gates features.
A new workspace starts with credit against real usage and needs no card.
Pricing
The four meters and what each costs.
Usage
Reading what you have actually used.
Credit
The signup credit, coupons and discounts.
Limits
Quotas per plan, and what happens at one.
Payment methods
Adding and changing a card.
Invoices
What you were charged, and when.
The shape of it
| Metered | Computation, storage, archive, transit |
| Not metered | Members, workspaces, backups, API calls, runs |
| Billed | Monthly, in arrears, against usage |
| To start | No card. A one-time credit against real usage |
Members are capped as a blast-radius limit, not a price. A workspace of one and a workspace of twenty pay the same for the same usage. The member cap exists because permissions are workspace-wide, not because seats are a revenue line.
What actually drives your bill
In rough order of impact for most workspaces:
- Archive, the standing cost of holding artifacts. Bounded only by retention.
- Computation, the time each run spends being processed.
- Transit, bytes leaving us, which is zero unless you deliver to your own buckets or keep a second copy.
- Storage, the short-lived working space during a run.
The first is the one to think about, because it accrues every day for the life of every
artifact. A backup with no expire_after keeps everything forever, and pays for it forever.
Reading your bill
curl -fsS "https://api.saved.sh/v1/workspaces/$WID/usage" \
-H "Authorization: Bearer $TOKEN"Or in the dashboard, under Settings → Usage. Both need billing:read, which is
human-only: a machine key cannot read or change billing.
Billing states
A workspace's state gates writes but never reads.
| State | New runs | Config changes | Reads and downloads |
|---|---|---|---|
trial | Yes | Yes | Yes |
active | Yes | Yes | Yes |
warned | Yes | Yes | Yes |
stopped | No | Yes | Yes |
blocked | No | No | Yes |
Downloads keep working in every state. A workspace behind on payment can still read and retrieve every artifact it has. Your backups are not leverage, and no state removes your access to data you already stored.
What stops is new work: runs will not start, so your backups fall behind while the account is unpaid. The data already there stays reachable.
No fees, no penalties
There are no overage fees, no late fees and no interest. A late fee on an unpaid backup bill collects almost nothing and turns a lapsed customer into an angry one.