Usage & cost

The Usage page in the Console answers one question first: what will this month cost? It leads with money — the unit you actually think in — and keeps the quantities underneath. Billing and payment live next door on the Billing page; Usage is what you consumed.

Usage is visible to Org owners and admins (the same access that sees billing).

What you see

• A headline. For the current month, month to date and a projected end-of-month total. The projection prices the rest of the month from what you’re running right now, so a resource you created mid-month is counted for the days it will actually run — not smoothed away. It’s an estimate, and labeled as one.
• A daily cost chart — one bar per day, split by product family. The last bars are drawn faded while the day is still accruing, so a partial day never looks like a drop.
• A breakdown, grouped family → product → resource. Each cluster, Network, Stack, or instance shows its own lines; org-wide products (like On-Call) show one set of lines. Every line names what set its rate — a control plane’s tier and replica count, a monitor’s interval and vantages.
• Free allowances, shown as progress. If your plan includes a monthly free amount — the first sends on Email, a floor of Uptime monitors — you’ll see how much of it you’ve used, and the line flips from free to a cost once you cross it.

Prices are applied when the page loads, from the current price list. A line reading “—” is metered but not yet priced during the beta; it appears on your invoice at €0.00.

Estimated vs. invoiced

While a month is open, every number is an estimate — the current prices applied to the usage so far. Once we issue the invoice for a closed month, that invoice becomes the number the page shows: the headline reads Invoiced, links to the Billing page, and the lines come from the invoice itself. The page never shows a recomputed estimate that could disagree with what you were charged.

Export the detail (CSV)

The page shows the summary; the Download CSV button gives you everything. The export is one month at full detail — one row per day, per resource, per dimension, per qualifier — ready to drop into a spreadsheet for showback or reconciliation.

The column schema is stable: we only ever add columns, never rename or reorder them, so a spreadsheet you build against it keeps working.

Column	What it holds
month	The calendar month, YYYY-MM.
day	The calendar day, YYYY-MM-DD.
day_status	final (settled) or open (still accruing today).
family	Product family, such as Infrastructure, Reliability, Delivery.
product	Product, such as Control Plane, Uptime, Registry.
resource	The specific resource (cluster, Network, Stack, instance); empty for org-wide products.
resource_deleted	true if the resource was deleted but still billed for the month.
dimension	The metered dimension key, such as control-plane, bandwidth, email-sent.
qualifier	The dimension’s attributes as key=value;key=value, such as tier=medium.
quantity	The metered amount for that day, in unit.
unit	The unit of quantity, such as cluster-hours, bytes, emails.
unit_rate_eur	The per-unit price applied (blank while unpriced).
multiplier	Per-unit multiplier such as replicas or vantages (blank for informational rows).
estimated_cost_eur	Indicative cost for the row — see the note below.
informational	true for metered-but-never-billed rows (CPU, memory).

The cost column is indicative. estimated_cost_eur is a gross per-day figure: monthly free allowances are applied when your invoice is issued, not spread across rows, so the column won’t sum exactly to your invoice. For the authoritative amount, use the invoice.

Next

• Open the Billing page for invoice history, your payment method, and billing contacts.
• Access control — who in your Org can see Usage and billing.