Migrate from Hetzner

​

How the platforms map

​

Move your state

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

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

​

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,"cpu":4}'
# → save the returned id as $COMPUTER_ID, then run your installer via /bash

​

What’s different

• Hetzner does, Orgo doesn’t: a general-purpose Linux server you fully own - arbitrary services and ports, CPU/RAM rescaling, 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 desktop with a built-in agent-control API (screenshot / click / type), sub-second boot, and nothing to administer - no OS, firewall, or TLS to manage. (A Hetzner server has no public network interface until you assign a Primary IP; Orgo exposes its API through an authenticated proxy instead.)

​

Reference