Browse Documentation

Reference / provider adapters

Current provider support.

Wildflower Computer supports 12 adapters. The generated capability directory covers every one; 5 direct providers also have evidence-backed behavior guides. Provider selection is explicit at creation and remains fixed for that sandbox.

Detailed behavior guides

Blaxel Preview / contract-tested / 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

A workspace is required on every lifecycle request.

Detailed Blaxel support
E2B Preview / contract-tested / e2b

Persistent sandboxes created from an E2B template.

Image
Template ID supported
Lifetime
Timeout in seconds
Output
Separate stdout and stderr

Defaults to the base template and a 300-second lifetime when omitted.

Detailed E2B support
Daytona Launch tier / live-proven / daytona

Persistent sandboxes created from a container image.

Image
Container image supported
Lifetime
Rounded up to TTL minutes
Output
Combined output in stdout

Wildflower Computer generates a one-line Dockerfile from the image value.

Detailed Daytona support
Runloop Preview / contract-tested / runloop

Persistent Runloop Devboxes created from an optional Blueprint.

Image
Blueprint name supported
Lifetime
Maximum 172800 seconds
Output
Separate stdout and stderr

The default starter image is used when a Blueprint name is omitted.

Detailed Runloop support
Fly.io Sprites Launch tier / live-proven / sprites

Persistent Sprites with a fixed environment and automatic sleep.

Image
Fixed environment
Lifetime
No timeout option
Output
Separate stdout and stderr

A cold Sprite may report stopped and wakes on its first command.

Detailed Fly.io Sprites support

Blaxel behavior

  • The image is a Blaxel runtime image and defaults to blaxel/base-image:latest.
  • An optional timeout in seconds is sent to Blaxel as the runtime TTL.
  • The adapter returns the provider process stdout, stderr, and exit code through the shared execution result.
  • The provider credential is a blaxel api key.

E2B behavior

  • The image field is interpreted as an E2B template ID. It defaults to base when omitted.
  • The timeout is a sandbox lifetime in seconds and defaults to 300 when omitted.
  • The adapter preserves separate stdout and stderr streams and returns the command exit code.
  • The provider credential is a e2b api key.

Daytona behavior

  • The image field is a container image. The adapter generates a one-line Dockerfile using that image.
  • The API accepts seconds and the adapter rounds them up to whole Daytona TTL minutes.
  • Daytona returns combined command output. The adapter places it in stdout and returns an empty stderr.
  • The provider credential is a daytona api key.

Runloop behavior

  • The image field is interpreted as a Runloop Blueprint name. The default starter image is used when omitted.
  • The timeout becomes the Devbox maximum lifetime and cannot exceed 172800 seconds.
  • The adapter waits for command completion and returns stdout, stderr, and the exit status. Truncated output is reported as an error.
  • The provider credential is a runloop api key.

Fly.io Sprites behavior

  • Sprites uses a fixed environment. The adapter rejects image rather than silently ignoring it.
  • Sprites automatically sleeps and persists until deletion. The adapter rejects timeout.
  • The adapter preserves separate stdout and stderr frames and returns the command exit code.
  • The provider credential is a fly.io sprites api token.
Support does not mean failover

The API and adapter contract tests cover these providers. Wildflower Computer does not automatically retry an operation on a different provider or migrate sandbox state.

Live proof is narrower than adapter coverage

Daytona and Fly.io Sprites are the initial launch tier with a current full private-staging lifecycle smoke. The remaining adapters are preview: their lifecycle boundaries are contract-tested without current live provider credentials.

For tested upstream contracts and machine-readable evidence, use theprovider compatibility matrix andOpenAPI downloads.