Skip to content

Overview

Understand how Kupe Cloud estimates usage, applies credits, and creates invoices.

Your bill is built from:

  • the monthly platform fee for your plan
  • billed compute usage for CPU, memory, and storage
  • optional observability overage when usage goes beyond the included allowance and overage is allowed
  • High Availability control-plane hours for clusters with HA enabled
  • credits, which reduce the amount due before payment is taken

Everything is billed monthly in arrears: after a billing period closes, one invoice covers that period’s plan fee and usage, and your saved card is charged automatically. Nothing is charged at signup — adding a payment method is a £0 checkout that saves your card.

There are two important ideas behind the model:

  • each plan gives you a resource pool and observability allowance
  • billing is based on actual billed usage across the period, not on unused plan headroom

That means unused capacity in the plan is free, while clusters and observability usage are charged as they accrue through the billing window.

Kupe tracks:

  • CPU core-hours
  • memory GiB-hours
  • storage GiB-hours
  • metrics usage by active-series P95
  • log usage by total ingest volume
  • High Availability control-plane hours, for clusters with HA enabled

Those values feed both the current-period estimate and the final invoice.

In the console:

  • Billing shows the current-period estimate, cost breakdown, remaining credits, and invoice history
  • Usage shows your plan pool, current allocations, observability allowance usage, and overage policy
  • the same compute unit rates apply across plans
  • plan changes take effect immediately and are prorated by the day — each plan is billed for the days it was active
  • credits reduce the invoice total but do not increase plan limits
  • amounts shown in Kupe exclude VAT — Paddle, the Merchant of Record, applies tax at payment
  • Enterprise uses custom plan configuration rather than preset limits