Every container runs its own VM kernel.

Push your docker-compose.yml. CargoForge runs it exactly as-is. Each container runs under its own kernel inside a Hardware-assisted VM instead of a plain container susceptible to every lousy neighbor on the box.

$ git push origin main Sealing container ds-7f2e1a-web... ✓ ds-7f2e1a-web healthy

Deployment

  • Build
  • Push
  • Sealing container…

ds-7f2e1a-web

Healthy · 3 services

This container's kernel Kata Containers
Shared with
nobody
ISOLATED ✓

Pay for what you need only

Run a 64MB RAM container. Get billed for a 64MB RAM container.

Every cpu, memory, and storage limit in your compose file is the actual enforced ceiling on the container and is billed accordingly per 0.%vCPU, MiB RAM, and GiB storage respectively. Declare 111MiB RAM, pay for 111MiB RAM; zero suprises!

# docker-compose.yml services: web: image: nginx:alpine ports: - "80:80" deploy: resources: limits: cpus: "0.1" memory: 128M x-cargoforge: storage_limit_gb: 3

0.1 vCPU$0.20/mo

128MB RAM$0.37/mo

3GB storage$0.18/mo

Total$0.75/mo

No imposed min or max resource limits. Resources and pricing are geared towards leanness. So set resources for each and every service in your docker-compose.yml freely.

Push it like you mean it ↓

The Math

vCPU$0.0000000761/0.1 vCPU‑sec

Memory$0.00408/GB‑hr

Storage$0.0000822/GB‑hr

Bandwidth$0.01/GB

The rate used to compute billing.

See it in action

Dashboard quick peek.

A dashboard that gets out of your way.

A simple projects dashboard with a solid backdrop of a self-healing and seamless failover architecture across baremetal nodes. All of it baked-in. Simplicity wins always.

The manifest

From dock to Docker.

A fleet of baremetal nodes host individual, secure containers; each container running inside its own hardware-assisted virtual machine. Services runs exactly as defined in your docker-compose.yml.

The fleet

Baremetal with solid orchestration and resilience. No nested virtualization or noisy neighbors to worry about. Hardware virtualization as first-class citizen.

Sealed containers

Every container gets its own real guest kernel in a lightweight VM. Not a namespace. Not a chroot. A hard isolation boundary, not a best-effort one.

Your compose file

The exact docker-compose.yml already in your repo including all services. We don't invent a format. Bring over your own YAML and break a leg!

What's so different

The short and sweet list of reasons.

Your pristine compose file

No proprietary schema, no translation step, no migration runbook. The file already in your repo is the deploy.

One container per kernel

Kata Containers define the hard boundaries. Zero shortcuts taken with concrete VM sandboxing. A docker-compose.yml with two services runs on two hardware-assisted containers.

No compose file yet? Pick one.

WordPress, Gitea, a self-hosted LLM chat, FreshRSS, Uptime monitor, IT Tools, a few dozen more working docker-compose.yml templates. one click away and fully editable before you deploy it.

Auto-scaling at the push of a button

Per-container auto-scale to ramp things up and down as needed. You only get billed for what you're using.

Nothing to SSH into, nothing to leak

No standing SSH key onto any host, from us or anyone else. The fleet never accepts an inbound connection in the first place.

Pay for what you use only

Auto-pause your dev projects when traffic slows down and save! The free plan has ample room for development too (300h/month). Or always-on for mission-important projects.

Failover, self-healing, and SSL

Because we can and wouldn't have it any other way. Worry less, do more!

The tariff

The flexibility of a container priced like one.

The dependability and security of a hardware-assisted VM combined with the flexibility of a Docker Compose project. Every plan pauses a project the moment it goes quiet and wakes it the instant a request comes in. So you're never billed for compute nobody's using; unless you'd rather it never paused at all.

Freight $0/mo

An option for finding out if this is for you or for the side project you don't need to run at 3am.

  • 15 containers
  • 3 projects
  • Every endpoint is HTTPS
  • 300 hrs/mo awake (tracked to the second) and resets monthly; a project stays paused till reset
  • 100 GB/mo data transfer included
  • No custom domain
  • No credit card required
Start for free ↗
Fleet Custom

Docker Compose on-a-stick of Baremetal servers, fully dedicated to your team.

  • One or more dedicated hosts, exclusive to your team
  • Unlimited projects and containers
  • Dedicated ingress + support
  • Custom account quotas
  • High availability within-region
Talk to us ↗

Cast off in one push

The whole deploy, in one session.

Automaticity at its core. Connect your repo and with every push rebuild and redeploy it with continuous integration. no push required.

$ git push origin main Parsing docker-compose.yml... Resolving host dock-host-04... Building web, api, worker (3/3)... Sealing each container with its own guest kernel... ✓ web running :3000 ✓ api running :8000 ✓ worker running ✓ project ds-7f2e1a healthy

Every container within a project gets its own hardware-base VM kernel with plenty of features to cover your dev needs.

For the CLI crowd

Never open the dashboard, if you're allergic...

No bespoke CLI binary to install. Every customer-facing endpoint is a documented REST API, authenticated with a long-lived key instead of a login session. Script it from a shell or a CI pipeline.

An API key is all you need to create a project, push a compose file, deploy, and check it went live. No browser needed.

Full reference at docs.cargoforge.dev.

Ship the preview, not just the diff

Every pull request gets its own live deployment.

Open a PR against a connected repo and Cargo builds and deploys it the exact same way your main branch already does. Then posts the live URL straight back as a PR comment. Close the PR, and it tears itself down. Nothing to spin up or clean up by hand.

A preview is a fully separate deployment on its own sealed container(s), its own hostname, its own volumes. Each PR gets its own resources.

Reviewers click the link in the PR; not a screenshot in a Slack thread. The actual branch running and torn down the moment the PR closes.

Questions

Docker Compose hosting FAQ

What is Docker Compose hosting?

Pushing the docker-compose.yml you already run locally to a managed control plane that deploys it as-is, instead of rewriting it into another declarative format like a Kubernetes manifest.

Can I deploy my existing docker-compose.yml without changes?

Yes. CargoForge runs the exact docker-compose.yml already in your repository or that you copy/paste in the dashboard. We don't invent our own format or require rewriting services, volumes, or networks to fit a different schema.

How is CargoForge different from a shared container host?

Every container CargoForge starts gets its own real guest kernel in a lightweight hardware-based virtual machine rather than a namespace inside a kernel competing with other customers' containers.

Does CargoForge support a docker-compose.yml with multiple services?

Yes. A docker-compose.yml with several services, a web app, a database, a cache, a worker, etc. It deploys as written, each service sealed in its own container.

Forge Away!

Push your docker-compose.yml file. No rewrite, no migration runbook; we'll take it from there.