Skip to content

Sandbox

A machine of its own for each AI agent, user or job, made from any OCI image in milliseconds. Run commands, read and write files, open a terminal; it sleeps when idle and wakes with its processes running.

업데이트

이 페이지는 아직 한국어로 번역되지 않아 영어로 보여 드립니다.

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.

과금 항목 가격 무료(하루 할당량) 유료(월 포함 사용량)
CPU(연산하는 동안) 100만 CPU-밀리초당 $0.01 100만 CPU-밀리초 6000만 CPU-밀리초
메모리(깨어 있거나 메모리에 일시 정지된 동안) GiB-시간당 $0.008 6 GiB-시간 250 GiB-시간
요청(큐브로, 그리고 샌드박스 링크를 거쳐 들어오는 요청) 100만 건당 $0.30 100,000 1000만
잠든 인스턴스가 보관하는 데이터(메모리와 고유 디스크) GB-월당 $0.02 스냅샷과 드라이브를 포함해 데이터 합계 15 GB 스냅샷과 드라이브를 포함해 데이터 20 GB-월
스냅샷이 보관하는 데이터 GB-월당 $0.02 위 데이터와 합산 위 데이터와 합산
북미에서 인터넷으로 나가는 트래픽 GB당 $0.004 리전 구분 없이 3 GB 리전 구분 없이 1 TB
유럽에서 인터넷으로 나가는 트래픽 GB당 $0.004
아시아 태평양에서 인터넷으로 나가는 트래픽 GB당 $0.01

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

무료 유료
최대 인스턴스 크기 2 vCPU, 4 GiB 8 vCPU, 16 GiB
동시에 깨어 있는 인스턴스 수 5 500
깨어 있는 인스턴스의 vCPU 합계 10 500
깨어 있는 인스턴스의 메모리 합계 10 GiB 1,000 GiB
보관하는 잠든 인스턴스 수 20 10,000
1분에 만들 수 있는 샌드박스 수 10 600
프로젝트 하나가 1시간에 만들 수 있는 샌드박스 수 200 10,000

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

탐색 메뉴

검색어를 입력하세요…

↑↓ 이동↵ 선택Esc 닫기