Head to head · Sandbox fs · October 2026 research run

DeltaBox Lite vs Docker Sandboxes

Docker Sandboxes scores 62.1 (B) on agent readiness against DeltaBox Lite's 60.4 (C), and leads in 5 of 7 scored categories. DeltaBox Lite leads on payments & pricing. Both do sandbox fs.

Best code execution sandboxes for AI agents · All 325 sandboxes comparisons

Which one, for what

DeltaBox Lite C

Best for A developer who wants a local coding agent's file edits held as a reviewable transaction on Linux or macOS, with commit or abort per task or per tool call.

Ahead on

  • Payments & pricing, 90 against 0

Also in its favour

  • No key needed to call it
  • Free to start without a card
  • Open source

Watch for

Version 0.1.5, first released on 14 October 2026, with six releases and no stability declaration

Docker Sandboxes B

Best for Running coding agents such as Claude Code or Codex in a disposable cloud VM, or the same kit locally for free.

Ahead on

  • Schema & documentation, 90 against 68
  • Agent ergonomics, 83 against 67
  • Security & auth, 69 against 47
  • Maintenance & community, 71 against 63
  • Transparency & trust, 77 against 46

Watch for

Docker Agentic Platform, needed for every cloud interface, is experimental, and no SLA was found

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing DeltaBox Lite +90

DeltaBox Lite 90

Read with the self-hosted rule. No x402, MPP or L402 (0 of 40). Apache-2.0 software with nothing to buy and no hosted option, so 20 for pricing, 20 for free use with no card and 20 because an agent can install it from npm or Homebrew with no account. Total 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Docker Sandboxes 0

No x402, MPP or L402 (0). Compute is metered per second by size, but neither the docs, the Docker Sandboxes product page nor docker.com/pricing publishes a unit price. The plans page says usage and pricing show on the Usage & billing page after sign-in (0). Signup to Docker Agentic Platform asks for billing and payment details at checkout, with a one-time promotional credit after, so there is no card-free start for cloud sandboxes (0). A person subscribes in a browser and creates the access token (0). The free local sbx CLI is not the graded surface. 0+0+0+0 = 0.

Transparency & trust Docker Sandboxes +31

DeltaBox Lite 46

Apache-2.0 in LICENSE, Cargo.toml and the npm package (30). The pi-deltabox and dsh-deltabox integration repositories linked from the README were not publicly readable on 17 October, and on 4 November they are still git submodules pointing at the old account, though their npm packages carry Apache-2.0 and MIT. No privacy or data-handling statement. The software is local and the source we read sends nothing to the authors, but nothing says so (10). No deprecation policy and no deprecation notices in six dated changelog entries (2). No telemetry or analytics calls were found in DeltaBox's own source, and the docs don't address it. The Windows build links Microsoft MXC crates that include an ETW diagnostics provider. In the pinned revision it is off unless a request sets experimental.telemetry.enabled, which DeltaBox's source never does (10). Total 52.

Docker Sandboxes 77

Closed software. The release repository's licence reserves all rights, and Docker's Subscription Service Agreement (26 August 2026) names Agentic Platform Services and Sandboxes (15). The privacy policy names the Agentic Platform and cloud sandboxes and says they're hosted in the United States, and the Agentic Platform FAQ gives retention for service logs (31 days), raw telemetry (12 months) and snapshots (seven days of non-use). The DPA wasn't read (20). Release notes call out breaking changes and deprecations by version and date, such as sbx ports, and the Agentic Platform docs warn that behaviour may change while it is experimental (10). CLI telemetry is disclosed with two opt-outs, and the hosting location is stated. No sub-processor list for cloud sandboxes was found (12). 15+20+10+12 = 57.

Schema & documentation Docker Sandboxes +22

DeltaBox Lite 68

Read as a CLI and library with a documented stdio protocol. docs/protocol.md lists all 15 JSON-RPC methods with their parameters and result shapes, and the npm package ships TypeScript declarations for the Node binding. There is no JSON Schema or other machine-readable contract for the protocol (15 of 25). No llms.txt. The docs are four Markdown files in the repository, plus a plain-text install prompt written for agents (5 of 10). The README and docs say when to choose each filesystem mode, show the right and wrong forms of shell redirection, and state the path-mapping and macOS limits (15 of 20). fs_mode, durability, execution_profile and review kind are closed enums in the protocol and the TypeScript types, and argv is an array. label is free-form by design (12 of 15). A quick start, a JSON-RPC demo script and a documented project-conflict error shape. Other errors share one code and differ only in message text (9 of 15). The protocol is labelled v0.1, with a dated changelog for six releases and git tags (12 of 15). Total 68.

