How to migrate an AI agent from Hetzner to Orgo

If an AI agent lives on a Hetzner Cloud server today, you can move just that agent to an Orgo computer and leave everything else where it is. This post covers how the two platforms map, what size to pick, how to carry the agent's state across, and what changes after the move. It follows the Migrate from Hetzner guide in the Orgo docs.

TL;DR

Move a workload to Orgo when the job is an AI agent operating a durable computer or browser. Keep general server workloads and public-facing services on Hetzner.

• A Hetzner server maps to an Orgo computer, created with POST /computers.
• ssh root@<server-ip> maps to POST /computers/{id}/bash, or orgo ssh <name> for an interactive shell. A Linux computer can also take direct SSH with your own key.
• The server disk maps to the computer's disk, which is persistent by default.
• A Hetzner Snapshot maps most closely to POST /computers/{id}/clone, or to a template when you want the same starting point for many computers.
• Move state by archiving it on the Hetzner server and pulling it into the Orgo computer from a private Git repo or any URL. Files up to 2 GB can also go up through the API.
• If you rebuild the same agent box often, put the setup in an Orgo template (your own templates need a Scale plan or higher), so each new computer starts from a prebuilt snapshot instead of re-running installs.

What does it mean to migrate from Hetzner to Orgo?

On Hetzner Cloud you run workloads as Servers: Linux VMs you provision, SSH into, and administer yourself. Orgo gives an AI agent a persistent computer with a desktop, browser, shell, and files, which the agent drives over the HTTP API, the orgo CLI, or MCP. Screenshot, click, and type are built in.

So migrating does not mean moving every Hetzner server to Orgo. Orgo is not a general cloud platform; it runs computers for AI agents. The migration covers the agent part of your stack: the server where an agent logs into web apps, drives a desktop browser, or runs around the clock as a CLI agent such as Hermes Agent, OpenClaw, or Claude Code.

What is an Orgo computer, compared with a Hetzner server?

An Orgo computer is a cloud machine with a full desktop environment, a browser, and the standard userland, reachable over HTTP and VNC. It comes online in seconds and runs until you stop it. Linux and Windows computers are self-serve: Windows is included on Scale and costs $15 a month per Windows computer on other paid plans. Mac and iPhone are available by request. Orgo provides the computer, and you choose the agent that drives it: Claude, OpenAI, or Gemini models, Hermes Agent, OpenClaw, or your own agent loop.

A Hetzner server is a general-purpose Linux VM you fully own, with arbitrary services and ports, managed networking (Primary and Floating IPs, firewalls, private networks), daily backups you enable per server with seven kept, and snapshots that stay until you delete them.

How do Hetzner and Orgo compare for AI agents?

The rule of thumb from the docs: keep general server workloads and public-facing services on Hetzner, and move to Orgo when the job is an agent operating a durable computer or browser.

When should you move to Orgo, and when should you stay on Hetzner?

Move the workload to Orgo when:

• Your agent needs a real desktop and browser, not just a process on a headless server.
• You are building your own screenshot, click, and type harness on a VPS. Orgo has one built in.
• You want a persistent home for Hermes Agent, OpenClaw, or Claude Code without running the OS, firewall, or TLS yourself.

Stay on Hetzner, or run both, when:

• You need a general Linux server you fully own, with arbitrary services and ports.
• The machine serves traffic from the internet. An Orgo computer has no public IP of its own, and apart from direct SSH on Linux, customers cannot publish a port from it to the internet today.
• You rely on Hetzner networking: Primary and Floating IPs, firewalls, private networks.
• The workload is a backend with no need for a desktop.

The two are not mutually exclusive. You can keep backend services on a VPS and use Orgo for the work where an agent drives a computer.

How do you size an Orgo computer for a workload that ran on Hetzner?

POST /computers takes no size name. You send cpu, ram, and disk_size_gb along with the required workspace_id and name (Create computer). The sizes are:

The dashboard offers Medium and up. If you send only ram, you get that size's vCPU: 2 for 8 GB, 4 for 16 GB, 6 for 32 GB.

