Holio Cloud
Your containers, run by Holio, in the EU.
Push an image, name a port, and Holio Cloud keeps it running — next to your orders, stock and customers on the Holio platform, not in another vendor's console.
- Where it runs
- Our own servers in Germany
- Isolation
- A gVisor sandbox per tenant
- Every deploy
- An immutable, numbered revision
A deploy should not be a new vendor, a new bill and a new login. On Holio it is a revision of a service your platform already knows.
What you get
Cloud Run's shape, on infrastructure we run
Revisions pinned to a digest
Every deploy is a numbered revision tied to an exact image digest. Nothing moves under you, and the last healthy revision keeps serving until the new one is ready.
A sandbox per tenant
Each customer's services run in their own namespace under gVisor, with restricted pod security, non-root containers and a quota from their plan.
Servers in the EU
The platform runs on dedicated Holio servers at Hetzner in Germany. Your workload and its data stay in the EU.
Rollback is one step
Traffic points at a revision, so going back means pointing at the previous one. No rebuild, no guesswork.
A CLI, an API and a screen
Deploy, inspect, suspend and resume from the Cloud tab in Holio, from the holio CLI, or from your own CI — the same routes, the same rights.
Your Holio identity
No separate cloud account. Who may deploy is decided by the roles your company already has in Holio.
How it works
Three steps from an image to a running service.
Build and push your image
Any OCI image that listens on a port and runs as non-root. Push it to the registry and pin the digest.
Deploy a revision
One command or one click. The revision is queued, the reconciler starts it in your sandbox, and it turns healthy when it answers.
Watch it, or roll it back
Status, logs and revisions in the Cloud tab. A bad deploy never replaces a healthy one.
Plans
Sized in CPU, memory and instances, and enforced by the platform — not by an invoice after the fact. Prices are set with each early-access customer.
Starter
Early access
What you get
- 0.25 vCPU, 512 MiB per instance
- 1 instance
- 5 million requests a month
- 25 GiB egress a month
- 20 secrets
Standard
Early access
What you get
- 1 vCPU, 1 GiB per instance
- Up to 2 instances
- 25 million requests a month
- 100 GiB egress a month
- 50 secrets
Scale
Early access
What you get
- 1 vCPU, 1 GiB per instance
- Up to 8 instances
- 50 million requests a month
- 200 GiB egress a month
- 100 secrets
Questions
Is Holio Cloud available today?
Holio Cloud is in early access. We are onboarding a small number of Holio customers and building out public endpoints, autoscaling and usage billing with them. Ask for access and we will tell you honestly what fits today.
Do we need to be on Holio?
Yes. Holio Cloud is part of the Holio platform: your company, users and roles come from there, and the service runs next to the rest of your data.
Where is my data?
On Holio's own servers at Hetzner in Germany. Nothing is placed outside the EU.
Can we build from source?
Not yet. Today you deploy a container image you have built. Building from a repository is on the roadmap.
What does it cost?
During early access the price is agreed with each customer, from the plan the service needs. Every plan has a fixed ceiling on CPU, memory and traffic, so a bill cannot run away from you.
Run your next service on Holio
Tell us what you want to run. We answer within one working day.