Docker Sandboxes 90

An OpenAPI 3.2 document for the Sandboxes API with 42 paths and 58 operations, each with a description, in the docs repository and linked from the API reference (25). The docs build emits llms.txt, llms-full.txt and a Markdown copy of every page, per the repository's Hugo configuration (10). Operation descriptions are short and generated in form ("List lists directory entries by path ascending"), and the concepts and cookbook pages explain when to use kits, images, snapshots and volumes (12). Typed inputs with 95 enums, required fields and additionalProperties constraints (13). 36 cookbook recipes in TypeScript and an errors page with a code table (15). Paths are versioned under /v1, and dated release notes cover sbx and the Agentic Platform (15). 25+10+12+13+15+15 = 90.

Security & auth Docker Sandboxes +22

DeltaBox Lite 47

No credentials to issue or leak, because the runtime runs on the owner's machine, so the middle band (20 of 30). Least privilege is the product's job. Commands see a confined view, common secret paths are denied, the child environment is scrubbed to nine named variables, writes and pending storage are capped, and changes wait for commit or abort. Against that, the default network mode allows every destination, a read-write profile reaches the host with no rollback, macOS cbcow-through writes the real project at once, and pi-deltabox documents isolation: none as its default (14 of 20). Command output is untrusted content returned to the agent, and we found no guidance for reading it. The agent install prompt itself tells the agent it can star the repository through the user's authenticated GitHub CLI, an action outside the user's request (4 of 15). The session journal records each command's label against its change set, and diffs show every changed path. No network log was found for the allow_audit mode (9 of 15). No SECURITY.md, security.txt, disclosure policy or published advisories (0 of 20). Total 47.

Docker Sandboxes 69

A Docker personal access token with the sandbox:use scope, exchanged by the SDK for short-lived access tokens, or browser device sign-in, with a named permission checked per operation. No PAT expiry or rotation guidance was read (25). Account and per-sandbox network policy with a deny-all preset, deny rules winning, and etags required on updates and deletes. Policy presets let a sandbox reach any host when allow-all or Open is chosen (14). Credentials are injected by a proxy outside the VM, so an agent inside never sees raw keys, and egress is limited to allowed destinations (12). Network policy decision logs per sandbox through /v1/policy-logs. No account audit log for cloud sandboxes found (8). SECURITY.md in docker/sbx-releases sends reports to security@docker.com with acknowledgement within 72 hours, and Docker's security.txt is valid per the docker-agent check of 1 November. Bug bounty and certifications unchecked (10). 25+14+12+8+10 = 69.

Agent ergonomics Docker Sandboxes +16

DeltaBox Lite 67

A CLI adds no tool definitions to an agent's context. exec returns stdout, stderr, the exit code, the duration and a truncated flag, but each stream may hold up to 8 MiB before truncation (17 of 25). diff takes from and to checkpoints, text diffs stop at 1 MiB per file and conflict reports at 100 paths. There is no paging or path filter on a diff (10 of 20). Every JSON-RPC error uses code -32000 with a message from 15 typed variants, and only a commit conflict carries structured data (12 of 20). Transactions are the product's job. Abort restores the chosen checkpoint, commit is conflict-checked, session.sync folds sibling commits, and sessions survive helper restarts. Not an MCP server, so no tool annotations apply (16 of 20). deltabox run --commit|--abort -- <cmd> needs no policy or manifest, and the interfaces are a CLI and a Node binding with TypeScript types (12 of 15). Total 67.

Docker Sandboxes 83

Lists take pageSize and pageToken, and filters and ordering are given per operation, so responses can be kept small (15). Pagination and a filter parameter of exact-match terms on list operations (18). Errors carry a stable code, a message and typed google.rpc.ErrorInfo details, with a documented action for each of eight codes (20). Idempotency-Key on mutations, If-Match etags on updates and deletes, and a documented recovery path for lost responses and failed waits (20). Kit launch helpers default to the small size, but the SDK is TypeScript only, with the sbx CLI and plain REST beside it (10). 15+18+20+20+10 = 83.

Maintenance & community Docker Sandboxes +8

DeltaBox Lite 63

