Docker & container workloads
Run Docker and Compose inside a Cube that has its own kernel. Your containers get a full, isolated microVM to live in — not a slice of someone else's host.
Cubes from $2.92/moNo credit card to sign up
Why run this on a Cube
Every line here is enforced by the platform rather than left to you: its own kernel per Cube, RAM and disk reserved 1:1, and full outbound access while nothing reaches in until you open a port — each one IP-allowlistable.
Your own kernel for your containers
Install the Docker engine and run any image with full root. Because the Cube brings its own kernel, your container host is isolated by design rather than sharing a kernel with other tenants.
Compose whole stacks
Run multi-container apps with Docker Compose — web, worker, cache, and database side by side inside a single Cube you fully control.
Reachable on your own domain
Point a custom domain at your containerised app with one CNAME and get automatic HTTPS. Web traffic enters through managed ingress, so the Cube is never exposed directly.
Snapshot the whole host
Take a live snapshot of the entire Cube — engine, images, and volumes — and restore it instantly to roll back or clone your setup.
How it works on a Cube
Treat a Cube as your container host and deploy your stack onto it.
- 01
Create a Cube with the CPU, RAM, and disk your images need.
- 02
SSH in as root and install the Docker engine and Compose.
- 03
Bring up your stack with docker compose up, then map a custom domain for automatic HTTPS.
- 04
Snapshot the Cube once it's healthy so you can restore or clone it later.
Frequently asked questions
Do I get real Docker, or a limited runtime?
Real Docker. You have full root on the Cube, so you install and run the standard Docker engine and Compose exactly as you would on any Linux machine.
Why run Docker inside a Cube instead of on shared infrastructure?
Cube gives your container host its own kernel and a per-cube sandbox, so your workloads are isolated at the VM level — stronger than sharing a kernel across tenants.
Can I expose a container to the web?
Yes. Map a custom domain with a single CNAME and web traffic gets automatic HTTPS through managed ingress — the Cube itself is never exposed directly.
Launch your first Cube
Signing up is free — you'll be SSH'd into your own Cube in under a minute. Claim $5 in free credit — one-time, per account, and nothing is charged for it.