Overview

Secure, disposable environments for safely running code from the console — for testing a script, exploring a dataset, or trying out AI-generated code without touching your own machine.

A Sandbox is a secure, disposable environment you create and use entirely from the console — an isolated Firecracker microVM where you can run code, automate a browser, and persist state, without touching your own machine or your production projects.

Why a sandbox

Sometimes you want to run a script or try out a snippet — including code an AI assistant just generated for you — without worrying about what it touches. A sandbox gives you a real, working environment (a filesystem, an interpreter, a terminal) that is completely isolated and disappears the moment you're done with it. Create one, use it, and either snapshot it for later or let it go — nothing it does affects anything else in your account.

Sandboxes are reclaimed automatically after a period of inactivity, so a forgotten sandbox never sits around running — or costing you anything — forever.

Common uses

• Trying out AI-generated code — paste in a script an AI assistant wrote and run it somewhere disposable before you copy it into a real project or your own machine.
• Running untrusted code — a package you haven't vetted, a snippet from a forum post, anything you want to execute without giving it access to your production apps or data.
• A scratch environment for a quick task — a one-off data-processing job, a small script to reshape a CSV, or testing a library before deciding to depend on it — spin one up, do the work, and let it disappear.

How it fits together

Every sandbox starts from a template — ready-made ones like Python and Node are built in, or pick one of your own from the template gallery. From there you run code in the console's built-in editor, manage the sandbox's files in a file browser, and take a snapshot whenever you want to freeze its state and pick up again later.

Quickstart

1. 1
   Create a sandbox

   From the Sandboxes page, click New Sandbox, pick a template, and give it a name.
2. 2
   Run some code

   Open the sandbox's in-console editor, type or paste code, and click Run to see the output.
3. 3
   Wrap up

   Take a snapshot if you want to keep the state, or just close it out — an inactive sandbox is reclaimed automatically.

Explore