CapabilitiesWays to drive it
Create from the website
Start a machine by clicking in the provider's dashboard, with no terminal.
Short answer: 7 of 16 providers offer it fully: Agent 37, Blaxel, Daytona, InstaBox, Lizard, Morph and Runtime. Checked 29 October 2026.
Who offers it
Part of Ways to drive it, which explains why it matters.
Fully: Agent 37, Blaxel, Daytona, InstaBox, Lizard, Morph and Runtime. Not at all: Boat, boxd, Cloudflare Sandbox, E2B, Modal, Sandboxer, Sprites, Tensorlake and Vercel Sandbox.
- Agent 37Yes
The dashboard can create an instance, not just list one.
docs-confirmed “You can create instances from our dashboard or provision them programmatically through the Agent 37 Cloud API” Source
- BlaxelYes
The console has a Deploy from console path that asks for image, resources, TTL and region.
docs-confirmed “Click **+Create sandbox** -> **Deploy from console**.” Source
- DaytonaYes
The Playground creates sandboxes in the browser and opens terminal and desktop tabs.
docs-confirmed “Daytona provides an interactive environment ("Playground") for creating sandboxes” Source
- InstaBoxYes
The Machines page has a Create machine button that matches the CLI call.
docs-confirmed “In the dashboard, **Create machine** on the **Machines** page does what `instabox create` does.” Source
- LizardYes
The dashboard creates a sandbox after you pick a template, region, size and lifetime.
docs-confirmed “The dashboard lets you create and manage Sandboxes without code.” Source
- MorphYes
The devbox dashboard creates a machine from a template or a snapshot.
docs-confirmed “Create a devbox from a template (or a snapshot)” Source
- RuntimeYes
The console's Search or create box starts a sandbox from the browser.
docs-confirmed “**Search or create** , or ⌘K (Ctrl+K), opens one search box. It goes to any page or resource and starts anything.” Source
- BoatNo
The dashboard is for account work such as keys, billing and members; every machine starts with the CLI.
inferred “| **[Dashboard](https://boat.dev/dashboard)** | one-off work, and the things that must not be automatable | browser sign-in |” Source
- boxdNo
The console shows machines, keys and backups; the quickstart creates the first machine with the CLI.
inferred “Install the CLI, create your first machine” Source
There is no sandbox console: a sandbox is a name inside your Worker, and the dashboard manages the Worker.
inferred “Your Worker reaches each sandbox by name.” Source
- E2BNo
The console manages keys, templates and billing; sandboxes are created by code.
inferred “This guide will show you how to start your first E2B Sandbox.” Source
- ModalNo
The dashboard reports metrics and the CLI attaches to running sandboxes; creating one is a code call.
inferred “sb = modal.Sandbox.create(app=sb_app)” Source
The dashboard opens desktops and manages keys and members; the quickstart starts the first sandbox with `sbx`.
inferred “Install the sbx CLI, sign in, and run your first sandbox in about two minutes.” Source
- SpritesNo
Sprites are created from the command line; there is no browser console for creating one.
inferred “sprite create - Create a new sprite” Source
The console lists sandboxes, logs and billing; the docs create sandboxes from the CLI or the SDK.
inferred “Create one on demand from the CLI or the SDK.” Source
The dashboard can stop or delete a sandbox but the docs give no way to create one there.
inferred “From the dashboard you can stop the current session or permanently remove the sandbox.” Source
Related
Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.