Deno Sandbox
deno.com
- Free plan
- Web
- API
What Deno Sandbox is
Deno Sandbox is an SDK for creating and managing isolated Linux microVMs in the cloud on Deno Deploy. It is intended for workloads such as AI agents, copilots, plugin systems, collaborative IDEs, ephemeral CI runners, smoke tests, user-provided code, and preview environments. Each sandbox has its own filesystem, network stack, and process tree, separated at the hypervisor level. Outbound networking is open by default, with an option to limit connections to approved hosts; secrets are substituted only for outbound requests to those hosts. Files disappear with the sandbox unless a volume is mounted, and the VM disk is wiped when the sandbox is killed or its last reference is dropped. A sandbox supports up to 2 vCPU, 10 GB of ephemeral disk, configurable memory from 768 MB to 4096 MB, and a 30-minute maximum lifetime. The SDK supports Deno latest stable, Node.js 24+, and Python 3.10 or later; JavaScript and Python packages and a REST API are available. Plans include Free at no cost, without Sandbox, and Pro at $20 /month with Sandbox included.
Who it suits
It suits developers building isolated execution environments for AI agents, user-supplied code, CI runners, or preview environments. Teams can use the JavaScript or Python SDKs, or connect through the REST API.
Good to know, and what to watch
- Hypervisor-level isolation gives each sandbox separate system resources.
- Allowlisting can restrict otherwise unrestricted outbound networking.
- Secrets are substituted only for approved outbound requests.
- HTTP, SSH, and on-demand VS Code access are available.
- Commands, requests, and SSH sessions can be traced in the dashboard.
- Each sandbox lasts no more than 30 minutes.
- Files are ephemeral unless a volume is mounted.
- The default prerelease limit is five concurrent sandboxes per organization.
- The Free plan does not include Sandbox.
Plans
Every plan and priceEnterprise
Free
Deno Sandbox usage
Pro
Free plan
Getting started
- Choose the Deno, Node.js or Python SDK, or use the REST API
- Install the JavaScript package from npm or JSR, or the Python package from PyPI
- Create a sandbox in Deno Deploy
- Configure memory, networking and any mounted volume
- Expose a development server, SSH session or VS Code editor as needed
- Trace commands and sessions in the Deno Deploy dashboard
Limits to check
The Free plan includes 1M requests per month and 10 hours of active CPU but no Sandbox. Pro includes Sandbox with three concurrent sandboxes per region and 5 GiB volume storage; each sandbox is limited to 30 minutes, 2 vCPU, 10 GB ephemeral disk and up to 4096 MB memory.
The Club's review
Deno Sandbox is a cloud SDK for running secure, disposable Linux microVMs on Deno Deploy. It is aimed at teams executing untrusted code, AI agents, tests, previews and other short-lived workloads. The isolation and credential controls are stronger than ordinary process-level sandboxes, while the short lifetime and concurrency ceilings make capacity planning important.
Overview
Each sandbox has its own filesystem, network stack and process tree, with isolation enforced at the hypervisor level. That is a substantial boundary for user-supplied code, plugin systems, copilots and collaborative development tools, rather than a general-purpose application host. Deno also positions it for ephemeral CI runners and smoke tests, where automatic disposal is useful.
The SDK is supported on Deno’s latest stable release, Node.js 24 and later, and Python 3.10 or later. JavaScript packages are distributed through npm and JSR, the Python SDK through PyPI, and a REST API provides direct access. The service is available through an API and web interface, with edge deployment.
Key features
Outbound network access is unrestricted initially, but an allowlist can confine connections to named hosts. That flexibility helps agents and test jobs reach external services, although teams wanting a default-deny posture must configure the allowlist themselves. Secrets remain placeholders inside the VM and are substituted only when making outbound requests to approved hosts, reducing the chance that running code can read credentials directly.
Storage is intentionally temporary: files vanish with the sandbox unless a volume is mounted, and the VM’s disk is wiped when its last reference is dropped or the VM is killed. This is well suited to clean-room jobs, but persistent projects need volume storage. Per-sandbox limits are 2 vCPU, 10 GB of ephemeral disk and configurable memory from 768 MB to 4096 MB. A sandbox can run for no more than 30 minutes. Documentation gives a default prerelease limit of five concurrent sandboxes per organization, with higher capacity handled by contacting Deno.
For development, a sandbox can expose an HTTP server, provide SSH and start an on-demand VS Code editor. The Deno Deploy dashboard traces commands, HTTP requests and SSH sessions. Amsterdam and Chicago are the supported regions. Deno Deploy is SOC2 and ISO27001 certified, and enterprise contracts can include HIPAA BAAs.
Pricing
The Free plan costs $0/month and includes 1 million requests per month and 10 hours of active CPU, but excludes Sandbox entirely. It is suitable for evaluating Deno Deploy’s surrounding platform, not for running microVMs.
Sandbox usage is billed at $0.20 per GiB-month, covering CPU time, memory and persistent-volume usage. Pro costs $20/month and includes Sandbox, three concurrent sandboxes per region and 5 GiB of volume storage. It fits a small production team with modest parallelism. Builder costs $200/month and raises capacity to 20 concurrent sandboxes per region with 50 GiB of volume storage, a more credible baseline for busy development or automation workloads. Enterprise uses custom pricing and offers custom sandbox concurrency and volume storage; it is the appropriate route for larger or compliance-sensitive deployments. Community support is included on every listed plan; Pro and Builder add email support, while Enterprise adds an email-support SLA.
Platforms
Use the API or web interface from JavaScript, TypeScript, Deno, Node.js or Python environments. Deployment targets the edge, with two listed edge locations, 200 GB/month bandwidth, request processing, response streaming, cron triggers and GitHub, dashboard or CLI deployment methods.
Who it's for
Deno Sandbox is a strong choice for teams that must run code they do not fully trust and need each execution discarded cleanly. It also suits AI-agent backends, preview environments, isolated CI tasks and interactive debugging that benefit from SSH or VS Code access. It is a weaker fit for long-running services, workloads needing more than 30 minutes per VM, or organizations that need substantial parallelism without negotiating a higher limit.
Pros and cons
Pros
- Hypervisor-level isolation: separate filesystems, networks and process trees provide a meaningful boundary for untrusted execution.
- Useful credential controls: host allowlists and outbound-only secret substitution limit how code can use sensitive services.
- Automatic cleanup: killed or dereferenced VMs and their disks are wiped, reducing leftover state.
- Developer access: HTTP exposure, SSH, VS Code and dashboard tracing support both automation and investigation.
Cons
- Paid-only Sandbox access: the $0 plan cannot run microVMs.
- Short execution window: each sandbox lasts at most 30 minutes.
- Concurrency constraints: the documented default is five per organization, while paid plan allowances are three or 20 per region.
- Open networking by default: teams requiring deny-by-default egress must apply an allowlist.
Alternatives
JSPM is a free, open-source package-management and CDN option when the requirement is importing JavaScript packages rather than isolated execution.
npm is the better fit for public package publishing and registry access, with a free plan for public package authors.
Pantry suits teams seeking package hosting with public packages, analytics and artifact storage.
Bun is a free, MIT-licensed JavaScript runtime and toolkit instead of a cloud microVM service.
vlt is a package-management service with a free tier and an $8/month Pro plan, rather than an isolated runtime.
Textadept is a free, open-source text editor for desktop platforms.
Yarn is a free open-source package manager without stated paid plans or usage limits.
Bower is a free command-line utility for package management.
Verdict
Choose Deno Sandbox when secure, disposable Linux environments are central to your product and you can work within its 30-minute lifetime and regional concurrency limits. Its strongest reason to buy is the combination of hypervisor isolation, controlled egress and secret handling. Look elsewhere for free Sandbox access, persistent long-running workloads or substantially higher parallel execution without a custom arrangement.
The verdict
Deno Sandbox provides isolated Linux microVMs with controls for network access, secrets, and cleanup. Check its time and concurrency limits, and note that the Free plan excludes Sandbox; Pro is $20 /month.
Questions people ask
What does Deno Sandbox cost?
The Free plan is free without Sandbox. Pro is $20 a month, Builder is $200 a month, and Enterprise is custom. Sandbox usage is listed at $0.20 per GiB-month for CPU time, memory and persistent volume usage.
Which runtimes are supported?
The SDK supports Deno latest stable, Node.js 24+ and Python 3.10 or later. JavaScript packages are available on npm and JSR, Python on PyPI, and a REST API is provided.
How isolated is each sandbox?
Each sandbox is a Linux microVM isolated at the hypervisor level with its own filesystem, network stack and process tree.
Can outbound connections be restricted?
Yes. Outbound networking is unrestricted by default, but an allowlist can limit connections to specified hosts.
Which regions are available?
The listed Sandbox regions are Amsterdam and Chicago.
What happens to sandbox files?
Files are ephemeral unless a volume is mounted. When the VM is killed or its last reference is dropped, the VM is destroyed and its disk wiped.
What the maker publishes
- Compliance
- The Sandbox FAQ says Deno Deploy is SOC2 and ISO27001 certified and says HIPAA BAAs are available for enterprise contracts. source
- Concurrency limit
- The docs state a default prerelease limit of 5 concurrent sandboxes per organization and invite users to contact Deno for a higher limit. source
- Connectivity and development
- Sandboxes can expose a dev server over HTTP, provide SSH access, and expose an on-demand VS Code editor. source
- Headquarters
- San Diego, California, USA source
- Headquarters
- San Diego, California, USA source
- Isolation
- Each sandbox is a Linux microVM isolated at the hypervisor level with its own filesystem, network stack, and process tree. source
- Observability
- Commands, HTTP requests, and SSH sessions can be traced in the Deno Deploy dashboard. source
- Outbound access
- Outbound networking is unrestricted by default, and an allowlist can restrict connections to specified hosts. source
- Packages and API
- The JavaScript SDK is available on npm and JSR, the Python SDK is on PyPI, and direct API access is available through a REST API. source
- Regions
- The docs list Amsterdam and Chicago as supported sandbox regions. source
- Resource limits
- The documented limits include 2 vCPU, 10 GB ephemeral disk, configurable 768 MB to 4096 MB memory, and a maximum 30-minute lifetime per sandbox. source
- Runtime support
- The SDK is tested and supported on Deno latest stable, Node.js 24+, and Python 3.10 or later. source
- Secret handling
- Secrets remain placeholders inside the sandbox and are substituted only for outbound requests to approved hosts. source
- Storage cleanup
- Sandbox files are ephemeral unless a volume is mounted, and the VM is destroyed and its disk wiped when its last reference is dropped or it is killed. source
- Support
- The pricing page includes community support on every listed plan, email support on Pro, Builder, and Enterprise, and an email support SLA on Enterprise. source
- Target workloads
- Deno identifies AI agents, copilots, plugin systems, collaborative IDEs, ephemeral CI runners, smoke tests, user supplied code, and preview environments as use cases. source
- What it is
- Deno Sandbox is an SDK for creating and managing secure, isolated Linux microVMs in the cloud on Deno Deploy. source
Checked against the maker's pages on 30 Sept 2026.