CONSOLE V1 / CUSTOMER GUIDE

Costs and operational status

What is estimated, measured, billed or unavailable.

Cost API boundary

GET /api/v1/costs is operator-only and reads a fixed server-configured JSON snapshot, schema log-salad-cost-inventory-v1, maximum 1 MiB. A snapshot tenant_id must match the session tenant. No path comes from the request. The API makes no provider inventory or billing calls. Unreadable, oversized or invalid configured snapshots fail explicitly.

Four different claims

Estimated: a model based on assumptions and usage inputs, not a bill. Observed: measured inventory/usage at a stated time and scope, not automatically billing truth. Billed: explicitly sourced billing evidence for a stated period, not an extrapolated estimate. Unavailable: not connected, missing or unknown—not zero. The labels are provenance categories; they are not a claim that every snapshot has all four, or a new enum enforced on every snapshot field.

Default is unavailable

Without a configured snapshot the response has as_of:null, clusters:[], summary:{status:unavailable} and a limitation that cloud inventory and billing are not connected. An empty list is not free infrastructure. Keep unknown resources separate from known totals, and show the snapshot timestamp before comparing values. Budget communications are not connected; no automated email, webhook or provider budget enforcement is promised.

Plan the whole resource lifecycle

Evaluate compute, retained block volumes, object bytes/requests, archive maintenance, data transfer and private endpoint hourly/data processing charges. Stopping idle compute can leave storage and endpoints billable. Set an approved evaluation budget, owner, duration and manual stop/review plan. Prices and savings depend on approved deployment scope; this website publishes no fixed price or cost guarantee.

Status is evidence

Overview counts and lane status belong to the private console, not this static website. not_observed, unavailable, pending and outcome_unknown must remain visible. No live badge is derived from a rendered diagram. Inspect persisted operation receipts, sink evidence and timestamps before asserting health or completion.