Morph Cloud vs Runloop Devboxes

Morph Cloud

Pause and snapshot keep memory and running processes, and one call branches an instance into several copies. A public OpenAPI file covers 69 operations. No terms of service, privacy policy or security page was found, the free plan includes no compute credit, and the changelog holds one entry from November 2024.

Runloop Devboxes

Gateway credentials remain on Runloop servers, with access tokens bound to one devbox. Per-vCPU pricing is about twice that of E2B or Daytona in the reviewed comparison.

Morph Cloud

1. Set ttl_seconds and ttl_action when starting an instance. Nothing in the docs stops an instance with no TTL from billing MCUs
2. Pass auth_mode: api_key when exposing an HTTP service. The default is none, which makes the URL public
3. Enable wake_on_ssh before calling exec on an instance that may be paused. There is no separate exec wake setting
4. Use /api/instance/list and /api/snapshot/list with page and limit (default 50, maximum 1,000). The plain list routes return everything
5. On a 503 from snapshot, branch, pause or reboot, wait for the Retry-After value before repeating the call

Runloop Devboxes

1. Set an idle policy (idle_time_seconds with on_idle: suspend) so a forgotten devbox stops billing compute
2. Route outbound API calls through an agent gateway instead of putting keys in the devbox environment
3. Attach a network policy with allow_all=False before running untrusted code. Egress is open by default
4. Restart background services after every resume. Nothing in memory survives
5. Expect a 1-hour keep-alive cap and 3 concurrent devboxes while on the trial