Reference / compatibility

Tested provider compatibility.

The Wildflower Computer API versions its own contract under v1. Adapter tests pin the upstream request and response shapes listed here; callers do not select these provider contract versions.

Detailed compatibility matrix

ProviderEvidenceCreate imageLifetimeCommand outputConnection context
BlaxelPreview / contract-testedRuntime image supportedTimeout sent as runtime TTLSeparate stdout and stderrX-Provider-Workspace
E2BPreview / contract-testedTemplate ID supportedTimeout in secondsSeparate stdout and stderrNone
DaytonaLaunch tier / live-provenContainer image supportedRounded up to TTL minutesCombined output in stdoutNone
RunloopPreview / contract-testedBlueprint name supportedMaximum 172800 secondsSeparate stdout and stderrNone
Fly.io SpritesLaunch tier / live-provenFixed environmentNo timeout optionSeparate stdout and stderrNone

OpenAPI 0.8.0 additionally covers AWS AgentCore, ASCII Box, Cloudflare Sandbox, Novita Agent Sandbox, Modal, Smol, and Vercel Sandbox. Their exact create inputs and capability descriptors are available in the generated provider reference. These adapters have keyless contract coverage, not current live credential proof.

Daytona and Fly.io Sprites are the initial launch tier and completed the full persistent lifecycle on private staging on July 28, 2026. All other adapters remain preview until an equivalent current credential smoke is recorded.

Tested upstream contracts

Blaxel

E2B

Daytona

Runloop

Fly.io Sprites

Shared response contract

Sandbox responses expose a normalized ID, provider, status, and metadata. Execution responses expose sandboxId, stdout, stderr, and exitCode. Provider-native IDs remain available atmetadata.nativeProviderId, and provider runtime versions appear at metadata.nativeProviderVersion when available.

Shared error contract

The current stable error code set includes invalid requests and idempotency keys, idempotency conflicts or uncertain outcomes, missing keys, invalid sandbox IDs, provider validation failures, authentication failures, missing sandboxes, rate limits, provider unavailability, provider errors, and internal errors. Provider response bodies are not forwarded because they may contain credentials or customer content.

Compatibility is not failover

A supported adapter means that the lifecycle is implemented and covered by contract tests. Wildflower Computer does not retry on a different provider, migrate an existing sandbox, or promise equivalent performance and pricing.

Machine-readable evidence