FAQ
Is the portal live? Can I start today?
Section titled “Is the portal live? Can I start today?”Sign up at console.paasbox.com. We bring up regions as demand builds, so if we don’t yet run a seed where you want your cluster, you can register interest for that region and we’ll provision one and let you know — typically once a handful of customers want it.
Which regions can I use?
Section titled “Which regions can I use?”Any Hetzner Cloud location where we operate a seed. For locations we don’t serve yet, you register interest instead of hitting a dead end. (We stand up a new region when roughly 5–10 customers ask for it.)
Do I keep full cluster-admin?
Section titled “Do I keep full cluster-admin?”Yes. paasbox issues a genuine admin kubeconfig for your cluster. You deploy and manage your workloads
yourself with kubectl, Helm, or Flux — paasbox is a cluster-lifecycle, fleet, and billing console,
not an in-cluster UI, and it stays out of your way.
Do you resell Hetzner compute?
Section titled “Do you resell Hetzner compute?”No. Your worker nodes, load balancers, and volumes live in your own Hetzner Cloud project and Hetzner bills you for them directly. paasbox is software that provisions and operates your cluster on your own cloud — it never resells infrastructure or compute.
Is this multi-cloud?
Section titled “Is this multi-cloud?”No — Hetzner Cloud only. The entire value proposition (your servers, your grandfathered prices) is Hetzner-specific.
Why does the Hetzner token need read/write?
Section titled “Why does the Hetzner token need read/write?”On-demand (“managed”) node pools legitimately create and delete servers in your project, and Hetzner API tokens can’t exclude delete — so read/write is required for that path. The grandfathered (“pooled”) path never deletes: that guarantee is a code invariant plus Hetzner delete-protection, not a matter of token scope. We disclose this plainly when you connect your account.
What happens to a server when I “adopt” it?
Section titled “What happens to a server when I “adopt” it?”Adoption brings the server under Kubernetes by rebuilding it — an OS reinstall, which wipes the disk. Migrate your workloads off first; the portal makes you confirm this explicitly. After adoption, the server is rebuilt in place and never deleted, which is exactly how it keeps its grandfathered price.
Can I mix grandfathered and on-demand nodes?
Section titled “Can I mix grandfathered and on-demand nodes?”Yes. A cluster can have a pooled pool over your adopted servers (your cheap baseline) and a managed pool of on-demand nodes for burst that scales to zero. The autoscaler prefers your pooled nodes and only spills to on-demand when the pool is full.
What happens if I delete a cluster?
Section titled “What happens if I delete a cluster?”The cluster is torn down and the per-cluster charge stops, prorated. Your adopted servers are not deleted — they’re your property and keep their grandfathered rate, ready to use in another cluster.
Do you back up my data?
Section titled “Do you back up my data?”We operate and back up the control plane (including etcd). Your application data — databases, volumes, object storage — is yours to back up, the same as on any cluster where you hold admin.