Best VPS for Claude Code? When a VM per project fits better

Best VPS for Claude Code? When a VM per project fits better

What Claude Code needs from a server, what running it on a VPS involves, and when a cloud VM per project with the agent signed in fits better.

20 Nov 20264 min readhomemade team

If you search for a VPS to run Claude Code on, you get hosting companies selling you their smallest plan with a Claude Code logo on it. That can work. It can also leave you with a server you now have to look after, running one agent, on one branch, all month.

This post is about what Claude Code actually needs from a machine, what a VPS gives you, and when a VM per project (what we build at homemade) fits better. We make one of the options, so read it with that in mind. Every fact about Claude Code below is from Anthropic's own docs.

What Claude Code needs

From Anthropic's setup page:

  • Linux is fine. Ubuntu 20.04+, Debian 10+ or Alpine 3.19+, x64 or ARM64.
  • 4 GB of RAM or more. That's the stated minimum for Claude Code itself, before your app, your database and your test runner.
  • An internet connection and a supported country.
  • A plan. Pro, Max, Ultra, Team, Enterprise or a Console account. The free claude.ai plan doesn't include Claude Code.

The 4 GB line matters: Anthropic lists it as the minimum for Claude Code alone, so a 1 GB or 2 GB VPS is below it before your dev server and tests are running.

Why people want it off their laptop

Three reasons come up again and again:

  • It keeps working when the lid is closed. A long run doesn't stop because you went home.
  • You can check on it from your phone. Anthropic's mobile docs say Remote Control drives your own machine, "so it needs to stay on with Claude Code or the Desktop app running".
  • It can't touch your laptop. An agent allowed to run any command is easier to trust on a machine you can throw away.

The VPS route

A VPS gives you a Linux box with a public IP for a fixed monthly price. To make it a good home for Claude Code you then:

  1. Pick a size with at least 4 GB of RAM, more if your app needs a database.
  2. Lock down SSH (keys only), set up a firewall, and keep the OS patched.
  3. Install Claude Code, git, your language runtimes and your project's dependencies.
  4. Clone the repo and sign Claude Code in.
  5. Run the agent inside tmux or screen so it survives a dropped connection.
  6. Expose your dev server somehow: an SSH tunnel, a reverse proxy with a certificate, or a private network like Tailscale.
  7. Pay for it every hour of the month, whether the agent is working or not.

None of that is hard, and if you like running servers it's a fine setup. If the machine is busy around the clock, a fixed monthly price suits it.

Where it gets awkward is the second agent. Two agents on one VPS share ports, node_modules, the git working tree and the RAM. So you either buy a second VPS and set it up again, or juggle git worktrees and port numbers by hand.

A VM per project instead

This is the part we built homemade for. Each project, or each task, gets its own Linux VM:

  • Claude Code is already there and signed in. You sign in once with your Claude plan or an Anthropic API key, and every new VM starts signed in. Codex, OpenCode, pi, Kimi and Grok are installed too.
  • Your repo is cloned and running. The VM starts from your repo at the branch you pick, with your install commands run and your services started in their own terminals.
  • Every port gets a link. Your dev server is on an HTTPS URL you can open on your phone or send to someone, public, organization only or owner only.
  • It sleeps when idle. You pay for hours a VM runs, not hours it sleeps, and it wakes up where you left it.
  • A second agent is a second VM. homemade vm create --branch other-task and the two never collide.

The price, from our pricing page: Hobby is free with 25 VM-hours a month. Pro is $20 a month with $20 of usage included, then from $0.012 an hour (nano) to $0.18 (large) by size. For Claude Code, pick tiny (2 vCPU / 4 GB) or bigger so you clear the 4 GB line.

So which one?

Pick a VPS if you want one long-lived server, you're happy to look after it, and it'll be busy most of the month.

Pick a VM per project if you run more than one agent at a time, you want the app running on a link without setting up a proxy, you want to check in from your phone, or the machine would sit idle most of the day.

And if you only hand off small tasks from the Claude app and don't need to see the app running, Anthropic's own cloud sessions may be all you need.

More detail: Claude Code in the cloud, and our step-by-step guide to running Claude Code and Codex in a cloud computer.

Try homemade

Every project gets its own cloud computers, with Claude Code and Codex signed in. The Hobby plan is free.

Related posts