Integrations

Provider coverage without false equivalence

The catalog is broad, but the integration status is intentionally precise. A listing is not presented as a working adapter.

Current built-in adapters

24 provider adapters are implemented directly in Elixir. Provider-specific protocols that cannot be implemented directly connect through the standard driver contract.

Integration matrix

ProviderStatusCapabilitiesSource
Docker built in 9 official docs ↗
Local development built in 5 official docs ↗
Runloop built in 16 official docs ↗
Tensorlake built in 18 official docs ↗
E2B built in 15 official docs ↗
Daytona built in 17 official docs ↗
Modal driver 16 official docs ↗
Vercel Sandbox built in 10 official docs ↗
Blaxel built in 17 official docs ↗
Sprites built in 12 official docs ↗
InstaVM built in 8 official docs ↗
Beam Sandboxes built in 13 official docs ↗
Cloudflare Sandbox built in 12 official docs ↗
CodeSandbox driver 13 official docs ↗
Upstash Box built in 11 official docs ↗
HopX built in 13 official docs ↗
Declaw built in 9 official docs ↗
Namespace Devboxes built in 11 official docs ↗
Northflank Sandboxes driver 14 official docs ↗
Fly Machines driver 14 official docs ↗
Kubernetes Agent Sandbox driver 17 official docs ↗
OpenSandbox built in 16 official docs ↗
NVIDIA OpenShell driver 8 official docs ↗
Microsandbox driver 10 official docs ↗
AIO Sandbox driver 10 official docs ↗
Sandbox0 built in 13 official docs ↗
Zeroboot driver 8 official docs ↗
Google Cloud Run sandboxes driver 8 official docs ↗
Deno Subhosting catalog 7 official docs ↗
exe.dev driver 9 official docs ↗
Morph Devboxes built in 12 official docs ↗
Agent Sandbox built in 11 official docs ↗
Archil built in 8 official docs ↗
Amazon Bedrock AgentCore Code Interpreter catalog 6 official docs ↗
Azure Container Apps dynamic sessions built in 5 official docs ↗
Together Code Interpreter built in 4 official docs ↗
Scrapybara built in 7 official docs ↗
Browserbase catalog 6 official docs ↗
Kernel catalog 5 official docs ↗

Configure a driver-backed provider

{
  "name": "Fly Machines via our driver",
  "kind": "fly_machines",
  "token": "fly_...",
  "config": {
    "driver_url": "https://fly-driver.internal.example"
  }
}