Skip to content
PAASBOX PAASBOX PAASBOX

Pricing & fair-use

One flat price per cluster

Section titled “One flat price per cluster”

€99 per cluster per month — or $129. That’s it.

  • No per-node fees. Run as many worker nodes as fair-use allows; the price doesn’t change.
  • No user limits. Invite your whole team.
  • No hidden costs. No control-plane nodes, no load balancers for the control plane, no per-API charges.

The fee covers everything we operate: your cluster’s control plane on our seed, automatic provisioning and upgrades, lifecycle management, and the cost/savings reporting.

How billing works

Section titled “How billing works”
  • Card up front. A valid payment method must be on file before a cluster can be created — that’s what lets us run your control plane without it ever running unpaid. There’s no charge until you start a cluster, and no free trial.
  • Per cluster, prorated. Each running cluster is one line on your subscription. Start one mid-month and you pay for the days it ran; delete it and the charge stops, with a prorated credit.
  • Two currencies. Pick EUR or USD. EU VAT is handled correctly (B2B reverse-charge with VAT-ID validation); the €99 is exclusive of VAT.

What’s separate

Section titled “What’s separate”

Your Hetzner bill — the worker nodes, load balancers, and volumes in your own Hetzner project — is billed to you directly by Hetzner, at your own (ideally grandfathered) rate. paasbox never resells you compute. See grandfathered pricing for what that’s worth, and try the savings estimator there.

Fair-use

Section titled “Fair-use”

The flat price assumes a bounded control-plane footprint on our seed. Fair-use makes that explicit; exceeding a limit is a conversation, not an outage — we surface it when you configure a cluster and block only the specific over-limit action, never the running cluster. Indicative limits:

  • Worker nodes per cluster — a soft cap above which we review and, if needed, reprice.
  • Pooled servers — bounded by the size of the fleet you’ve enrolled.
  • Clusters per team — a soft cap before a quick manual review, to protect seed capacity.
  • Control-plane footprint — standard sizing; unusually large API/etcd footprints move to a paid tier.

Hibernated clusters keep billing while they’re parked, because the control plane still occupies the seed.