Usage and Costs
Track current-period usage before it becomes a finalized invoice.
Compute usage
Section titled “Compute usage”Compute is billed from resource-hours across the billing window:
- CPU in core-hours
- memory in GiB-hours
- storage in GiB-hours
In practice, that means billing follows the resources your clusters are allocated over time. Unused plan headroom is not billed.
Compute formula
Section titled “Compute formula”resource quantity x hours x hourly rateCurrent compute rates:
| Resource | Rate | Monthly equivalent |
|---|---|---|
| CPU | £0.030/vCPU/hour | £21.90/vCPU |
| Memory | £0.006/GiB/hour | £4.38/GiB |
| Storage | £0.000116/GiB/hour | £0.085/GiB |
Example
Section titled “Example”If a cluster is allocated 4 vCPU, 16 GiB memory, and 100 GiB storage for a full hour:
(4 x 0.030) + (16 x 0.006) + (100 x 0.000116) = £0.2276/hourObservability usage
Section titled “Observability usage”Each plan includes an observability allowance. Kupe tracks two things for billing:
- metrics usage by active-series P95 over the billing period
- logs usage by total ingest volume over the billing period, measured as uncompressed bytes received
Usage within the included allowance is covered by the plan.
If overage remains enforced, the allowance acts as a hard limit and no overage charge is added.
If a tenant admin allows overage, usage above the included amount is billed at the flat overage rates.
Overage rates
Section titled “Overage rates”| Resource | Rate |
|---|---|
| Metrics active series | £0.003/series/month |
| Log ingest | £0.30/GB/month |
Overage formula
Section titled “Overage formula”max(0, actual usage - included allowance) x unit rateHigh Availability
Section titled “High Availability”Clusters with High Availability enabled run a replicated control plane, billed per hour while HA is enabled:
| Resource | Rate | Monthly equivalent |
|---|---|---|
| HA control plane | £0.0205/cluster/hour | ≈ £15.00/cluster |
HA hours are metered like compute: you pay only for the hours HA was actually enabled, and disabling HA or deleting the cluster stops the meter. Hours accrued before a mid-period deletion are still included on your next invoice.
What you see in the console
Section titled “What you see in the console”The console splits this across two views:
- Usage shows your current pool usage, included observability allowance, and whether overage is allowed
- Billing shows the current-period estimate, breakdown by cost category, and completed invoices
If your plan changes during the billing period, the current-period estimate reflects the prorated result across the affected plan windows.
What the current estimate includes
Section titled “What the current estimate includes”The current-period estimate can include:
- compute charges accrued so far
- metrics overage accrued so far
- logs overage accrued so far
- High Availability hours accrued so far
- estimated credits applied so far
It is an estimate until the billing period closes and the invoice is issued.
Next steps
Section titled “Next steps”- Plans and Upgrades: understand what each plan includes
- Invoices and Payments: see how estimates become invoices