Overview
atominfra gives you a Lane: your own private share of the platform. In it you create virtual machines, and you manage all of them with one command-line tool, af. You can use af yourself, or hand it to your coding agent (Claude Code, Codex and others), which can then create and manage machines for you.
Your Lane is yours alone. Everything you create lives there. Nobody else on the platform can see or reach it, and its machines are reachable only from your own devices, over the private network you join during setup. Isolation between Lanes is audited.
Your Lane has its own CPU cores and caps on RAM, disk and the number of machines. Your admin sets them; af usage --json shows yours. See Usage and limits.
Machines
Section titled “Machines”Every machine in your Lane is one of two kinds:
| Kind | For | Lifetime | You reach it by |
|---|---|---|---|
| Box | Development, long jobs, coding agents | Persistent; snapshotted nightly, 7 days kept | SSH (Boxes) |
| Runner | GitHub Actions jobs for your repos | Until you delete it, or one job with --ephemeral |
GitHub, after you register it (Runners) |
| Size | vCPU | RAM | Disk |
|---|---|---|---|
| S | 4 | 8 GB | 50 GB |
| M | 8 | 16 GB | 100 GB |
| L | 12 | 32 GB | 200 GB |
| CI | shares your Lane’s CPUs | 16 GB | 50 GB |
CPU and RAM can grow and shrink. Disk only grows. CI is a size for Runners only.
The network
Section titled “The network”Your machines are reachable only over the platform’s private network, and only from your own devices. They can reach the internet. af never opens a public port.
What af will never do
Section titled “What af will never do”- Show you, or let you reach, another Lane.
- Hold your GitHub token or any other credential.
- Open a public port.
- Back your work up off the platform. Snapshots protect you from mistakes, not from losing the platform: keep your work in git and pushed.
Ready? Go to Getting started.