Sandbox Kit

Examples

Run one project for one operation. Each project loads its own environment file.

Each project selects one provider, loads a .env file, and performs one operation. Open the project for the call you need.

Creation projects provision a real sandbox. Filesystem and lifecycle projects use the sandbox id in .env. Stop, terminate, archive, delete, and remove can destroy that sandbox or the path you set. Error projects fail locally and create nothing.

The tables below are the common projects. The repository also has network, labels, secrets, pause, archive, and a project for each filesystem call (read, write, copy, mkdir, list, stat, remove). The full list is the examples catalog.

Daytona

OperationTypeScriptGo
Createprojectproject
Read a fileprojectproject
From an imageprojectproject
From a snapshotprojectproject
Lifetime policiesprojectproject
Look upprojectproject
Stopprojectproject
Deleteprojectproject
Errorsprojectproject
OperationTypeScriptGo
Createprojectproject
Read a fileprojectproject
Resourcesprojectproject
Attachprojectproject
Terminateprojectproject
Errorsprojectproject

Run a project

TypeScript needs Node.js 20, 22, or 24.15+. Go needs Go 1.26.0 or later. <area> is filesystem, configuration, lifecycle, or errors. Replace the path with the project you opened above. Skip cp .env.example when you already have a .env.

git clone https://github.com/sandbox-kit/kit.git
cd kit/examples/typescript/<provider>/<area>/<project>
cp .env.example .env
npm install && npm run build && npm start

Put the variables from that project's .env.example into .env. Daytona create uses DAYTONA_API_KEY. Modal create uses MODAL_TOKEN_ID, MODAL_TOKEN_SECRET, and MODAL_APP_NAME.

On this page