Integrate once
Build against the same create, get, runCommand, and delete operations for every supported adapter.
Provider-neutral sandbox API
One API. Your choice of sandbox provider.
Wildflower Computer gives applications one stable API for creating, executing in, and deleting persistent sandboxes across 12 supported providers. Bring your own credentials and choose a different provider for new sandboxes without rewriting the lifecycle.
Let sandboxes bloom→
creategetrundeleteFEATURED GUIDES
5 providers in detail12 adapters in the OpenAPI contract.One lifecycle / many backends
Providers change. Your contract doesn’t.
Each sandbox cloud has its own API and lifecycle details. Wildflower Computer keeps the application-facing operations narrow while provider selection stays explicit.
Choose per sandbox
Select the provider when you create. Routing stays deliberate, visible, and under your application’s control.
Return to the same state
A routeable ID sends later operations back to the same provider-native sandbox.
The contract / in practice
The abstraction is visible in the code.
Use the TypeScript SDK or raw HTTP. Both examples create a provider-backed sandbox, run a command, and delete it.
TypeScript SDK
import { Wildflower } from "@wildflowercomputer/sdk";const client = new Wildflower({ wildflowerApiKey: process.env.WILDFLOWER_API_KEY,});const sandbox = await client.sandboxes.create({ provider: "e2b", image: "base", timeout: 300,});const handle = client.sandboxes.attach(sandbox.id);await handle.waitUntilReady();const result = await handle.runCommand({ command: "echo hello",});await handle.writeText("/tmp/hello.txt", "hello");console.log(result.stdout, result.stderr, result.exitCode);await handle.delete();HTTP / cURL
export WILDFLOWER_URL="http://localhost:8080"export WILDFLOWER_API_KEY="<your-wildflower-api-key>"export PROVIDER_API_KEY="$E2B_API_KEY"sandbox_id=$( curl -fsS "$WILDFLOWER_URL/v1/sandboxes" \ -H "Authorization: Bearer $WILDFLOWER_API_KEY" \ -H "Content-Type: application/json" \ -H "X-Provider-Api-Key: $PROVIDER_API_KEY" \ -H "Idempotency-Key: logical-create-42" \ --data '{"provider":"e2b","image":"base","timeout":300}' | jq -r '.id')curl -fsS "$WILDFLOWER_URL/v1/sandboxes/$sandbox_id/exec" \ -H "Authorization: Bearer $WILDFLOWER_API_KEY" \ -H "Content-Type: application/json" \ -H "X-Provider-Api-Key: $PROVIDER_API_KEY" \ --data '{"command":"echo hello > /tmp/hello && cat /tmp/hello"}'curl -fsS -X DELETE "$WILDFLOWER_URL/v1/sandboxes/$sandbox_id" \ -H "Authorization: Bearer $WILDFLOWER_API_KEY" \ -H "X-Provider-Api-Key: $PROVIDER_API_KEY"Where Wildflower Computer sits
The interface, not the infrastructure.
Wildflower Computer does not host the sandbox. It forwards each lifecycle operation to the adapter for the provider chosen at creation.
Existing sandboxes remain attached to their selected provider. Wildflower Computer does not automatically fail over between providers.
Read the API conceptsApplicationYour application
create · get · runCommand · delete
Stable contractWildflower Computer APIProvider adapterBlaxel
Provider adapterE2B
Provider adapterDaytona
Provider adapterRunloop
Provider adapterFly.io Sprites
Clear boundaries / fewer surprises
Two choices. One clean boundary.
Your application chooses and calls the model provider. Wildflower Computer handles sandbox operations only.
MODEL PROVIDER ≠ SANDBOX PROVIDER
Models think. Sandboxes execute.
Pick either independently. Wildflower Computer does not execute models or provide an agent runtime.
Read the boundaryBRING YOUR OWN KEY
Credentials stay under your control.
Authorization: Bearer <key>X-Provider-Api-Key: <key>Connect an encrypted project profile or send an ephemeral inline override for the operation.
Documentation / current contract
Go from first sandbox to the full contract.
Direct answers / current product
What Wildflower Computer is—and isn’t.
Short factual answers to the questions developers and search systems ask first.
What is Wildflower Computer?
A provider-neutral sandbox API that connects applications to 12 supported providers using customer-owned credentials.
Read how the sandbox API worksWhich sandbox providers are supported?
AWS AgentCore, Blaxel, ASCII Box, Cloudflare Sandbox, E2B, Novita Agent Sandbox, Daytona, Modal, Runloop, Smol, Fly.io Sprites, and Vercel Sandbox.
Review tested compatibilityHow are provider credentials handled?
PostgreSQL mode encrypts project profiles at rest. Static local mode keeps profiles in memory, and inline overrides remain ephemeral.
Understand the credential boundaryIs Wildflower Computer a sandbox provider?
No. It is the application-facing API and adapter layer; the selected provider hosts the sandbox.
Explore supported providersHow is it different from E2B or Daytona?
E2B and Daytona provide sandbox infrastructure. Wildflower Computer exposes one lifecycle across them and other supported providers.
Compare E2B and Daytona sandbox behaviorWhich programming languages are supported?
The HTTP API works from any language. Generated clients currently exist for TypeScript, Python, Rust, Go, and Zig.
Explore generated sandbox SDKsOPEN ROUTE / PERSISTENT STATE
Keep your sandbox options open.
Create persistent sandboxes on the provider you choose, through one narrow API.
Build the first lifecycle