Wildflower Computer
Open console

Guides / implementation

Build a portable sandbox boundary.

These guides show how to adopt the shared lifecycle without pretending that provider-specific images, lifetimes, or existing sandbox state are interchangeable.

View as MarkdownOpen this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in CursorSend this page to Cursor chatDownload OpenAPIUse the machine-readable contract

Migration guides

Migrate application calls from E2B

Put the shared Wildflower Computer lifecycle around new E2B sandboxes, then make future provider choice explicit.

Read the E2B migration guide

Migrate application calls from Daytona

Keep container-image and TTL semantics visible while moving lifecycle calls behind the provider-neutral API.

Read the Daytona migration guide