Docs

What you need and in what order: sign up, subscribe, choose where sessions run, connect your Claude account, open the first session.

Register it in the console, run one command on it as root, and it connects itself. No ports to open, no certificates, no public IP.

Sessions run on your own Anthropic account. Authorize once from the console, or sign in on the machine yourself.

A session is one Claude Code running in one directory. It stays up when you leave, sends a notification when it needs you, and one switch stops all automatic replies.

Where your files, transcripts and Claude login are stored, on our machine or on yours, and who can reach them.

Billed by how many sessions run at once, not by token. Monthly in advance, non-refundable. Cancel anytime and keep the current period.

When a company needs it, what runs where afterwards, what still leaves the network, and how it is delivered.

Run one program once to stop the usage analytics and crash reports that Claude Desktop and Claude Code send to Anthropic by default. For macOS, Windows and Linux.

The few things that go wrong in practice: a machine that will not connect, sessions that will not start, the concurrency limit, and a subscription that has not shown up yet.