Skip to content

Credits and billing

What credits are, the three ways to get them, and what happens to a running workload when they run out.

Usage is metered in credits. Your balance is per-account, and every change to it is written to an append-only ledger — the balance you see is the running sum of that ledger, not a number edited in place. Nothing moves without a row recording why.

Getting credits

A redeem code. An operator issues a code; you enter it in Wallet and the balance moves immediately. The code’s text is shown to whoever created it once and never stored, so a lost code cannot be recovered — only reissued.

A card. Wallet takes a payment and credits the balance when the payment confirms.

Auto-recharge. Optionally, top up by a fixed amount whenever the balance falls below a threshold you set, so a long-running workload does not stop because nobody was watching the number.

How it is spent

Workloads deployed from a template that carries an hourly rate debit per minute, for as long as they run. A stopped workload costs nothing — that is the difference between Stop and Delete, and the reason Stop exists.

Storage is not billed today.

Published rates are not available yet. The console shows what your own workloads have consumed; what a given template costs is a question for whoever operates your platform.

Running out

When the balance reaches zero, running workloads are stopped automatically — scaled to zero, not deleted. Configuration, namespaces and any stored data are untouched.

Top up and resume, and the workload comes back at the replica count it had.

Auto-resume does that step for you: turn it on in Wallet and workloads stopped for lack of credits restart by themselves once the balance recovers. Paired with auto-recharge, an overnight run does not end because a number hit zero at 03:00.

The stop is durable rather than best-effort. If the platform cannot reach the cluster at the moment it needs to stop something, billing pauses immediately and the stop is retried until the cluster confirms it. You are not charged for the gap, and a workload does not quietly keep running for free either.

The ledger

Wallet shows every transaction: grants, top-ups, per-minute usage and any adjustment, each with its reason.

This is the record to reach for when a balance is not what you expected. It is append-only — a correction appears as its own entry rather than by editing the one that was wrong — so the history is always complete.

If a payment is disputed

While a chargeback is open on your account, new credit purchases are refused and the console says so. Redeem codes still work. The hold lifts by itself when the dispute closes.