On-premises rate cards
Price clusters that have no cloud bill, with unit rates per node pool or amortized hardware cost.
Who does what
How data center clusters are priced
- 01
Prices
Rate cards per node pool or label (vCPU-hour, GiB-hour, GPU-hour, storage GiB-month), or hardware purchase price over a depreciation period plus power, space and support.
Your rate card
- 02
Cluster snapshots
A cluster token from KubeOn, in a Kubernetes Secret. Snapshots go to your organization in KubeOn and nowhere else.
Agent in each cluster
- 03
UnitVane
Outbound HTTPS from each cluster to KubeOn, which runs everything else. No inbound port.
Managed by KubeOn
- 04
Allocate + reconcile
The hub joins hourly snapshots with your rates and allocates each node's cost to the pods, teams and labels that ran on it.
KubeOn hub
The KubeOn agent never changes your clusters. Snapshots leave over outbound HTTPS only.
On this page
Rate cards
A rate card prices capacity by node label or node pool. Rates are effective-dated: a new card applies from its effectiveFrom date, and earlier days keep the rates they were allocated with.
# rate-cards/dc1-standard.yamlapiVersion: kubeon.io/v1kind: RateCardmetadata: name: dc1-standardspec: currency: USD effectiveFrom: "2026-01-01" # Option 1: unit rates, per node pool or node label rates: - match: { nodeLabel: "node.kubernetes.io/pool=general" } vcpuHour: 0.0312 memoryGiBHour: 0.0041 - match: { nodeLabel: "node.kubernetes.io/pool=gpu" } vcpuHour: 0.0312 memoryGiBHour: 0.0041 gpuHour: 1.18 storage: - storageClass: ceph-rbd gibMonth: 0.06 # Option 2: amortized hardware, spread across the nodes it covers hardware: - match: { nodeLabel: "kubeon.io/rack=r12" } purchasePrice: 184000 depreciationMonths: 48 monthly: power: 1450 space: 900 support: 610Hardware amortization
Instead of unit rates, give KubeOn what the hardware cost. It spreads the purchase price over the depreciation period, adds monthly power, space and support, and divides the result across the nodes the entry matches, by their CPU and memory capacity.
Assign a card to a cluster
Name the card in the agent values with pricing.rateCard, or map it to clusters in Settings > Rate cards. A cluster with no card shows inventory and usage but no cost, and Diagnostics flags it.
What changes compared with the cloud
- Reconciliation compares allocation with the rate card total instead of an invoice.
- Network transfer cost uses the per-GB rate on the card, if you set one.
- Node sizing proposals compare node pools by the rates you defined.