Sandbox guide

CapabilitiesTeams and accounts

Team workspace

Several people share machines, billing and keys.

15 yes1 with a catch0 no0 not published

Who offers it

Part of Teams and accounts, which explains why it matters.

Fully: Agent 37, Blaxel, Boat, boxd, Daytona, E2B, InstaBox, Lizard, Modal, Morph, Runtime, Sandboxer, Sprites, Tensorlake and Vercel Sandbox. With a catch: Cloudflare Sandbox.

  • Agent 37Yes

    A workspace owns the keys, the wallet and every instance, with members invited by email.

    docs-confirmed “A workspace is the account: it owns the API keys” Source

  • BlaxelYes

    Workspaces hold members, roles and service accounts.

    docs-confirmed “There are three roles that a user or service account can have in a workspace” Source

  • BoatYes

    An organisation has one plan and one wallet, and the owner invites people by email.

    docs-confirmed “It has one plan, one wallet, and members who run sandboxes on it.” Source

  • boxdYes

    Every account is an organisation; machines can be private or shared with the org.

    pricing-page “Every account is an organization. Invite your team, share machines, and draw from one credit balance.” Source

  • DaytonaYes

    A collaborative organisation holds members and shared sandboxes.

    docs-confirmed “Every member of an organization can address that organization's running sandboxes” Source

  • E2BYes

    A workspace holds projects, who can reach them, and one billing account.

    docs-confirmed “A workspace groups your E2B projects and holds their billing.” Source

  • InstaBoxYes

    Organisations and workspaces carry members, roles, keys and one allowance.

    docs-confirmed “Every member uses the org's sandboxes” Source

  • LizardYes

    Workspaces hold projects and members; inviting people adds no seat fee.

    docs-confirmed “Lizard groups services into projects and projects into workspaces.” Source

  • MorphYes

    Devboxes are shareable to anyone in the organisation, and you can create several.

    docs-confirmed “devboxes are shareable live via URL to anyone in your Morph Cloud organization, and you can create multiple organizations as needed.” Source

  • RuntimeYes

    One account holds as many people as you need, each with a role.

    docs-confirmed “One Runtime account can have as many people as you need.” Source

  • SandboxerYes

    An organisation is a shared wallet with one plan, one balance and its members.

    docs-confirmed “An **organization** is a shared wallet: one plan, one balance, and the members who run sandboxes on it.” Source

  • SpritesYes

    Sprites uses your Fly.io account and organisation, including org switching in the CLI.

    docs-confirmed “Sprites uses your Fly.io account for authentication” Source

  • TensorlakeYes

    Organisations hold projects and members, with project-level access.

    docs-confirmed “Organizations are the top-level entity in our system.” Source

  • Vercel SandboxYes

    A Vercel team holds members, seats and billing, with unlimited free viewer seats.

    pricing-page “Unlimited free Viewer seats with read-only access” Source

  • Cloudflare SandboxWith a catch

    The catch: People share the Cloudflare account and its Workers, but there is no per-sandbox sharing or sandbox workspace.

    Sandbox names carry no owner, so your Worker must derive them from the caller.

    docs-confirmed “Members and permissions” Source

Related

Other capabilities in this feature

Where it decides the choice

The feature

Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.