Run it
Containers without the platform tax.
Push an image and run it. Scheduling, health checks, rolling deploys and restarts are handled for you — and you do not inherit a Kubernetes control plane, its upgrades, or the engineer whose week it becomes.
Containers
- Any OCI image
- Rolling deploys with health gates
- Private networking
- Automatic restarts
How it helps
What you get with Containers
Rolling by default
New revisions roll out instance by instance with health gates, so a bad image stops partway instead of replacing everything at once.
Scale you set
Fix the instance count or let it track load. Either way the number is yours, not a heuristic you have to reverse-engineer during an incident.
On your own network
Containers join the same private networks as your VMs and databases, so a service mesh is not a prerequisite for two things talking.
Compute
The rest of Compute
Virtual machines and containers on dedicated capacity — sized by you, scheduled where you say.
Infrastructure you can point at.
Start in minutes on dedicated capacity, or talk to us about private capacity and named datacentres. Every tier is the whole platform.
Every service, every tier Predictable egress No charge to open a ticket