session 4c19 · 41 min · branch fix/checkout-tax
Claude Code reads files, rewrites code, runs shell commands and loops until the job is done. That needs a real environment — not a laptop that sleeps, or a cloud function that times out.
from £12.99/month, no minimum term · prices exclude vat. no setup fee.
Why a container rather than a laptop
Claude Code is not a chat window. It reads files, rewrites code, runs shell commands and loops until the job is done — which takes time, and takes a machine that is still there when it finishes.
A large refactor can take an hour of tool calls. On a laptop that hour is hostage to sleep settings, VPN drops and battery. On a container it simply keeps going, because the machine is not the one in your bag. Start something, disconnect, and come back to it.
Serverless is the other obvious place to put an agent, and it is the wrong shape for this. Functions have execution limits and a filesystem that vanishes between invocations. An agent that works for forty minutes and needs its checkout still there does not fit that model.
Claude Code runs shell commands. Sooner or later that means adding a runtime, a package manager or a build tool. This is a normal Linux container with root, so it can — and so can you, alongside it.
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.
| compared on | alternativeOn your laptop | alternativeA cloud function | recommendedThe Email Shop |
|---|---|---|---|
| Long-running jobs | Stop when the machine sleeps | Cut off at the timeout | Keep running — the container stays on |
| Shell access | Yes | Limited or none | Root access — install whatever the job needs |
| Persistent filesystem | Yes, until you close the lid | Wiped between invocations | Yes — your checkout stays where you left it |
| Your Anthropic account | Yours | Yours | Yours — you connect it, we do not resell model access |
| Where it sits | Wherever you are | Vendor's regions | UK data centres |
| Backups | Whatever you set up | Not applicable | Included |
Long-running jobs
Shell access
Persistent filesystem
Your Anthropic account
Where it sits
Backups
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.
A container of your own that stays on, with root access. You install the CLI and connect your own Anthropic account.
Start a long job, close your laptop, get on a train. The container keeps running, because it is a server rather than the machine in front of you.
A normal Linux container. Install the Claude Code CLI, whichever runtimes your project needs, and anything else you want alongside it.
Your checkout, your branches and your build cache stay where you left them between sessions. Nothing is wiped between runs.
You connect your own account and your model usage is billed to you by Anthropic. We do not resell model access or add a margin to your token spend.
Your container is backed up. If a run goes badly wrong, ask us and we will restore it.
The container sits on infrastructure in the United Kingdom, with a UK team on ticket, email and live chat at any hour.
pricing
Move up or down a tier whenever you like, and cancel any month.
Prices are per month, billed monthly. No minimum term — cancel any month.
One project at a time
2 vCPU · 4 GB RAM · 60 GB storage · root access
Bigger repositories, heavier builds
4 vCPU · 8 GB RAM · 120 GB storage · root access
Several projects, or work running around the clock
8 vCPU · 16 GB RAM · 250 GB storage · root access
Prices exclude VAT. No setup fee.
A container in a UK data centre that stays on, with root access and backups included. Connect your own Anthropic account and get on with it.