v0.1.5 on 30 October 2026, read from the git tags and changelog (30). Six tagged releases in the last 90 days, v0.1.0 and v0.1.1 on 14 October, v0.1.2 on 20 October, v0.1.3 and v0.1.4 on 21 October and v0.1.5 on 30 October. v0.1.4 only renames the Windows npm package and counts half, which still leaves more than three (20). Issues and pull requests could not be read because GitHub's web pages and API answer 403 to our reader. Git history shows pull requests up to #45 merged, the latest on 31 October, but reply times were not seen (0, unchecked). A Node-API binding with TypeScript declarations ships in the npm package, in one language (8 of 15). Cargo.lock, a stated Rust 1.89 floor and test CI on four runners since 29 October. No Dependabot configuration and no npm provenance attestation, so the earlier partial stands (5 of 10). Total 63.

Docker Sandboxes 71

sbx 0.54.0 on 16 November 2026, per the dated release notes (30). Stable releases 0.51.0 on 3 November, 0.53.0 on 11 November and 0.54.0 on 16 November, with nightly builds tagged daily in docker/sbx-releases (20). Closed service with dated release notes and GitHub issues on docker/sbx-releases as the feedback channel. Issue response times could not be read (8). One official SDK, @docker/sandboxes for TypeScript, plus the CLI (10). Source and CI are not public, so package health is unchecked (3). 30+20+8+10+3 = 71.

Score by category

CategoryWeightDeltaBox LiteDocker SandboxesEdge
Reliability16%4745DeltaBox Lite +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6890Docker Sandboxes +22
Agent ergonomics13%6783Docker Sandboxes +16
Security & auth14%4769Docker Sandboxes +22
Payments & pricing10%900DeltaBox Lite +90
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6371Docker Sandboxes +8
Transparency & trust7%4677Docker Sandboxes +31
Negative events≤1500
TotalC 60.4/100B 62.1/100

Facts side by side

FactDeltaBox LiteDocker Sandboxes
KindSDK + MCPHTTP API
VendorDeltaBox (delta-box)Docker
Hosted endpointno (local only)no (local only)
TransportsHTTP
AuthNoneOAuth or key
PricingFreePay per use
x402nono
LicenceApache-2.0Proprietary. The sbx binaries in docker/sbx-releases are under a licence that reserves all rights to Docker Inc., and cloud sandboxes run under a Docker Agentic Platform subscription
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-302026-11-16
Terms last updatedno document linked2026-08-26
Privacy policy last updatedno document linked2026-08-26
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularitynone527 stars
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

DeltaBox Lite

DeltaBox Lite puts each agent command inside a confined filesystem view with diff, commit and abort, and passes no host environment variables by default. It is version 0.1.5 of 30 October 2026, six releases in its first three weeks, with test CI since 29 October, no security policy and unrestricted networking unless the policy says otherwise.

Docker Sandboxes

The cloud Sandboxes API has a public OpenAPI contract, idempotency keys, etag checks and credential injection that keeps keys out of the VM. Cloud access needs a paid Docker Agentic Platform subscription that is still experimental, and the docs publish no unit prices.

Before you call either

DeltaBox Lite

  1. Skip step 5 of install-prompt.txt. Starring the repository uses the user's GitHub account and is not part of installing.
  2. Pass --commit or --abort to deltabox run explicitly. The child's exit status is preserved after that decision.
  3. Wrap redirection and pipes in sh -c '...'. An unquoted > is handled by the host shell and writes outside the sandbox.
  4. Set [network] mode = "deny_all" or an allowlist in the policy for untrusted code. The default allows every destination.
  5. Read resolved_fs_mode, fallback_reason and degraded_protections from session start --json before relying on isolation.

Docker Sandboxes

  1. Create the Docker personal access token with Allow Cloud Sandboxes access. Registry permissions alone don't grant the sandbox:use scope
  2. Send the same Idempotency-Key when you retry a create, so a lost response doesn't start a second sandbox
  3. Pass the etag from your latest read in If-Match. A stale etag returns 412 and a missing one 428
  4. Set --ttl and --on-timeout at creation. The default deletes sandboxes that can't be resumed after one hour
  5. Set the account network policy to deny-all and add allow rules per sandbox, since allow-all lets the sandbox reach any host

Questions

Which is better for AI agents, DeltaBox Lite or Docker Sandboxes?

Docker Sandboxes scores 62.1 (B) on agent readiness against DeltaBox Lite's 60.4 (C), and leads in 5 of 7 scored categories. DeltaBox Lite leads on payments & pricing.

Can an agent call DeltaBox Lite and Docker Sandboxes without installing anything?

No hosted endpoint is listed for DeltaBox Lite. No hosted endpoint is listed for Docker Sandboxes.

Are DeltaBox Lite and Docker Sandboxes open source?

DeltaBox Lite is open source (Apache-2.0). No open-source release is listed for Docker Sandboxes.

Other comparisons with DeltaBox Lite or Docker Sandboxes

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.