Skip to content

Billing

You buy cores and memory by the hour. Prices are not chosen by hand — they are computed from a published rule, recomputed every run, so the answer to “why does this cost that” is a calculation you can check.

User guide What you are charged for and what you are not, how a price is arrived at, when money actually moves, and where to read the bill.

Developer guide Reading prices and usage from code — the public price endpoints, month-to-date cost, the rated rows behind a total, and the rounding rule that makes small periods bill nothing.

How prices are set The rule in full: the cheapest current-generation equivalent at least as large, less twenty per cent, in euros — and the families deliberately excluded from the comparison.

How a period is billed The guarantees behind your invoice — one row per hour, frozen once billed, never billed twice, and what happens when a rate changes after the fact.

Metering and invoicing The chain from what runs to what you are invoiced, its hourly cadence, and the tenant rule that ties your resources to your bill.

Catalog and availability The public shop-window endpoints, field by field, including how inStock is computed live from real capacity.

Instance types — what each shape is, since the shape is what is priced.

Quotas and limits — the ceiling on what you can run up.

Account API — the billing portal link and the usage call.