Egg types

Everything you run on Ruust is an Egg. There are four kinds, and you pick one when you lay a new Egg. They share the same flat, per-Egg pricing, the same regions, and unmetered egress on every tier, so the difference is what runs inside, not how you are billed.

• Web app: a site or service built from a Git repo (or a demo), served over HTTPS.
• Database: a managed Postgres or Redis on a persistent volume, reachable privately.
• Vault: a storage-only Egg that keeps durable, off-host copies of a database Egg’s backups.
• Game backend: a managed realtime multiplayer backend (Nakama) with its own Postgres.

Web app Egg

Point Ruust at a repository and it builds, hatches and serves it over HTTPS at <name>.<region>.ruust.run. The buildpack is auto-detected (Nixpacks), or you bring your own Dockerfile. A demo template is one click if you just want to see it run. Web Eggs get automatic TLS, custom domains, horizontal scaling and private networking to the databases in their Coop.

Database Egg

A managed Postgres or Redis running the official engine image on a persistent volume you size yourself. A database Egg has no public URL: it is reached privately by the app Eggs in its Coop, by hostname, on the engine port (5432 for Postgres, 6379 for Redis). You size the disk yourself, and can grow it later; the size is hard-enforced as a per-volume quota on hosts whose filesystem supports it. A Postgres Egg can also import data from any reachable postgres:// source and turn on scheduled snapshots.

Vault Egg

A Vault is a storage-only Egg: it runs nothing of its own, it just holds durable, off-host copies of a database Egg’s snapshots. Attach one to a Postgres Egg and each completed snapshot is relayed onto the Vault, which is placed on a different host, so losing the database’s host cannot lose its backups. A Vault is billed per GB per month; you can restore from it even after the local copy has been pruned.

Game backend Egg

A managed realtime game backend (Nakama) deployed from our own image, the same way a database is: nothing to build. It gives you matchmaking, realtime rooms, presence, storage and server-side RPCs out of the box. Clients connect with a Nakama SDK over HTTPS and a WebSocket at wss://<name>.<region>.ruust.run. It is an API, not a page, so it has no "Open site" button.

Nakama keeps its state in a database, so a game backend is always laid together with a private Postgres Egg, peered and wired for you. The backend’s compute is the size you pick; the Postgres is its own Egg (its own line on the bill) that you can resize any time.

Pricing

Web and game Eggs are priced on compute (the sliding scale: £12 per vCPU plus £6 per GB per month). A database Egg adds a flat per-GB line for its volume. A Vault is pure per-GB storage. Egress is unmetered on all of them, in every region.