Run Claude Code on a VPS—or use a managed workspace?

A VPS gives you control of a server. A managed agent workspace reduces infrastructure setup. Both move execution off your laptop; the better choice depends on how much server work you want to own.

No card required. Credit covers hosting. Provider usage limits apply.

What you manage with a VPS

With a self-managed VPS, you choose the operating system, install the provider’s CLI from its official source, configure access, and maintain the server. You also own updates, firewall configuration, credentials, disk capacity and backups.

That can be a good choice if you already run servers, need custom system packages or want complete control over the environment. A low VPS invoice does not include your administration time. A server also does not remove Claude’s account eligibility or usage limits.

What A32 manages instead

A32 provisions the environment with Claude Code and Codex available, provides the browser terminal, and exposes managed jobs through the dashboard and API. You choose a plan and persistent disk, connect your own agent account and run a task.

You still own your project, provider account, task instructions and backups. A32’s instance is a separate container and volume; it should not be described as a dedicated physical server or an arbitrary full-system VPS.

Compare the complete workflow

DecisionSelf-managed VPSA32 workspace
Server setupYou install and maintain the environmentProvision through the dashboard or API
AccessYou configure SSH and any web terminalBrowser terminal and authenticated machine APIs
Long tasksYou configure process/session managementManaged running jobs keep the instance awake
PersistenceDepends on your disk, lifecycle and backup setupHome volume survives sleep/restart; deletion removes it
Model costsYour eligible subscription or API keyYour eligible subscription or API key

A low-risk first test

Use a throwaway project and ask the agent to create and read a small file. Disconnect your browser during a managed job, reconnect, and inspect the final status. Then check the file after the instance’s documented sleep and wake cycle.

On your VPS, install the CLI and sign in through the provider’s own flow. For A32’s managed setup, follow the hosting walkthrough. Before adding automation for other people, review the provider’s current authentication and commercial terms.

Published by agent-32 · Reviewed 18 November 2026.

Run your first task on A32.

No card required.

Start free — €5 credit