Costs and billing
What you pay for a PaaSbox Clusters cluster, to whom, and when. PaaSbox charges one price per cluster; Hetzner bills the server and the rest of your project to you directly.
PaaSbox ClustersIn progress
€29per cluster per month, incl. VAT
Outside the EU: $29 plus applicable sales tax
single node · planned price
Not bookable yet
Software as a service for one k3s cluster on one server in your own Hetzner project, kept current by the portal.
- Created in your project with your Hetzner token
- Upgrades in your maintenance window, after a snapshot
- Snapshots straight to your own S3 bucket
- Temporary kubeconfigs, readable only by you
- Curated add-ons: storage, ingress, certificates, DNS records
Paddle, the merchant of record, issues the invoice. Hetzner bills the server and the rest of your project to you directly.
What PaaSbox charges
Section titled “What PaaSbox charges”| What | Price |
|---|---|
| A cluster with one node, in the EU | €29 incl. VAT per cluster per month, VAT where it applies |
| A cluster with one node, outside the EU | $29 plus applicable sales tax per cluster per month |
| Add-ons, snapshots, kubeconfigs, upgrades, the API | nothing extra |
- Paddle is the merchant of record. You buy the subscription from Paddle, which takes the payment, issues the invoices, handles VAT and sales tax, and handles refunds. Paddle’s buyer terms apply to the purchase.
- One price per cluster. A cluster per stage and per app costs the price once for each; a throwaway cluster costs it only for the time it exists (below).
When a cluster is billed
Section titled “When a cluster is billed”| Event | What happens to the bill |
|---|---|
A cluster is first ready: pbx-agent reports a healthy Kubernetes API for the first time | It starts to count. A cluster that never becomes ready is never billed. |
| The team’s first cluster | A team admin starts the team’s one subscription in Paddle’s checkout, for one cluster. |
| Another cluster becomes ready | The subscription’s quantity goes up at once, and the rest of the current month is charged, prorated. |
| A cluster is deleted or detached, and others remain | The quantity goes down at once, and the rest of the month is credited to your next bill. |
| The team’s last cluster is deleted or detached | The subscription ends with the month already paid. A cluster created before that month ends continues the subscription without a new charge for that month. |
| A cluster after the subscription ended | Goes through Paddle’s checkout again. |
There is no separate cancel button: the bill follows your clusters. The portal’s count of clusters is what counts: it sets the subscription’s quantity on every change and compares it with Paddle every night.
Your team’s only cluster costs a full month, €29 incl. VAT or $29 plus applicable sales tax outside the EU, even if you delete it minutes after it became ready: deleting the team’s last cluster credits nothing. Create a team’s first cluster as one you may keep.
A throwaway cluster next to a cluster you keep costs the prorated part of a month for the time it existed: charged when it becomes ready, the rest credited when you delete it. As your only cluster, it costs the month you paid when you created it; another cluster created within that month uses the same month.
The team’s admins see the subscription, the next bill and the invoices on the team’s billing page, and open Paddle’s customer portal from there to change the payment method.
What Hetzner bills you
Section titled “What Hetzner bills you”Hetzner bills you directly, as for anything else in your project. For a cluster that is:
- the server, at Hetzner’s price for its type, which the create form shows next to each type; a server you already have keeps whatever Hetzner bills you for it,
- its IP addresses,
- the node image, which the portal stores once per project as a snapshot,
- traffic beyond what the server includes,
- Hetzner volumes, if you switch on the volume add-on and your apps use them,
- and your bucket for snapshots, if it is at Hetzner Object Storage.
Hetzner’s prices reach you unchanged: Hetzner bills you, not PaaSbox. Hetzner bills by the hour at its own prices; PaaSbox has no hourly price.
If an invoice stays unpaid
Section titled “If an invoice stays unpaid”| When | What happens |
|---|---|
| A charge fails, or the subscription ends while clusters are still billed | Nothing is deleted. The team cannot create a new cluster until the payment method is updated, or, for an ended subscription, a new one is started. |
| Day 1, 7 and 13 | A mail to the team’s admins. |
| Day 14 | The portal detaches the team’s clusters: they keep running in your project, the portal stops managing them, and billing stops. Their API names go 30 days later. |
| Paid before day 14 | The grace period ends; nothing changes. |
A failed charge for an added cluster does not undo the cluster: the change applies, the subscription is past due, and the steps above take over. See Detach or delete a cluster for what a detached cluster keeps.
What the price does not include
Section titled “What the price does not include”- There is no SLA. The cluster runs on one server in your project; if it fails, your apps are down until it is back, restored from a snapshot, or rebuilt.
- No monitoring of your workloads, and no deployment of your apps: you deploy them, yourself or through your agent.
- No backup of the data in your volumes: a snapshot holds the cluster’s state, not your volumes’ contents.
Planned Clusters with three servers come later, with their own price. There is no price for them yet.