Every number PaaSbox Clusters holds you to, in one place, grouped by subject. Each row says where the limit comes from, so you know whether to change your request, ask me, or wait.
10 at once, more on request. Clusters being deleted, deleted or detached do not count. The create page says when the team has reached them; ask for a higher limit.
The portal, before create
Servers per cluster
1: single node is the only topology offered
The create form
API keys
25 active keys per team, created by a team admin In progress
The API keys page
An API key’s lifetime
30 days, 90 days (the default), a year, or no expiry In progress
The API keys page
Creating a cluster while an invoice is unpaid
Refused until the payment method is updated In progress
Lower-case letters, digits and hyphens, at most 32, no hyphen at either end; unique in the team; made from the name when left empty; cannot change later
The create form
The Kubernetes API’s name
<DNS label>.<team>.k3s. followed by PaaSbox’s zone
CPX and CCX (amd64), CAX (arm64) In progress. No CX: the CX line boots with BIOS only, and the node image needs UEFI.
The create form; an adopted CX server is refused
Server types offered
Those Hetzner sells in the chosen location, not deprecated, for an architecture the release has an image for. The list is read from your project and kept for 10 minutes.
The create form
Memory a fresh cluster uses
1.2 GiB of a cpx22’s 3.8 GiB, measured in a lab on 2026-10-10
—
Memory per add-on
The estimates in the add-on catalogue: 50–150 MiB for each of the first six, 170 MiB for Flux, 150–1230 MiB for the PaaSbox Platform
The portal adds them up
Smallest server for an add-on
PaaSbox Platform: 4 GB; 8 GB for the profiles saas-http01 and saas with observability. No other add-on has one.
