cps

cps gives you a hardware-isolated Linux microVM that boots instantly: root over SSH, a persistent disk, and a public HTTPS ingress — all driven from a single CLI. Machines are ephemeral by default, with automatic resource reclamation: spin one up, do your work, forget it — the TTL cleans up after you.

Under the hood it’s Firecracker + jailer: every machine is a real VM with its own kernel, isolated at the hardware level — not a container sharing a kernel with its neighbours.

Where to next

• Getting started — from install to a running machine in a couple of minutes.
• CLI reference — every command: new, ssh, expose, snapshot, backup, and more.
• API & authentication — tokens, org-scoping, and the REST API for automation beyond the CLI.

What a microVM gives you

• Instant start — boots in ~a second, not the tens of seconds of a full VM.
• Strong isolation — a dedicated kernel per machine (Firecracker + jailer); guest-to-guest networking is isolated. Not a “shared-kernel container”.
• Real Linux — root, arbitrary packages, syscalls, your own disk. Not a stripped-down sandbox.
• Persistent & portable — the disk survives restarts; snapshots/backups restore on another host.
• Ephemeral by default — a TTL reclaims resources automatically; persistent machines are opt-in (--ttl 0).

This is an invite-only alpha. Questions, bugs, ideas → the community chat @cps_run on Telegram.