Features

Everything it does, and where it stops.

Kamal ships containers. This is the rest of the job: the machines underneath, the data on them, and the people and programs allowed to change either.

Connect your first server See how it works

Servers

Built in your own cloud account, or machines you already own.

Build a serverPick a type, a location and an image from the provider's own live catalogue, priced per location.
Bring a machine you ownAny Linux box reachable over SSH. No token, no API — the first session is the record.
Rename, resize, power, rebootReal provider actions, awaited rather than fired and forgotten. A resize warns that disk growth cannot be undone.
Take over what is already runningRead a machine's containers and make records from them. Nothing is booted, restarted or redeployed.

Hardening

Read back off the machine every time you open the page, never from a flag someone set once.

Deploying

Standard Kamal, run from a machine kept apart from the ones serving your app.

Data

Databases, the volumes under them, and getting both somewhere else.

Operating

The week after the deploy: what it is doing, what it costs, and who to tell.

Automation and people

The same actions, through whichever door suits — and a gate in front of them.

And where it stops.

No Docker Compose, no preview environments, and configuration history — who changed a secret or a role — is not recorded yet. Private networking between hosts, managed load balancers and accessories reachable from more than one machine are all still open.

See the comparison

Start with staging.

Connect a cloud account, build one server, and watch the hardening panel read it back to you.

Connect your first server Read the docs

Sign-ups are paused while the app is in maintenance.