Three things to check before you copy your Hetzner server spec across:

• You can create up to XL (6 vCPU, 32 GB RAM) on your own, on every plan. More vCPU or RAM than that returns 403 with code CONTACT_US_FOR_SIZE, and Orgo sets it up on request. No computer goes above 8 vCPU, 64 GB RAM, or 300 GB of disk, so if a Hetzner server is bigger than that, split the agent work across several computers.
• Your plan limits each computer. A plan's computers share its RAM total and its vCPU, and disk goes up to 40 GB per computer on Starter, 80 GB on Growth, and 150 GB on Scale. On Starter, the one computer goes up to 8 GB of RAM. Adding memory, vCPU, or storage to your account raises those limits.
• The pricing models differ. As of October 2026, Hetzner bills each server by the hour up to a monthly cap, and keeps billing a powered-off server until you delete it (Hetzner billing FAQ). Orgo bills per plan, which sets how many computers you can run and the RAM they share, and you can add capacity on top. Plans start at $29 a month for one computer, and a free account's $5 signup credit runs one Medium Linux computer by the hour. Compare total cost for the workload, not RAM alone, since a raw VM leaves you to install and run the desktop, browser, and automation yourself. Current prices are on the pricing page.

How do you move state from a Hetzner server to Orgo?

The Orgo docs recommend pulling data in from inside the Orgo computer. POST /computers/{id}/bash runs any shell command there, so the transfer goes straight from your repo or file host to the computer, with no laptop round-trip. A command runs for 200 seconds unless you send timeout, which goes up to 300. For a pull that takes longer, start it in a detached tmux session and check on it with a second call.

Recommended: a private Git repo

1. On the Hetzner server, archive what you want to keep and copy it down. Hetzner's own Migrate data guide also uses scp.

ssh root@<server-ip> "tar czf /tmp/state.tgz -C /root ."
scp root@<server-ip>:/tmp/state.tgz ./state.tgz
# Commit state.tgz (or the raw directory) to a private repo.

GitHub blocks files larger than 100 MiB, so split a bigger archive or use one of the other options below.

2. Inside the Orgo computer, clone and extract:

curl -X POST https://www.orgo.ai/api/computers/$COMPUTER_ID/bash \
  -H "Authorization: Bearer $ORGO_API_KEY" -H "Content-Type: application/json" \
  -d '{"command":"git clone https://TOKEN@github.com/you/your-state.git ~/state && tar xzf ~/state/state.tgz -C ~","timeout":300}'

Use a token that can only read that one repository, since Git keeps the clone URL, token included, in ~/state/.git/config.

Other options

• Any URL. Host the archive anywhere the computer can reach, and curl or wget it from inside the computer the same way.
• Files up to 2 GB. Start large upload (POST /files/uploads) returns a signed URL. PUT the file to it, then call Complete large upload (POST /files/uploads/complete), and the computer pulls the file into place. The computer must be running for that last step.
• Files up to 10 MB. Upload file (POST /files/upload) stores a file in the workspace and pushes it to the computers that are running.

Moving Hermes Agent or OpenClaw specifically? The Migrate to Orgo playbook moves either one with its memory, skills, sessions, and configuration intact.

How do you set up the Orgo computer?

One create call, then run your installer through /bash:

curl -X POST https://www.orgo.ai/api/computers \
  -H "Authorization: Bearer $ORGO_API_KEY" -H "Content-Type: application/json" \
  -d "{\"workspace_id\":\"$WORKSPACE_ID\",\"name\":\"prod\",\"ram\":8}"
# Save the returned id as $COMPUTER_ID, then run your installer via /bash.

Sending only "ram": 8 gives you a Medium: 2 vCPU, 8 GB RAM, and your plan's default disk. The computer draws on your plan. A free account can instead run one Medium Linux computer by the hour on its signup credit by adding "billing_mode": "hourly" to the request.

One difference from your Hetzner server to plan for: an Orgo computer does not run systemd, so a unit file you used there will not start. Run a long-lived process in a detached tmux session, which does not come back on its own after a restart, or, on a Scale plan or higher, declare it as an app in your own template, which keeps it running. The curated Hermes Agent and OpenClaw templates already supervise their gateways.

