Billing and metrics
Storage, key-value, and worker runtime are billed continuously from your account balance.
AnythingCloud billing is account-level. The Billing page shows the current cost, the expected month-end total, the service split, and a six-month spend chart. Charges are debited as they accrue, not as one bill at the end of the month. Prices in this guide are in USD; the console shows them in your display currency.
Pay as you go
Pay-as-you-go buckets are charged on the bytes actually stored. The default rate is $0.03 per GB per month, charged continuously. There is no storage cap: a bucket that stores 10 GB for a full month costs about $0.30, and a bucket that stores 10 GB for a day costs about $0.01.
Charges follow the storage you actually have, so deleting objects lowers the next charge.
Workers
A running worker is billed by the hour, scaled by its Memory setting. The default 128 MB size costs $0.0025 per hour; 64 MB costs half that, 256 MB double, and 512 MB four times as much. Prices are shown in your display currency in the console.
Only workers in the live state accrue runtime. Paused, draft, ready, and error workers do not. Worker requests, schedules, and object events do not have a separate per-request charge; KV operations are billed separately below.
Key-value storage
KV namespaces are billed on live bytes at $0.50 per GB per month, whether or not a worker is bound. Operations are billed per million: reads $0.50, writes and deletes $5.00, and lists $5.00. Storage accrues continuously, and operations are counted per namespace per day. Deleted or expired bytes stop counting toward storage. Keys keep accruing storage while no worker is bound or running. The operator can change these rates.
Monthly storage plans
A monthly plan is a flat price for a storage quota. The price does not change with the amount of the quota you use, and it is debited continuously over the month. The console enforces the quota on uploads; S3 API writes are not capped by it.
| Storage | Price |
|---|---|
| 5 GB | $1.00 / month |
| 100 GB | $3.00 / month |
| 250 GB | $5.00 / month |
The plan price is fixed when the bucket is created. If the site operator changes the published prices, existing buckets keep the price they were created with; new buckets use the current price.
Choosing a mode
- Pay as you go is better when usage is small, variable, or short-lived.
- A monthly plan is better for a predictable amount of storage and a lower flat price.
The Create bucket page shows the current rate and plan prices before you create anything.
Monthly budgets
Open Billing → Budget to create one budget per scope: All AnythingCloud, Workers, Object storage, or KV store. Each budget has its own limit, alert percentage, and hard-cap choice:
- Alert only. A warning appears in Billing and on the budget card when spend crosses the alert percentage. Services keep running.
- Hard cap. When that scope reaches its limit, AnythingCloud pauses the account. Raise the limit and resume to restore service.
The Overview chart shows a line for the all-services budget and a chip for every budget with its current spend. A limit of 0 removes that budget. Budgets use the same continuous spend figure shown as the current cost.
Pausing
If the balance cannot cover a debit, AnythingCloud pauses the account. Public access is removed from buckets, the edge stops routing them, and workers stop. Add funds and choose Resume on the Billing page to restore service. Charges stop while the account is paused.
Enabling AnythingCloud for the first time also requires a positive balance. A negative or zero balance shows an Add funds action instead of the enable button.
Metrics
Each bucket has a Metrics tab with three ranges: 24 hours, 7 days, and 30 days. It shows:
- Storage over time, from hourly bucket scans.
- Reads and writes, counted at the edge from request methods (GET/HEAD are reads; PUT/POST/DELETE are writes).
- Current stored bytes, object count, and totals for the selected range.
The meter runs every few minutes. Storage samples are captured by the hourly usage scan. Request counts are collected from the edge access log and can lag by a minute or two. Signed requests are counted as reads or writes.
Workers have their own Metrics tab with request counts, errors, average duration, egress, and the edge map for the same ranges. Worker logs are separate from metrics.
Billing page
The billing page is account-level, not bucket-level. It shows the balance, current cost, expected month-end cost, the billing period, a service breakdown, a six-month spend chart with a hover read-out, the active budgets, and the worker runtime summary. Per-bucket storage and request details are on each bucket's Metrics tab; per-worker details are on the worker's Metrics tab.