Sandboxes

A sandbox is a long-running container inside a project, useful for development shells, one-off jobs and small internal services. Create one from Sandboxes → Create Sandbox.

Base toolchain

Every sandbox is provisioned with a usable toolchain so it works the moment it starts:

apt-get update && apt-get install -y \
  nano curl git wget unzip ca-certificates gnupg \
  procps iputils-ping build-essential

Alpine images get the equivalent apk packages. Install failures are swallowed so a flaky mirror cannot wedge the container; you can always install more later.

Web terminal

Each sandbox hosts a browser terminal and, for supported images, a VS Code server. Open it from the sandbox list — the connection is authenticated with the same session as the console.

Lifecycle

Sandboxes can be stopped and restarted without losing their volume. Restarting re-runs the provisioning step, so a toolchain change made since the last start takes effect on the next start, not on a running container.

Resources

CPU, memory and storage are set at creation. A sandbox is a container, not a virtual machine: treat it as ephemeral compute with a persistent volume.