The Quickstart covers the rest: taking screenshots, clicking, typing, and running commands over HTTP.

Should you turn your Hetzner bootstrap script into an Orgo template?

If you used to rebuild agent servers on Hetzner by re-running the same setup script, an Orgo template is the closer fit. A template is one declarative file that describes the hardware, software, services, secrets, and what the user sees on connect. Orgo builds it once into a golden snapshot that every launch starts from in seconds (Templates).

Curated templates from Orgo (Coding with Claude Code and Codex, OpenClaw, and Hermes Agent) launch on any paid plan, and a free account can launch them by the hour on its credit. Publishing and building your own templates requires a Scale plan or higher. For more, see Orgo templates and triggers.

What is actually different after you move?

• Hetzner does, Orgo doesn't: a general-purpose server you fully own, with arbitrary services and ports, and managed networking.
• Orgo does, Hetzner doesn't out of the box: a persistent desktop computer with a built-in agent control API, online in seconds, with no OS, firewall, or TLS to set up.
• Networking: a Hetzner server can have its own public IPv4 and IPv6 addresses. An Orgo computer has none of its own. You and your agent reach it through Orgo's API with your API key, you can watch it over VNC in the browser, and a Linux computer can also take direct SSH with your own key.
• Backups: both platforms keep them. Hetzner keeps up to seven daily backups per server once you enable them, plus snapshots until you delete them. Orgo backs up running Linux and Windows computers daily and keeps each backup for 7 days.

Persistence also works differently. An Orgo computer's disk and files persist across stop and start, but memory and running processes do not, and the computer can come back on another host with a different IP (Stop computer). On a Linux computer without a GPU that is not billed by the hour, suspend keeps memory and running processes too; see how to pause, fork, or clone an agent's computer. Plan for your agent to resume from disk, not from a live process.

FAQ

Is Orgo a drop-in replacement for a Hetzner server?

No. Orgo is not a general cloud platform; it runs persistent computers for AI agents. Keep general servers and public-facing services on Hetzner.

Can I keep my backend on Hetzner and move only the agent?

Yes. Keep the backend services on Hetzner and move only the computer the agent works on to Orgo.

Does an Orgo computer get a public IP like a Hetzner Primary IP?

No. An Orgo computer has no public IP of its own. You reach it through Orgo's API with your API key, or over direct SSH with your own key on a Linux computer. Customers cannot publish any other port from it to the internet today.

What replaces a Hetzner Snapshot on Orgo?

POST /computers/{id}/clone copies a computer's disk into a new computer right away (Clone computer). Unlike a Hetzner Snapshot, it is not an image you keep on its own. For a repeatable starting point across many computers, a template's golden snapshot is the closer match.

What is the largest Orgo computer I can create?

Up to XL (6 vCPU, 32 GB RAM) on your own, within your plan's limits, with up to 300 GB of disk if you add storage. 2XL (8 vCPU, 64 GB RAM, 300 GB disk) is set up on request.

Can I run systemd services on an Orgo computer?

No. Orgo computers do not run systemd. Use a detached tmux session, which does not survive a restart, or, on a Scale plan or higher, a template of your own that declares the process as an app. The curated Hermes Agent and OpenClaw templates already keep their gateways running.

How do I move files larger than 10 MB?

Pull them in from inside the computer with git or curl through /bash, or use the two-step large upload, which takes files up to 2 GB.

Moving from a DigitalOcean Droplet instead?

The same steps apply. See Migrate from DigitalOcean.

Do I bring my own agent?

You can. Orgo provides the computer, and any agent that works through its HTTP API, CLI, or MCP can drive it: Claude, OpenAI, or Gemini models, Hermes Agent, OpenClaw, or your own agent loop.

Related

• Best hosting for OpenClaw and Hermes Agent
• Orgo templates and triggers
• How do you pause, fork, or clone an AI agent's computer?
• How to scale AI agent computers to thousands on Orgo
• What is computer use?