Featured provider guides
Preview / contract-tested / blaxel
Blaxel
Persistent Blaxel sandboxes addressed through an API key and workspace.
- Image
- Runtime image supported
- Lifetime
- Timeout sent as runtime TTL
- Output
- Separate stdout and stderr
Preview / contract-tested / e2b
E2B
Persistent sandboxes created from an E2B template.
- Image
- Template ID supported
- Lifetime
- Timeout in seconds
- Output
- Separate stdout and stderr
Launch tier / live-proven / daytona
Daytona
Persistent sandboxes created from a container image.
- Image
- Container image supported
- Lifetime
- Rounded up to TTL minutes
- Output
- Combined output in stdout
Preview / contract-tested / runloop
Runloop
Persistent Runloop Devboxes created from an optional Blueprint.
- Image
- Blueprint name supported
- Lifetime
- Maximum 172800 seconds
- Output
- Separate stdout and stderr
Launch tier / live-proven / sprites
Fly.io Sprites
Persistent Sprites with a fixed environment and automatic sleep.
- Image
- Fixed environment
- Lifetime
- No timeout option
- Output
- Separate stdout and stderr
All providers in the current contract
The OpenAPI 0.8.0 provider enum covers AWS AgentCore, Blaxel, ASCII Box, Cloudflare Sandbox, E2B, Novita Agent Sandbox, Daytona, Modal, Runloop, Smol, Fly.io Sprites, and Vercel Sandbox. See the generated provider reference for exact create inputs and connection context.
GET /v1/providersreturns each stable provider ID, display name, normalized published price, and capabilities. The provider pricing referenceadds the complete published-rate calculation and official sources while keeping billing caveats visible instead of presenting the result as an invoice forecast.
Daytona and Fly.io Sprites are the initial launch tier because both have a current full lifecycle smoke on private staging. AWS AgentCore, Blaxel, Cloudflare Sandbox, E2B, Modal, Runloop, and Vercel Sandbox remain preview adapters with deterministic keyless contract coverage, not current live credential proof.
What “supported” means
Each provider shown here has an adapter in the current API, provider-contract fixtures, normalized lifecycle behavior, and generated SDK inputs. Support does not mean that every provider behaves identically or that Wildflower Computer retries an operation elsewhere.