Sandbox guide

CapabilitiesSizes and regions

GPUs

Machines with a graphics processor, for running AI models or other GPU work inside the sandbox.

2 yes1 with a catch11 no2 not published

Who offers it

Part of Sizes, regions and hardware, which explains why it matters.

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

  • DaytonaYesup to 8 GPUs

    Graphics machines are preemptible, ignore your region choice and cannot use the free credit.

    docs-confirmed “each GPU adds up to 16 vCPUs, 192GB RAM, and 512GB disk” Source

  • TensorlakeWith a catchby request

    The catch: Graphics machines exist but you have to ask on Slack to be given access, and they cannot be resized or run virtual machines inside.

    docs-confirmed “GPU sandboxes are available by request.” Source

  • Agent 37Nono GPU

    Note: No graphics processor is offered on any machine or plan.

    Inferred: no GPU shape appears on the pricing page or in the sizing docs.

    inferred “4 vCPU is the ceiling on every instance type.” Source

  • BoatNono GPU

    Note: No size has a graphics processor, at any price.

    docs-confirmed “No size has a GPU.” Source

  • boxdNono GPU

    Note: There is no graphics processor option.

    Inferred: no GPU shape, price or availability anywhere in the docs.

    inferred “This is the largest size a single machine may have” Source

  • Cloudflare SandboxNono GPU

    Note: There is no graphics processor option; the largest machine is 4 cores of CPU.

    Inferred: no GPU instance type or price in the docs.

    inferred “Maximum vCPU” Source

  • E2BNoCPU only

    Note: There is no graphics processor option in any plan, tool or template.

    docs-confirmed “E2B sandboxes are CPU-only, sized by vCPU and RAM only, with no GPU option in the SDKs, CLI, API, or a template definition.” Source

  • InstaBoxNono GPU

    Note: No graphics processor is offered on any plan.

    Inferred: no GPU appears in the plans, docs or API.

    inferred “4 vCPUs and 8 GiB of memory by default, the only size on the free plan.” Source

  • LizardNoCPUs only

    Note: Sandboxes run on processors only; there is no graphics option.

    docs-confirmed “Sandboxes run on CPUs only.” Source

  • RuntimeNono GPU

    Note: Runtime lists a GPU request as an example of something it cannot do.

    docs-confirmed “No GPU sandboxes, so our model evaluations cannot move” Source

  • SandboxerNono GPU

    Note: There are no graphics processors.

    docs-confirmed “You need GPUs. Sandboxer has none.” Source

  • SpritesNono GPU

    Note: Sprites are not a graphics environment; Fly sells graphics machines as a separate product.

    docs-confirmed “Sprites are not a GPU environment. Fly.io sells GPU Machines separately” Source

  • Vercel SandboxNono GPU

    Note: No graphics processor option is published for sandboxes.

    Inferred: no GPU appears in the pricing table or the size limits.

    inferred “Each vCPU includes 2 GB of memory.” Source

  • BlaxelNot published

    Custom hardware is advertised, but no GPU model or price is published.

    not-published “Custom hardware options” Source

  • MorphNot published

    No page states whether graphics processors are available.

    not-published “Full virtual machines capable of running any configuration of containers” Source

Related

Other capabilities in this feature

Where it decides the choice

The feature

Words used here

  • vCPUOne share of a processor. More vCPUs let a machine do more things at once; an agent waiting for messages uses a small fraction of one.
  • Memory (RAM)The machine's working space while it runs. Lost when the machine stops unless the provider saves it. A browser or a large program needs more of it.
  • RegionThe part of the world where the machine runs. It matters for speed if your users are far away, and for law if data must stay in a country or the EU.

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