Orgo - Cloud computers for AI agents

You run workloads on Hetzner Cloud as Servers: Linux VMs you provision, SSH into, and administer yourself. Orgo gives an AI agent a full, always-on computer (browser, shell, and files) that it drives over the HTTP API, the orgo CLI, or MCP. This page maps the two and shows the cleanest way to move.

Doing this with an agent? Paste this page into Claude Code or Codex as context. Every command is copy-paste and self-contained, so the agent can run the switch end to end.

How the platforms map

Hetzner Cloud	Orgo
Server (Linux VM)	A computer (`POST /computers`)
`ssh root@<server-ip>`	`POST /computers/{id}/bash`, or `orgo ssh <name>`
Server disk	The computer’s disk, persistent by default
Snapshot	`POST /computers/{id}/clone`
Primary/Floating IP + Firewall	No public per-computer IP. Reach it via the authenticated proxy: `www.orgo.ai/api/desktops/{instance_id}/proxy/<path>`

Move your state

Orgo runs any shell command inside the computer via POST /computers/{id}/bash. The cleanest transfer is to pull your data in from inside the computer: no size limits, no laptop round-trip. Recommended: via a Git repo. Push the state you want to keep to a private repo, then clone it inside the Orgo computer:

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 dir) to a private repo.

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 ~"}'

Alternatives

Any URL. Host the tarball anywhere reachable and curl/wget it from inside the computer the same way. A Git repo is the tidiest, versioned option.
Small files (< 10 MB). POST /files/upload drops a file straight onto the computer. It caps at 10 MB. For larger state, use the Git or URL pull above, or split into < 10 MB batches.

Reference: Connecting to the server, Migrate data (Hetzner’s own doc uses scp).

Set up on Orgo

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

See the Quickstart for the full control surface (bash, exec, screenshot, click/type).

What’s different

Neutral, both directions:

Hetzner does, Orgo doesn’t: a general-purpose Linux server you fully own, with arbitrary services and ports, managed networking (primary/floating IPs, firewalls, private networks), and built-in daily backups + persistent snapshots.
Orgo does, Hetzner doesn’t out of the box: a persistent GUI computer with a built-in agent-control API (screenshot / click / type), online in seconds, with nothing to administer. You manage no OS, no firewall, and no TLS. A Hetzner server has no public network interface until you assign a Primary IP. Orgo exposes its API through an authenticated proxy instead.

Rule of thumb: keep general server workloads and public-facing services on Hetzner. Move to Orgo when the job is an agent operating a durable computer or browser.

Reference

Hetzner Cloud Servers

Their VM

Migrate data

scp file transfer

Orgo Quickstart

Control a computer over HTTP

Move an agent (Hermes/OpenClaw)

Full state-preserving playbook

Get Started

Guides

Migrations

Templates

Model integrations

Migrate from Hetzner

How the platforms map

Move your state

Set up on Orgo

What’s different

Reference

Hetzner Cloud Servers

Migrate data

Orgo Quickstart

Move an agent (Hermes/OpenClaw)

​How the platforms map

​Move your state

​Set up on Orgo

​What’s different

​Reference

Hetzner Cloud Servers

Migrate data

Orgo Quickstart

Move an agent (Hermes/OpenClaw)

How the platforms map

Move your state

Set up on Orgo

What’s different

Reference