Orgo - Cloud computers for AI agents

You run apps on Fly.io as Machines: fast-booting Firecracker microVMs grouped under an App, with optional Volumes for persistence. 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

Fly.io	Orgo
App + Machine (Firecracker microVM)	A computer (`POST /computers`)
`fly ssh console` (over WireGuard)	`POST /computers/{id}/bash`, or `orgo ssh <name>`
Volume (persistent storage)	The computer’s disk, persistent by default
Volume snapshot	`POST /computers/{id}/clone`
Anycast IPs + Fly Proxy (public inbound)	No public per-computer IP. Reach it via the authenticated proxy: `www.orgo.ai/api/desktops/{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 upload cap beyond the computer’s free disk, and no laptop round-trip. A /bash call runs for 200 seconds unless you send timeout, which goes up to 300, so start a longer pull in a detached tmux session. Recommended: via a Git repo. Push the state you want to keep to a private repo, then clone it inside the Orgo computer:

# Machines have no public SSH; this runs over Fly's private WireGuard mesh.
fly ssh console -a YOUR_APP -C "tar czf /tmp/state.tgz -C /root ."
fly ssh sftp get -a YOUR_APP /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.
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.

Reference: Fly SSH & SFTP, Fly Volume snapshots.

Set up on Orgo

One call provisions the computer. Install your software with the same /bash endpoint.

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:

Fly does, Orgo doesn’t: general-purpose compute and PaaS, with arbitrary long-running services, public inbound via Anycast shared/dedicated IPs, multi-region deployments, and opt-in persistence via Volumes (a Machine’s base filesystem is ephemeral).
Orgo does, Fly doesn’t out of the box: a persistent GUI computer with a built-in agent-control API (screenshot / click / type) and no server to administer. You manage no OS, no firewall, and no TLS.

Rule of thumb: keep general server workloads and public-facing services on Fly. Move to Orgo when the job is an agent operating a durable computer or browser. Fly’s public-networking and multi-region features have no 1:1 Orgo analog. Reach the computer’s own API through the authenticated proxy instead.

Reference

Fly Machines

Compute primitive

Fly SSH & SFTP

Extract files

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 Fly.io

How the platforms map

Move your state

Set up on Orgo

What’s different

Reference

Fly Machines

Fly SSH & SFTP

Orgo Quickstart

Move an agent (Hermes/OpenClaw)

​How the platforms map

​Move your state

​Set up on Orgo

​What’s different

​Reference

Fly Machines

Fly SSH & SFTP

Orgo Quickstart

Move an agent (Hermes/OpenClaw)

How the platforms map

Move your state

Set up on Orgo

What’s different

Reference