Daytona vs Morph Cloud

Daytona

API keys with per-action scopes, so an agent can create sandboxes without being able to delete them. The container class shares the host kernel. Only the VM classes get their own.

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.

Daytona

1. Pick a Linux VM class for untrusted code or when memory must survive a pause. Container sandboxes stop and archive instead
2. Set autoStopInterval yourself. The 15-minute idle default can stop a sandbox while the agent is still thinking
3. Give the agent a key without delete:sandboxes if it shouldn't destroy work
4. Read Retry-After-{throttler} on a 429 before retrying sandbox creation
5. Check the organisation's tier before relying on outbound calls from inside the sandbox

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