session 4c19 · 41 min · branch fix/checkout-tax
Give your coding agent somewhere permanent to work. Long refactors keep running after you disconnect, your API keys live on the server instead of six laptops, and every session leaves a record.
from £12.99/month · prices exclude vat. no setup fee, no minimum term.
What a hosted session actually gives you
Four practical differences from running the same CLI on the machine in front of you.
A large refactor can take an hour of tool calls. On a laptop that hour is hostage to sleep settings, VPN drops and battery. Here the session runs under a process supervisor on the server: you attach to watch, detach when you want, and the agent carries on. If your connection dies mid-run, nothing is lost and you reattach to the same session.
The usual pattern is an Anthropic key in a dotfile on every developer's laptop, plus a Git token beside it. That is several copies of a credential on several machines that leave the building. On a hosted machine the keys sit in a secret store, get injected into the session environment at run time, and are rotated centrally. Revoking someone's access is one change, not a request that they delete a file.
Agents write code. Sooner or later someone asks which commits came from an agent, what it was asked, and what it touched. We keep the prompt, the tool calls, the file diffs and the exit status for every session, so that question has an answer rather than an argument. On Scale the history is kept for a year.
Once the machine is always on, some jobs stop needing a human to start them. Run an agent at 2am to triage the overnight test failures and open a draft pull request. Trigger one from a webhook when a dependency alert lands. This is the part people do not anticipate when they first move off a laptop, and it is usually what they end up valuing.
the options
Claude Code runs anywhere there is a terminal. The question is what happens to a forty-minute job when you shut the laptop and get on a train.
Long-running jobs
On your laptop: Stop when the machine sleeps
A bare cloud VM: Keep running, if you set up tmux yourself
The Email Shop: Keep running — sessions are supervised and resumable
Where your API key lives
On your laptop: On every laptop that runs it
A bare cloud VM: In a file you put there
The Email Shop: In a managed secret store, injected at run time
Setup
On your laptop: Per developer, repeatedly
A bare cloud VM: You build the image and keep it current
The Email Shop: Node, Python, Go, Docker and the CLI, already there
Who else can pick it up
On your laptop: Nobody — it is your machine
A bare cloud VM: Anyone with the SSH key
The Email Shop: Named team members, each with their own login
Record of what changed
On your laptop: Your shell history, until it rotates
A bare cloud VM: None by default
The Email Shop: Every session logged with commands, diffs and timings
Cost of an idle machine
On your laptop: Nothing
A bare cloud VM: Full price, running or not
The Email Shop: From £12.99/month flat
If you only use Claude Code in short bursts while you are sat at your desk, your laptop is the right answer and you do not need this.
The difference between a general-purpose VPS and this is everything below, already configured.
Start a job, disconnect, come back tomorrow. Sessions run under a supervisor, so a dropped connection does not kill the work or lose the output.
Anthropic keys, Git tokens and deploy credentials live in a secret store and are injected into the session. Nothing is written into a dotfile on a laptop.
We set up deploy keys and clone the repositories your team works on, so a new session starts inside the project instead of starting with git config.
Prompts, tool calls, file diffs and exit codes, kept and searchable. Useful for review, and necessary the first time someone asks what the agent changed.
Node, Python, Go, Rust, Docker and the usual build tooling, kept current. The agent can install more, and we snapshot before it does.
Run an agent nightly against your test suite, or on a webhook when CI fails. The same machine, doing work while nobody is watching.
pricing
One developer, one persistent machine
2 vCPU · 4 GB RAM · 60 GB NVMe · 1 concurrent session
£12.99/mo
EnquireA small team sharing one environment
4 vCPU · 8 GB RAM · 120 GB NVMe · 3 concurrent sessions
£24.99/mo
EnquireContinuous agent work across projects
8 vCPU · 16 GB RAM · 250 GB NVMe · 10 concurrent sessions
£49.99/mo
EnquirePrices exclude VAT. No setup fee, no minimum term.
Set up takes about ten minutes, and we will help you move your keys and repositories across. Cancel any month.
