Sandbox

Trang này chưa được dịch sang Tiếng Việt: đây là bản tiếng Anh.

A sandbox is a virtual machine of its own: a Firecracker microVM that runs an OCI image, the kind docker builds and registries serve. You make one with an API call. Then you run commands in it, read and write its files, open a terminal or a link to one of its ports. Commands and files reach it through an agent inside the machine, not through its network.

When nothing happens in it, a sandbox sleeps. It keeps its memory, its processes and its disk, and the next call wakes it where it was, in milliseconds. It stays until you delete it.

When to use Sandbox

• An AI agent’s computer: a coding agent, a browser agent or a code interpreter that runs commands, installs packages and keeps its work between turns.
• Code you did not write: what users or models send you, kept away from your own machines and from each other, with network rules and secrets the code never sees.
• A job per request: glac run makes a sandbox, runs one command and deletes it.
• Environments that branch: a snapshot of a running sandbox, and copies (forks) that each go on from that moment.
• A server of its own: with init: "systemd" the image’s own systemd is its PID 1, for packages, services, cron and SSH as on any server (a whole system).

To serve an image at an address, with instances that start for requests, use Cube. Both run on the same machines, at the same prices.

How it works

1. Make. POST /v1/sandboxes (glac sandboxes create) with an image, or with none for the platform’s default image. The first sandbox of an image waits while the platform pulls it and saves a template. Later ones are copies of that template, from a pool that is already running.
2. Use. Run commands (exec), read and write files, open a terminal, give out links to ports. Calls wait for a sandbox that is starting or asleep: none fails for that.
3. Sleep. After sleep_after_seconds idle (30 unless you say), it sleeps. Whatever needs it wakes it: a command, a file, a request on a link, a timer.

What it costs

A sandbox pays for the CPU it uses and the memory it holds while it is awake. Asleep, it pays for what it keeps: its memory and the part of its disk that is its own. One held paused in the machine’s memory pays for that memory as if awake, and no CPU.

On Free, what an instance uses comes out of the day’s quotas; Paid includes a quantity of each meter every month, and past it usage is paid from the balance at these prices. See pricing and plans.

Limits of each plan

The sandboxes awake, their vCPUs and their memory are counted for the whole account: sandboxes and Cubes’ instances of every project together. Every limit is on the limits page.

Next

• Quickstart: make a sandbox, run a command, copy files, open a port, with the command line, Python or the console.
• Commands, files and terminals: running commands, their output, files, terminals, images.
• Sleep and wake: what puts a sandbox to sleep, what wakes it, keeping it awake from inside.
• Snapshots and forks: saving a sandbox as it is, going back, copies that go on, templates.
• Links, tokens and SSH: links to ports, tokens for one sandbox, SSH.
• Network rules and secrets: what a sandbox may reach, and secrets it uses without holding them.