Skip to main content
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 Linux desktop (browser + shell + files) that it drives over an HTTP API. 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

Move your state

Orgo runs any shell command inside the computer via POST /computers/{id}/bash, so the cleanest transfer is to pull your data in from inside the machine - 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:
Alternatives
  • 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.
Reference: Fly SSH & SFTP, Fly Volume snapshots.

Set up on Orgo

One call provisions the computer; then install your software with the same /bash endpoint.
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/PaaS - 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 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.
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 desktop or browser. Fly’s public-networking and multi-region features have no 1:1 Orgo analog - reach the desktop’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