Deno Sandbox vs Freestyle

Deno Sandbox

Secrets stay outside the microVM and are substituted only on outbound requests to approved hosts, and an allowlist limits egress. The service is still in beta, sandboxes need the $20 Pro plan, lifetime is capped at 30 minutes, and no sandbox operation appears in the published OpenAPI document.

Freestyle

A public OpenAPI 3.1 file describes 88 operations with a stable error code on every failure, and per-VM identity tokens keep the team API key away from end users. No terms of service, product privacy policy, request rate limit or incident history was found, and the only SDK is TypeScript.

Deno Sandbox

1. Set DENO_DEPLOY_TOKEN to an organisation token (prefix ddo_) from Settings in console.deno.com. The organisation must be on Pro or above
2. Pass allowNet on every Sandbox.create(). The Security page says outbound access is unrestricted when it is omitted
3. Pass credentials through secrets with a hosts list, not env, so code in the VM sees only a placeholder
4. The default timeout ends the VM when the client disconnects. Pass a duration such as "10m" and reconnect with Sandbox.connect({ id }), up to 30 minutes
5. Create volumes in ord and start the sandbox in ord. A volume mounts only in its own region
6. exposeHttp URLs are public with no authentication. Treat the random subdomain as a secret

Freestyle

1. Send a firewall object on every POST /v5/vms. It is required, and a VM with no rules has no outbound internet
2. Ask the owner to run freestyle login in a browser once, then mint a key with freestyle tokens create --output json
3. Do not retry an exec that answers 409 VM_NON_RESPONSIVE. The command may already have run
4. Keep exec-await under its 300,000 ms cap and use a PTY session or x-freestyle-background-after-secs for longer work
5. Call the /v5 paths. The unversioned duplicates in the OpenAPI file are marked deprecated