Freestyle vs SPACE

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.

SPACE

Once deployed, SPACE's native API has a public OpenAPI 3.1 contract, stable error codes with a retryable flag and 24-hour idempotency keys, and egress and credential controls sit outside the VM. A person must first deploy it on a Linux x86_64 host with KVM and Kubernetes. Version 0.8.0 has no tagged release, changelog or public container images.

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

SPACE

1. Ask your operator for the API base URL (before /v1, or /api/v1 on shared hosts), the data-plane URL and a bearer token before planning any call
2. Poll the returned operation until it succeeds and the sandbox is running before creating a command. A 202 response is not readiness
3. Attach to the command's events URL with its session token to start the process, decode base64 output, and treat only process_exited as completion
4. Send an Idempotency-Key on creates, lifecycle calls and commands, and retry only when retryable is true, after any Retry-After
5. Save output as it arrives. Reconnecting with Last-Event-ID returns resync_required, not the missed output