Why Wildflower Computer exists
Sandbox providers expose different creation inputs, lifecycle states, and execution protocols. Wildflower Computer puts one small application-facing contract in front of those differences while keeping meaningful provider-specific behavior visible.
What it does
- Creates a persistent sandbox on one selected provider.
- Returns a routeable ID for later get, runCommand, and delete calls.
- Normalizes sandbox state, metadata, command results, and errors.
- Generates TypeScript, Python, Rust, Go, and Zig clients.
- Supports encrypted project profiles and ephemeral credential overrides.
What it does not do
- Host the provider-native sandbox.
- Move existing sandbox state between providers.
- Automatically fail over, retry elsewhere, or resell provider capacity.
- Operate as a general-purpose secret manager.
- Execute AI models or provide a completed agent platform.
Separate projects, one contract
The API and generated SDKs live in the Wildflower source project. This website is a separate static Astro project. The OpenAPI document and generated provenance connect the public documentation to the implemented contract.