Pricing & billing
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
PaaSbox charges per cluster, in two tiers. The marketing view with the savings math lives at /pricing/; this page is the ladder in table form plus the billing mechanics.
The ladder
Section titled “The ladder”All prices exclude VAT (as of 2026-07-09):
| Tier | Control plane | Monthly | Annual (pay 10, get 12) | Hourly (PAYG) |
|---|---|---|---|---|
| Basic | single replica | €49 / $65 | €490 / $650 | €0.09 / $0.12 |
| HA | 3× etcd & API server, survives node failure | €99 / $129 | €990 / $1,290 | €0.19 / $0.24 |
- No per-node fees, no user limits, no hidden costs. The fee covers everything we operate: the control plane, provisioning and upgrades, lifecycle management, hibernation, and the portal.
- Basic vs HA changes only the control plane’s failure tolerance. Your workloads run on your worker nodes either way — a control-plane restart pauses management (deploys, scaling), not the apps already running.
- Annual is pay 10, get 12 — two months free against the monthly rate, for one-year terms.
- Hourly pay-as-you-go meters awake hours only: partial hours round up, each active period bills a minimum of 4 hours, and a hibernated cluster meters €0. It’s the right plan for spiky or intermittent use; steady clusters are cheaper on monthly or annual.
What’s separate: your Hetzner bill
Section titled “What’s separate: your Hetzner bill”Your worker nodes, load balancers, and volumes live in your own Hetzner project, and Hetzner bills you for them directly — at your own rate. PaaSbox never resells you compute. See grandfathered pricing for what keeping your pre-increase rate is worth.
How billing works
Section titled “How billing works”- Card up front, €5 signup credit. 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. A one-time €5 credit per team covers your first experiments; 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.
- Currency is fixed at first checkout. Pick EUR or USD the first time you pay; the account stays in that currency.
- Mid-period charges on PAYG. When accrued pay-as-you-go usage reaches €25 above what’s already been charged, we invoice immediately instead of letting a surprise build up until month-end.
- Tier changes. Upgrading a monthly cluster to HA mid-period is prorated — you pay the difference for the remaining period.
- VAT. Prices exclude VAT; it’s added automatically based on your country. EU businesses with a valid VAT ID are reverse-charged. Outside the EU, PaaSbox is offered to businesses only.
Hibernation and the meter
Section titled “Hibernation and the meter”- On hourly PAYG, a hibernated cluster costs €0 — the meter only counts awake hours. Waking it starts a new active period (4-hour minimum).
- On monthly and annual, the flat fee keeps running while a cluster is hibernated — the plan reserves your control plane’s slot. If a cluster spends most of its life asleep, PAYG is the cheaper plan.
- Either way, hibernating drops the Hetzner side of the bill: on-demand worker nodes are deleted and your pooled servers are released back to your fleet — never deleted.
Spend caps
Section titled “Spend caps”Every account has a monthly spend cap from day one, so a script gone wrong can’t produce a runaway bill. Caps rise with billing history:
| Cap | When |
|---|---|
| €200 / month | every new account |
| €1,000 / month | after 2 cleanly paid months |
| €5,000 / month | after 6 cleanly paid months and €500 total paid |
| Custom | by arrangement — contact us |
Approaching the cap warns you; at the cap, awake clusters are hibernated — never deleted. Raise the cap or wait for the month to roll over, then wake them.
If a payment fails
Section titled “If a payment fails”- New cluster starts are blocked immediately, and Stripe retries the charge over the next days.
- After roughly 3 days unpaid, running clusters are hibernated (your data and configuration stay intact).
- After roughly 14 days unpaid, managed (on-demand) resources are deleted. Pooled servers are never deleted — even in dunning. They return to your fleet, keeping their grandfathered price.
Cancellation & refunds
Section titled “Cancellation & refunds”- Monthly plans cancel anytime and run to the end of the paid period — no partial refunds; the discount versus hourly PAYG is the trade for the period commitment. If you want hour-precision exit, use PAYG.
- Annual plans cancel to the end of the term. On request, we refund the unused remainder minus the months used at the monthly rate (annual = 10× monthly, so the refund reaches €0 at month ten).
- Deleting a cluster mid-period ends its subscription immediately and forfeits the remainder of that period.
- EU consumers have a 14-day right of withdrawal; by starting cluster provisioning you consent to immediate performance and waive it once the service has begun. Outside the EU, PaaSbox is offered to businesses only.
The standalone refund & cancellation policy and the terms of service are the authoritative versions of these rules.
Fair use
Section titled “Fair use”The flat price assumes a bounded control-plane footprint on our platform. 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 platform capacity.
- Control-plane footprint — standard sizing; unusually large API/etcd footprints move to a paid tier.