Overview
Ruust is flat-priced container hosting for always-on apps. Connect a repo, and we build it, run it on HTTPS and keep it alive.
Ruust runs your app as a container we call an Egg. You point us at a Git repo, we detect the stack, build it, and run it on HTTPS in the region you choose. There are no cold starts and no per-request billing: an Egg is always on, at one flat price per month.
Almost anything that builds into a container runs here: Node, Next.js, Nuxt, Rails, Django, Go, Rust, PHP and more. If your app listens on a port, it runs on Ruust.
The words we use
- An
Eggis one deployed app: a container with a size, a URL and a flat monthly price. - A
Coopis a project: a group of Eggs that can reach each other privately and be shared with a team. - A
regionis where an Egg runs. London and Virginia are live. Your own hardware is a region too (see bring your own host). - Egress is
unmeteredon every size. We never bill for bandwidth or show a cap.
How a deploy works
- You connect a Git repo, or pick a ready-made demo.
- Ruust detects the stack and builds it to a container image (Nixpacks, or your own Dockerfile).
- The image is placed on a host and started. The Egg incubates, then hatches.
- We issue TLS and route traffic to it. Your app is live on HTTPS: demos and cached rebuilds are ready in seconds, whilst a first-time repo build is often around 90 seconds. There is no enforced SLA.
What it costs
Pricing is a flat sliding scale: £12 per vCPU plus £6 per GB of memory, per month, sized however you like. A database Egg adds its disk at £0.50 per GB per month, and a Vault is pure per-GB storage. Bursting above your guaranteed CPU is free, egress is unmetered, and there is no plan fee. Bring your own host and you pay a small flat fee per Egg instead, because the compute is yours.
Where to next
- New here? Start with the
Quickstart. - Want to know how the build works? Read
How builds work. - Deploying a specific stack? Jump to its guide in the sidebar.
- Running on your own metal? See
Bring your own host.