Skip to content
Kupe Cloud Kupe Cloud Kupe Cloud Docs

Overview

Kupe Cloud billing is designed to stay predictable. Your monthly total is made up of a small number of components, and the console shows both the current-period estimate and your completed invoices.

What makes up the total

Section titled “What makes up the total”

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
  • credits, which reduce the amount due before payment is taken

The core billing model

Section titled “The core billing model”

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.

What the platform measures

Section titled “What the platform measures”

Kupe tracks:

  • CPU core-hours
  • memory GiB-hours
  • storage GiB-hours
  • metrics usage by active-series P95
  • log usage by total ingest volume

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

Where to check billing

Section titled “Where to check billing”

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

Important billing behavior

Section titled “Important billing behavior”
  • the same compute unit rates apply across plans
  • plan changes inside a billing period are prorated in the estimate
  • credits reduce the invoice total but do not increase plan limits
  • Enterprise uses custom plan configuration rather than preset limits

Pages in this section

Section titled “Pages in this section”