Skip to main content

Release 2026.11.12

Sandboxes​

Sandboxes in private preview​

Serenity Edge Sandboxes, isolated microVMs for AI agents, are in private preview, by invitation: Linux machines that you create through an API, run commands in, pause, resume and kill. They are enabled on request for existing Serenity Edge customers and partners; once they are enabled, the Serenity Edge API key you use for inference works for sandboxes too. To ask for access, see Enterprise or write to [email protected]. See Sandboxes and the quickstart.

Compatible with the E2B SDKs​

The API is compatible with the E2B API and the official E2B SDKs (pip install e2b, npm install e2b), tested with version 2.63.0. Set E2B_DOMAIN to vlc1.serenitysandboxes.cloud and E2B_API_KEY to your Serenity Edge API key, and Sandbox.create() works with no other change. The preview runs in one site, in the European Union.

Prices​

A running sandbox is billed per second, with no minimum, for its reserved resources: 0.0504 USD per vCPU-hour and 0.0162 USD per GiB-hour of memory. CPU time may be shared under load, as on burstable instances. A paused sandbox is billed 0.08 USD per GiB-month actually stored. Billing started on 12 November 2026, and there are no welcome credits. See Pricing and usage.

The default template​

The preview has one public template, edge-agents, used by default, so Sandbox.create() needs no arguments (over HTTP, its templateID is base or edge-agents). It is Ubuntu 24.04 with tools for agents (Python 3.12 with uv and Jupyter kernels, Node.js 26 LTS, the .NET 10 SDK, compilers, git and the GitHub CLI, LibreOffice and document tools, and a headless Chromium with Playwright), with 2 vCPUs, 2 GiB of memory and about 26 GiB of disk, of which 20 GiB are free. See Templates.

Limits, network and lifetime​

Each account may run up to 48 sandboxes at once and create 60 per minute, and a sandbox runs for at most 24 hours; a paused sandbox keeps its files, memory and processes for up to 30 days. Commands, files and an interactive terminal go through the SDKs over HTTPS; there is no SSH access. A sandbox reaches public websites and APIs over HTTP and HTTPS (ports 80 and 443), through an egress proxy that the template sets up, and nothing else; private and internal addresses are refused. A sandbox created with allow_internet_access: false reaches nothing at all, and is billed the same. See Limits and quotas and Network access and security.

Not in the preview​

Desktops and computer use are coming soon. Template builds, public sandbox URLs, outbound network rules set by the client, sandbox logs, create fields outside the supported list, credentials added to outbound requests by Serenity Edge, a spending cap and reading usage records through the API are not available in the preview; each is refused with its own edge_ error code where a request can ask for it. When the site is full, a create or a resume gets 503 sandbox_capacity_unavailable: retry later. See Preview status and Errors.

Preview limitations​

Paused sandboxes are not backed up yet, so they can be lost if the site's storage fails: keep anything you need outside the sandbox. The preview has one site, and its limits and prices may change; changes will be announced here. Until the sandbox domain is on the Public Suffix List, do not rely on cookie isolation between sandbox host names (see Cookies and browsers). There is no service level, and the independent security testing of the service is not finished: do not put production secrets or personal data in a preview sandbox.

Known issues​

Writing a file with sandbox.files.write to a path under /tmp a second time fails with HTTP 500 ("permission denied"): write files under /home/user until the fix. Sandbox metrics are not available in the preview. See Known issues in the preview.


Documentation​

  • New section "Sandboxes (private preview)": overview, quickstart, API reference, errors, limits and quotas, pricing and usage, and network access and security.