Move to Cloud

Partly in development

The cost preview and the Terraform export are built. The guided move of clusters and apps is in development, and its steps can change before launch.

Move to Cloud is the third step: the app you prepared on your Mac goes to your own cloud account. It always starts with the cost, so you know the monthly bill before anything is created.

Targets. Hetzner Cloud is the first and for now the only target. More clouds will follow. ownpaas reaches your cloud account with your own API token, which stays in your Keychain; the lab and your agents never see it.

1. Cost

The cost preview lists every resource of the project with the cloud resource it maps to and its monthly price, and adds them up, without and with VAT. Example:

Lab resource	In the cloud	Per month (net)
server cp-1	server type cax21, Nuremberg	6.49 €
server worker-1	server type cax21, Nuremberg	6.49 €
load balancer ingress	lb11	5.39 €
volume pg-data, 20 GB	volume, 20 GB	0.88 €
total		19.25 € (22.91 € with 19 % VAT)

The figures in this example are illustrative. The real preview uses the cloud’s current price list, which the app fetches with your token (Settings › Cloud Prices). Traffic and object storage are listed as not priced.

The same figure is on each project’s Overview, and your agent gets it with the MCP tool estimate_cost.

2. Move (in development)

For an app on Kubernetes, the guided move will:

1. creates the clusters in your cloud account from the same cluster template as in the lab, managed by an always-on management cluster (see Kubernetes clusters);
2. installs the same platform on them;
3. deploys your apps there;
4. switches the public address, if the app was pre-published through the gateway.

Each step is shown before it runs, with what it creates and what that costs.

Planned: moving clusters and their workloads with Cluster API itself, so a cluster moves with its state instead of being created anew.

Into PaaSbox Clusters (planned)

For a Kubernetes app, the planned destination is PaaSbox Clusters: a k3s cluster on one server in your own Hetzner project, created and kept current by the PaaSbox portal (upgrades after a snapshot, snapshots to your own S3 bucket). It is a separate service at a planned €29 per cluster per month, incl. VAT, sold on paasbox.com; Hetzner bills you for the server directly. PaaSbox Clusters is not bookable yet, and the move from ownpaas into it is not built.

The idea is the same on both sides: small, isolated environments, one per stage and per app, instead of one large cluster that everything shares.

Without Kubernetes

A lab project of plain servers, networks and load balancers can be exported as a Terraform configuration for the cloud: real server types, locations and images replace the lab’s, and the values ownpaas cannot know (such as certificate keys) become variables. Review it and run terraform apply with your own token. It works with the hcloud CLI and the Terraform hcloud provider.

Disk contents do not move with the export: cloud-init in the servers’ user data recreates most setups, and data moves with your own tools.