{
  "data": {
    "a": {
      "slug": "docker-sandboxes",
      "name": "Docker Sandboxes",
      "vendor": "Docker",
      "vendorUrl": "https://www.docker.com",
      "company": "docker.com",
      "kind": "http-api",
      "category": "code-sandboxes",
      "summary": "Docker Sandboxes runs AI agents in microVM sandboxes, locally through the `sbx` CLI or on Docker-managed cloud compute through `sbx --cloud`, a REST API and a TypeScript SDK. Cloud sandboxes belong to the experimental Docker Agentic Platform.",
      "url": "https://www.anchorterminal.com/tools/docker-sandboxes",
      "markdownUrl": "https://www.anchorterminal.com/tools/docker-sandboxes.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/docker-sandboxes.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/docker-sandboxes.json",
      "dns": "docker-sandboxes.grade.anchorterminal.com",
      "repo": "https://github.com/docker/sbx-releases",
      "license": "Proprietary. 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",
      "transports": [
        "http"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@docker/sandboxes"
        }
      ],
      "auth": "mixed",
      "authNotes": "Cloud access needs a Docker account with an active Docker Agentic Platform pay-as-you-go subscription, bought through Docker Billing in a browser. Automation uses a Docker personal access token created with Allow Cloud Sandboxes access (the `sandbox:use` scope), which the SDK exchanges for short-lived access tokens. Interactive use signs in through a browser device flow. Each operation checks a named permission such as `sandboxesCreate` or `sandboxesDelete`.",
      "pricing": "usage",
      "pricingNotes": "Cloud compute is pay-as-you-go with no recurring fee, metered by the second on runtime and the chosen CPU and memory size, billed monthly. The docs publish no unit prices, which appear in the Agentic Platform console. Signup needs billing and payment details and gives a one-time promotional credit. The `sbx` CLI and local sandboxes are free, including for commercial work. Model inference is billed by the user's own provider.",
      "priceSummary": "Pay per use",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Sandboxes API's OpenAPI document, the sandbox and Agentic Platform docs or the billing pages in the docker/docs repository (checked 2026-11-18). Payment is a Docker Billing subscription.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 527,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://docs.docker.com/ai/sandboxes/",
      "llmsTxt": "https://docs.docker.com/llms.txt",
      "openapi": "https://github.com/docker/docs/blob/main/content/reference/api/sandboxes/api.yaml",
      "capabilities": [
        "sandbox.code",
        "sandbox.fs",
        "sandbox.persist"
      ],
      "tags": [
        "hosted",
        "usage",
        "beta",
        "microvm",
        "typescript",
        "cli",
        "openapi",
        "llms-txt",
        "docker"
      ],
      "lastRelease": "2026-11-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.1,
        "grade": "B",
        "agentReady": false,
        "rank": 698,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 17,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 83,
          "maintenance": 71,
          "payments": 0,
          "reliability": 45,
          "schema": 90,
          "security": 69,
          "transparency": 77
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "Running coding agents such as Claude Code or Codex in a disposable cloud VM, or the same kit locally for free.",
        "strengths": [
          "Public OpenAPI 3.2 contract with 58 described operations, and llms.txt and Markdown copies of the docs",
          "`Idempotency-Key` on creates, starts, stops and deletes, kept for at least 24 hours, and `If-Match` etags on updates",
          "Credentials are added to outbound requests outside the VM, so code in the sandbox never holds the raw key",
          "Errors carry stable codes and typed details, with a documented action for each code",
          "Three stable `sbx` releases between 3 and 16 November 2026, with dated release notes"
        ],
        "weaknesses": [
          "Docker Agentic Platform, needed for every cloud interface, is experimental, and no SLA was found",
          "No unit prices on docker.com or in the docs, and signup asks for payment details in a browser",
          "The SDK is TypeScript only, and the source of `sbx` and the SDK is not public",
          "Request rate limits are described without numbers",
          "Cloud sandboxes live at most 24 hours from creation, and snapshots are deleted after seven days of non-use"
        ],
        "agentNotes": [
          "Create the Docker personal access token with Allow Cloud Sandboxes access. Registry permissions alone don't grant the `sandbox:use` scope",
          "Send the same `Idempotency-Key` when you retry a create, so a lost response doesn't start a second sandbox",
          "Pass the etag from your latest read in `If-Match`. A stale etag returns 412 and a missing one 428",
          "Set `--ttl` and `--on-timeout` at creation. The default deletes sandboxes that can't be resumed after one hour",
          "Set the account network policy to deny-all and add allow rules per sandbox, since allow-all lets the sandbox reach any host"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.1
          }
        ],
        "editorialScores": {
          "ergonomics": 83,
          "maintenance": 71,
          "payments": 0,
          "reliability": 45,
          "schema": 90,
          "security": 69,
          "transparency": 57
        },
        "provenanceScore": 97,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "lastMoved": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npm install @docker/sandboxes  # or brew install docker/tap/sbx"
      },
      "letme": {
        "capability": "https://letme.dev/sandbox.code",
        "tool": "https://letme.dev/docker-sandboxes"
      },
      "sameCompany": [
        "docker-agent",
        "docker-model-runner"
      ],
      "area": "agent-runtime",
      "provenance": {
        "legalEntity": "Docker, Inc.",
        "domain": "docker.com",
        "domainRegistered": "1995-01-25",
        "endpointOnVendorDomain": true,
        "terms": "https://www.docker.com/legal/docker-subscription-service-agreement/",
        "privacy": "https://www.docker.com/legal/privacy/",
        "statusPage": "https://www.dockerstatus.com/",
        "changelog": "https://docs.docker.com/ai/sandboxes/release-notes/",
        "securityTxt": "valid",
        "checked": "2026-11-18",
        "notes": [
          "The Docker Subscription Service Agreement (last updated 26 August 2026), which Docker's Terms of Use say governs paid services, defines Agentic Platform Services and Sandbox, so it governs cloud sandboxes. The privacy policy at /legal/privacy/ says the Agentic Platform and cloud sandboxes are hosted in the United States.",
          "The API base URL https://connect.docker.com/sandboxes is a docker.com subdomain, per the OpenAPI document.",
          "docs.docker.com's robots.txt allows all agents with Content-Signal ai-train=yes, search=yes, ai-input=yes, and the published pages are served as Markdown. www.docker.com's robots.txt disallows only admin, thank-you, search and asset paths (read 18 November 2026).",
          "dockerstatus.com (incident.io) lists Docker Sandboxes under Cloud and AI Services and Docker Agentic Platform under Beta Products. Its incident history is drawn by a script and wasn't readable.",
          "docker/sbx-releases holds release binaries, a SECURITY.md sending reports to security@docker.com with acknowledgement within 72 hours, and an all-rights-reserved licence. The source of `sbx` and of `@docker/sandboxes` is not public. Legal entity, security.txt and domain date are carried from docker-agent (checked 1 November 2026)."
        ],
        "score": 97
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/docker-sandboxes.json",
      "live": {
        "slug": "docker-sandboxes",
        "vendorStatus": {
          "page": "https://www.dockerstatus.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T22:37:48.853198999Z"
        },
        "updatedAt": "2026-11-18T22:37:48.853198999Z"
      }
    },
    "answer": "Sprites scores 68 (B) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 3 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust.",
    "b": {
      "slug": "sprites",
      "name": "Sprites",
      "vendor": "Fly.io",
      "vendorUrl": "https://fly.io",
      "company": "fly.io",
      "kind": "http-api",
      "category": "code-sandboxes",
      "summary": "Sprites are hosted Linux microVMs from Fly.io that keep their disk between runs, pause when idle and wake on request. They are driven through a REST API, a CLI, four SDKs or a hosted MCP server.",
      "url": "https://www.anchorterminal.com/tools/sprites",
      "markdownUrl": "https://www.anchorterminal.com/tools/sprites.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sprites.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sprites.json",
      "dns": "sprites.grade.anchorterminal.com",
      "repo": "https://github.com/superfly/sprites-js",
      "license": "Proprietary service under the Fly.io Terms of Service. The JavaScript, Go, Python and Elixir SDKs are MIT",
      "transports": [
        "http"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@fly/sprites"
        },
        {
          "registry": "pypi",
          "name": "sprites-py"
        }
      ],
      "auth": "api-key",
      "authNotes": "A bearer token created at sprites.dev/account after signing in with a Fly.io account, sent as `Authorization: Bearer \u003ctoken\u003e` to `https://api.sprites.dev`. Tokens belong to an organisation, and no scopes or expiry were found in the reviewed docs. The CLI signs in through a browser with `sprite org auth` or takes a token with `sprite auth setup --token`. The hosted MCP server uses OAuth with a token restricted by default to a name prefix and a capped number of Sprites.",
      "pricing": "usage",
      "pricingNotes": "$0.0385 a CPU-hour and $0.021875 a GB-hour of memory while a Sprite is active, hot storage at $0.000683 a GB-hour while awake and cold storage at $0.000027 a GB-hour while data is kept. Nothing is charged per Sprite or for bandwidth. Every new user gets a $1 free trial with no credit card, invoices under $5 are waived, and new organisations get a $30 trial credit. The product page also describes monthly plans with allowances, of which Hero ($100) and Mythic ($2,000) are priced (https://fly.io/sprites/, https://fly.io/pricing/, checked 2026-11-04).",
      "priceSummary": "$0.0385 / vCPU-hr",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Sprites docs, the OpenAPI document or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 157565,
        "pypiWeekly": 58695,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://docs.fly.io/sprites",
      "llmsTxt": "https://docs.fly.io/llms.txt",
      "openapi": "https://docs.fly.io/sprites/api/openapi.json",
      "capabilities": [
        "sandbox.code",
        "sandbox.fs",
        "sandbox.persist"
      ],
      "tags": [
        "hosted",
        "usage-priced",
        "microvm",
        "persistent",
        "checkpoints",
        "openapi",
        "cli",
        "typescript",
        "python",
        "go",
        "elixir",
        "mcp",
        "llms-txt",
        "status-page"
      ],
      "lastRelease": "2026-10-20",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 68,
        "grade": "B",
        "agentReady": false,
        "rank": 411,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 68,
          "maintenance": 80,
          "payments": 60,
          "reliability": 80,
          "schema": 74,
          "security": 61,
          "transparency": 66
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": -2,
        "negativeNotes": [
          "2026-10-08, still on 2026-11-04: the Fly.io pricing page says of Sprites \"No plans and no tiers\", while the Sprites product page describes paid plans (Hero at $100 a month, Mythic at $2,000) that carry usage allowances and set concurrency and creation-rate limits, and links to the pricing page for \"every tier and what each includes\". Prices for the other named plans were not found. 2 points. https://fly.io/pricing.md and https://fly.io/sprites.md"
        ],
        "verdict": "A Sprite keeps a 100 GB ext4 disk between runs, bills compute only while active and can be checkpointed and restored through a published OpenAPI contract. The status page records five partial Sprites incidents since August, one lasting over seven hours, and outbound network access is unrestricted until a policy is set.",
        "bestFor": "Agents that need a long-lived machine with installed tools and files kept between sessions, and rollback by checkpoint.",
        "strengths": [
          "The filesystem persists across pauses, and compute billing stops about 30 seconds after activity ends, per the lifecycle docs",
          "A public OpenAPI 3.1 document covers 44 operations on sprites, exec, files, checkpoints, services and policies, with an AsyncAPI file for the WebSocket calls",
          "Connectors hold third-party credentials outside the Sprite, deny access by default and can limit which provider paths a Sprite may call",
          "Checkpoints are copy-on-write snapshots of the writable filesystem, and the last five are mounted read-only inside the Sprite",
          "Unit prices are public, $0.0385 a CPU-hour, $0.021875 a GB-hour of memory and about $0.50 a GB-month of hot storage",
          "Official SDKs for JavaScript, Go, Python and Elixir are MIT, with JavaScript and Go releases on 20 October 2026",
          "New users get a $1 trial with no credit card, and new organisations a $30 trial credit"
        ],
        "weaknesses": [
          "Five partial Sprites incidents on the status page since 30 August 2026, including 7 hours 28 minutes of intermittent API failures on 23 September and 75 minutes of unreachable Sprite URLs on 11 October",
          "Outbound network access is unrestricted by default. The DNS allowlist is opt-in and set from outside the Sprite",
          "The product page creates a Sprite with `PUT /v1/sprites/my-sprite` and a JSON `command` body, while the OpenAPI document creates with `POST /v1/sprites` and passes `cmd` as a query parameter",
          "No API changelog, deprecation policy or error-code reference was found in the reviewed documentation",
          "The pricing page says Sprites have no plans and no tiers, while the product page describes paid plans that set concurrency and creation-rate limits",
          "No scopes were found for API tokens created at sprites.dev/account. Only the MCP connector's OAuth token is restricted by default"
        ],
        "agentNotes": [
          "Create a token at sprites.dev/account after a browser signup, and send it as `Authorization: Bearer \u003ctoken\u003e` to `https://api.sprites.dev`",
          "Follow the OpenAPI document, not the product page example. Create with `POST /v1/sprites` and a JSON `name`, and run commands with `POST /v1/sprites/{name}/exec` using `cmd` query parameters",
          "Set a network policy with `POST /v1/sprites/{name}/policy/network` before running untrusted code. Egress is open until one is set",
          "Processes started by exec stop on a cold wake. Define a Service for anything that must answer the request that wakes the Sprite",
          "Create a checkpoint before a restore. Restoring replaces the filesystem, ends active sessions and keeps no copy of the replaced state",
          "Sprite creation is limited to 10 a minute on pay-as-you-go. The Go SDK reads `Retry-After` and the error code `sprite_creation_rate_limited` on a 429",
          "Delete Sprites you no longer need. An idle Sprite still bills cold storage for the bytes it holds",
          "Set `SPRITES_CLIENT_SIGNALS=0` before the first SDK call if your operator doesn't want client-signal headers sent"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 68
          }
        ],
        "editorialScores": {
          "ergonomics": 68,
          "maintenance": 80,
          "payments": 60,
          "reliability": 80,
          "schema": 74,
          "security": 61,
          "transparency": 54
        },
        "provenanceScore": 77,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "curl -fsSL https://sprites.dev/install.sh | sh  # CLI. SDKs: npm install @fly/sprites, pip install sprites-py",
        "http": "curl -X POST https://api.sprites.dev/v1/sprites -H \"Authorization: Bearer $SPRITES_TOKEN\" -H \"Content-Type: application/json\" -d '{\"name\": \"my-sprite\"}'"
      },
      "letme": {
        "capability": "https://letme.dev/sandbox.code",
        "tool": "https://letme.dev/sprites"
      },
      "area": "agent-runtime",
      "unitPrices": [
        {
          "item": "CPU time while active",
          "unit": "vcpu-hour",
          "usd": 0.0385,
          "note": "Memory extra at $0.021875 a GB-hour"
        },
        {
          "item": "Hot storage while the Sprite is awake",
          "unit": "gb-month",
          "usd": 0.5,
          "note": "Billed at $0.000683 a GB-hour, on bytes written"
        },
        {
          "item": "Cold storage while data is kept",
          "unit": "gb-month",
          "usd": 0.02,
          "note": "Billed at $0.000027 a GB-hour"
        }
      ],
      "provenance": {
        "legalEntity": "Fly.io, Inc.",
        "domain": "fly.io",
        "domainRegistered": "2004-07-15",
        "endpointOnVendorDomain": false,
        "terms": "https://fly.io/legal/terms-of-service/",
        "privacy": "https://fly.io/legal/privacy-policy/",
        "statusPage": "https://status.flyio.net",
        "changelog": "",
        "securityTxt": "valid",
        "checked": "2026-11-04",
        "notes": [
          "The Terms of Service (effective 29 April 2026) name Fly.io, Inc. and cover the website and all products and services reached through it. No separate Sprites terms were found.",
          "The Privacy Statement is effective 24 September 2026. The sub-processor list was last updated the same day.",
          "The API is at api.sprites.dev and Sprite URLs are on sprites.app, second domains of the vendor's. sprites.dev redirects to fly.io/sprites, and RDAP gives its registration date as 2025-06-03.",
          "RDAP for fly.io gives a registration date of 2004-07-15.",
          "No changelog for the Sprites API or environment was found. The Python SDK repository keeps a CHANGELOG.md.",
          "fly.io/.well-known/security.txt answered 200 on 2026-11-04 with Contact mailto:security@fly.io, Expires 2027-10-22 and Policy https://docs.fly.io/security; it returned 404 on 2026-10-08.",
          "The Terms of Service (effective 29 April 2026) and the Acceptable Use Policy, re-read on 2026-11-04, contain no ban on automated access to the website."
        ],
        "score": 77
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/sprites.json",
      "live": {
        "slug": "sprites",
        "vendorStatus": {
          "page": "https://status.flyio.net",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T22:38:53.726010779Z"
        },
        "versions": [
          {
            "registry": "npm",
            "name": "@fly/sprites",
            "version": "0.2.4",
            "seenAt": "2026-11-18T18:31:18.712722925Z"
          },
          {
            "registry": "pypi",
            "name": "sprites-py",
            "version": "0.7.2",
            "released": "2026-10-06",
            "seenAt": "2026-11-18T18:31:19.63988218Z"
          }
        ],
        "githubStars": 37,
        "npmWeekly": 159078,
        "pypiWeekly": 121011,
        "securityTxt": {
          "url": "https://fly.io/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-10-22T00:00:00.000Z",
          "checkedAt": "2026-11-18T16:29:08.873938323Z"
        },
        "llmsTxt": {
          "url": "https://docs.fly.io/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:16:15.366004357Z"
        },
        "domain": {
          "domain": "fly.io",
          "checkedAt": "2026-11-15T15:28:51.465433309Z"
        },
        "pages": [
          {
            "url": "https://fly.io/pricing/",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-18T21:43:58.957948545Z",
            "changedAt": "2026-11-18T21:43:58.957948545Z",
            "fingerprint": "d333a1c61946"
          },
          {
            "url": "https://fly.io/legal/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:43:54.84896574Z",
            "changedAt": "2026-10-30T05:40:20.286187728Z",
            "fingerprint": "393b851b214a"
          },
          {
            "url": "https://fly.io/legal/terms-of-service/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:43:56.956403369Z",
            "changedAt": "2026-10-30T05:40:22.599416434Z",
            "fingerprint": "6c040370ed70"
          }
        ],
        "github": {
          "repo": "superfly/sprites-js",
          "checkedAt": "2026-11-16T13:12:39.164339626Z",
          "stars": 37,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-02T15:27:49Z",
          "openIssues": 1,
          "openPRs": 0,
          "issuesOpened90d": 1,
          "issuesClosed90d": 1,
          "prsMerged90d": 28,
          "ci": {
            "branch": "main",
            "runs": 32,
            "success": 32,
            "failure": 0,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-11-02T15:28:14Z"
          },
          "replies": {
            "sampled": 9,
            "unanswered": 1,
            "medianDays": 154.7
          }
        },
        "updatedAt": "2026-11-18T22:38:53.726010779Z"
      }
    },
    "edges": [
      {
        "by": 60,
        "category": "payments",
        "leads": "sprites",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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 \u0026 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.",
          "b": "No x402, MPP or L402 (0). Unit prices are public without a login, $0.0385 a CPU-hour, $0.021875 a GB-hour of memory, $0.000683 a GB-hour of hot storage and $0.000027 a GB-hour of cold storage (20). The product page and the pricing page now say every new user gets a $1 free trial with no credit card, invoices under $5 are waived, and new organisations get a $30 trial credit (20; was 10). A person signs up with a Fly.io account in a browser and creates the token (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60."
        },
        "scores": {
          "a": 0,
          "b": 60
        }
      },
      {
        "by": 35,
        "category": "reliability",
        "leads": "sprites",
        "name": "Reliability",
        "reasons": {
          "a": "Hosted lines, for the cloud Sandboxes API. dockerstatus.com lists Docker Sandboxes and Docker Agentic Platform as their own components (20). Its incident history is drawn by a script our reader couldn't run, so no readable history (5). Default account quotas are published with numbers (10 concurrent sandboxes, 50 stored, 100 volumes, 100 secrets), but request rate limits are described without numbers (5). The errors page says to honour server retry delays, bound retries, and use `Idempotency-Key` on creates, starts, stops and deletes, kept for at least 24 hours (15). No SLA found in the docs (0). Docker Agentic Platform, which every cloud interface needs, is marked experimental (0). 20+5+5+15+0+0 = 45.",
          "b": "Hosted lines. status.flyio.net runs on incident.io with history and a Sprites component (20). Five Sprites incidents since 6 August, each partial in its own text, so minor under this run's reading. Deletion jobs failed for 47 minutes on 30 August, \"a subset of Sprites users\" had API errors for 1 hour 38 minutes on 2 September, intermittent API failures starting near SJC ran 7 hours 28 minutes on 23 September, creates failed in regions outside Europe for 28 minutes on 8 October, and \"some or all\" Sprite URLs on sprites.app were unavailable for about 75 minutes on 11 October after a certificate error (20; was 5, which isn't a checklist value). The product page gives creation limits of 10 a minute on pay-as-you-go and 60 to 240 on plans, and 100 running Sprites on the Hero plan. No general request limits were found in the docs (10). The docs and the OpenAPI document list no 429 response and no idempotency keys; the Go SDK reads `Retry-After` and `X-RateLimit` headers on a 429 and names a `sprite_creation_rate_limited` code, so Retry-After handling alone (10; was 7). Fly.io's published Service Level Agreement applies to the Services for customers on an Enterprise plan, with 99.9 per cent monthly availability and service credits of 10 to 30 per cent, and excludes no product, so it is read as covering Sprites (10; was 5, which isn't a checklist value). No beta or preview label was found on Sprites, so the surface is read as generally available, though the API document is version 0.1.12 and the SDKs are 0.x (10; was 8, which isn't a checklist value). 20 + 20 + 10 + 10 + 10 + 10 = 80."
        },
        "scores": {
          "a": 45,
          "b": 80
        }
      },
      {
        "by": 16,
        "category": "schema",
        "leads": "docker-sandboxes",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "A public OpenAPI 3.1 document with 44 operations and 59 schemas, plus an AsyncAPI file for the WebSocket calls (25). llms.txt and a Markdown copy of every docs page (10). Concept pages say when to use Services, Tasks and checkpoints and when not to, while operation descriptions are one line each (15). Request bodies have required fields and examples, but the document has 6 enums and no schema for error bodies (10). 116 examples in the OpenAPI document. Error responses are a status code and a short phrase, and the product page's create and exec examples disagree with the OpenAPI document (8). Paths are versioned under `/v1`. No API changelog was found, and only the Python SDK keeps a changelog file (6)."
        },
        "scores": {
          "a": 90,
          "b": 74
        }
      },
      {
        "by": 15,
        "category": "ergonomics",
        "leads": "docker-sandboxes",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "List calls take `max_results`, and service logs take `lines` and `duration`. Exec returns command output directly, with a WebSocket route for streaming (17). Sprite lists page with `continuation_token` and filter by `prefix` (16). Status codes are listed per operation and the SDKs raise typed errors with a machine code, but no code list is published (10). No idempotency keys. Service creation is a PUT by name and Sprite names are unique per organisation, and the hosted MCP server marks tools as read-only or destructive (10). Creating a Sprite needs only a name, and there are official SDKs in four languages and a CLI (15)."
        },
        "scores": {
          "a": 83,
          "b": 68
        }
      },
      {
        "by": 11,
        "category": "transparency",
        "leads": "docker-sandboxes",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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.",
          "b": "The SDKs are MIT and the platform is closed under terms of service effective 29 April 2026 (18). The privacy statement, effective 24 September 2026, keeps account data while the account is active and analytics data for at most 12 months. A pre-signed DPA is available on request. The terms grant Fly.io a licence to use customer data to run and improve the services. No retention period for Sprite data after deletion was found beyond the docs calling destruction permanent (18). No deprecation policy was found. The maintenance page says Sprites on Ubuntu 25.04 must upgrade, without a date (3). A sub-processor list of 34 vendors with countries and a dated change log, last updated 24 September 2026, names Tigris for Sprites object storage. The docs do not say which region a Sprite runs in (15). The four SDKs send coarse client-signal headers (interactive, CI or agent detection) by default; their READMEs disclose this and give the `SPRITES_CLIENT_SIGNALS=0` opt-out, so no deduction. 18 + 18 + 3 + 15 = 54."
        },
        "scores": {
          "a": 77,
          "b": 66
        }
      },
      {
        "by": 9,
        "category": "maintenance",
        "leads": "sprites",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "`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.",
          "b": "`@fly/sprites` v0.2.4 and `sprites-go` v0.2.2 on 20 October 2026, 15 days ago, each with a code fix (HTTP exec exit frames; directory stat and connection diagnostics) (30). Since 6 August, tags v0.2.1 to v0.2.4 of the JavaScript SDK, v0.5.1 to v0.7.2 of `sprites-py`, v0.1.1 to v0.2.2 of the Go SDK and v0.2.1 to v0.2.4 of the Elixir SDK, many more than three even at half (20). No product changelog was found. Support is the community forum below the Hero plan and email above it. Issue response on GitHub was not read (7). Current official SDKs for JavaScript, Go, Python and Elixir (15). All four SDK repositories run a checks workflow in CI and take dependency updates. The JavaScript SDK requires Node.js 24 or later (8). 30 + 20 + 7 + 15 + 8 = 80."
        },
        "scores": {
          "a": 71,
          "b": 80
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Docker",
        "b": "Fly.io",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary. 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",
        "b": "Proprietary service under the Fly.io Terms of Service. The JavaScript, Go, Python and Elixir SDKs are MIT",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-16",
        "b": "2026-10-20",
        "name": "Last release"
      },
      {
        "a": "2026-08-26",
        "b": "2026-04-29",
        "name": "Terms last updated"
      },
      {
        "a": "2026-08-26",
        "b": "2026-09-24",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "527 stars",
        "b": "158k npm/wk, 59k PyPI/wk",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Sprites scores 68 (B) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 3 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Docker Sandboxes or Sprites?"
      },
      {
        "answer": "Docker Sandboxes takes an API key or an OAuth sign-in. Sprites needs an API key.",
        "question": "Do Docker Sandboxes and Sprites need an API key?"
      },
      {
        "answer": "No hosted endpoint is listed for Docker Sandboxes. No hosted endpoint is listed for Sprites.",
        "question": "Can an agent call Docker Sandboxes and Sprites without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 90 against 74",
          "Agent ergonomics, 83 against 68",
          "Security \u0026 auth, 69 against 61",
          "Transparency \u0026 trust, 77 against 66"
        ],
        "also": null,
        "goodFor": "Running coding agents such as Claude Code or Codex in a disposable cloud VM, or the same kit locally for free.",
        "slug": "docker-sandboxes",
        "watchFor": "Docker Agentic Platform, needed for every cloud interface, is experimental, and no SLA was found"
      },
      {
        "aheadOn": [
          "Reliability, 80 against 45",
          "Payments \u0026 pricing, 60 against 0",
          "Maintenance \u0026 community, 80 against 71"
        ],
        "also": null,
        "goodFor": "Agents that need a long-lived machine with installed tools and files kept between sessions, and rollback by checkpoint.",
        "slug": "sprites",
        "watchFor": "Five partial Sprites incidents on the status page since 30 August 2026, including 7 hours 28 minutes of intermittent API failures on 23 September and 75 minutes of unreachable Sprite URLs on 11 October"
      }
    ],
    "history": {
      "docker-sandboxes": [
        {
          "causes": [
            "terms",
            "evidence"
          ],
          "date": "2026-11-18",
          "delta": 4.7,
          "from": 57.4,
          "fromGrade": "C",
          "to": 62.1,
          "toGrade": "B"
        }
      ],
      "sprites": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 65.5,
          "fromGrade": "B",
          "to": 68,
          "toGrade": "B"
        },
        {
          "causes": [
            "security",
            "evidence",
            "correction"
          ],
          "date": "2026-11-04",
          "delta": 6.9,
          "from": 58.6,
          "fromGrade": "C",
          "to": 65.5,
          "toGrade": "B"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-27",
          "delta": 0.3,
          "from": 58.3,
          "fromGrade": "C",
          "to": 58.6,
          "toGrade": "C"
        }
      ]
    },
    "job": {
      "capability": "sandbox.code",
      "name": "Code sandboxes"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-docker-sandboxes.json",
        "title": "Amazon Bedrock AgentCore Code Interpreter vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-sprites.json",
        "title": "Amazon Bedrock AgentCore Code Interpreter vs Sprites",
        "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-docker-sandboxes.json",
        "title": "Blaxel Sandboxes vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-sprites.json",
        "title": "Blaxel Sandboxes vs Sprites",
        "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/boat-vs-docker-sandboxes.json",
        "title": "boat vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/boat-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/boat-vs-sprites.json",
        "title": "boat vs Sprites",
        "url": "https://www.anchorterminal.com/compare/boat-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/celesto-vs-docker-sandboxes.json",
        "title": "Celesto (formerly SmolVM) vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/celesto-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/celesto-vs-sprites.json",
        "title": "Celesto (formerly SmolVM) vs Sprites",
        "url": "https://www.anchorterminal.com/compare/celesto-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-docker-sandboxes.json",
        "title": "Cloudflare Sandbox SDK vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-sprites.json",
        "title": "Cloudflare Sandbox SDK vs Sprites",
        "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/daytona-vs-docker-sandboxes.json",
        "title": "Daytona vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/daytona-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/daytona-vs-sprites.json",
        "title": "Daytona vs Sprites",
        "url": "https://www.anchorterminal.com/compare/daytona-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deno-sandbox-vs-docker-sandboxes.json",
        "title": "Deno Sandbox vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deno-sandbox-vs-sprites.json",
        "title": "Deno Sandbox vs Sprites",
        "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-docker-sandboxes.json",
        "title": "DigitalOcean Managed Agents vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sprites.json",
        "title": "DigitalOcean Managed Agents vs Sprites",
        "url": "https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-e2b.json",
        "title": "Docker Sandboxes vs E2B",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-e2b"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-freestyle.json",
        "title": "Docker Sandboxes vs Freestyle",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-freestyle"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-instavm.json",
        "title": "Docker Sandboxes vs InstaVM",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-instavm"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-maritime.json",
        "title": "Docker Sandboxes vs Maritime",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-maritime"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.json",
        "title": "Docker Sandboxes vs Microsoft Execution Containers",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-modal-sandboxes.json",
        "title": "Docker Sandboxes vs Modal Sandboxes",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-modal-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-morph-cloud.json",
        "title": "Docker Sandboxes vs Morph Cloud",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-morph-cloud"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-offscreen.json",
        "title": "Docker Sandboxes vs Offscreen",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-offscreen"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-perplexity-space.json",
        "title": "Docker Sandboxes vs SPACE",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-perplexity-space"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes.json",
        "title": "Docker Sandboxes vs Render Sandboxes",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-runloop.json",
        "title": "Docker Sandboxes vs Runloop Devboxes",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-runloop"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sandbox0.json",
        "title": "Docker Sandboxes vs Sandbox0",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sandbox0"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-together-code-sandbox.json",
        "title": "Docker Sandboxes vs Together Code Sandbox",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-together-code-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.json",
        "title": "Docker Sandboxes vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/e2b-vs-sprites.json",
        "title": "E2B vs Sprites",
        "url": "https://www.anchorterminal.com/compare/e2b-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/freestyle-vs-sprites.json",
        "title": "Freestyle vs Sprites",
        "url": "https://www.anchorterminal.com/compare/freestyle-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/instavm-vs-sprites.json",
        "title": "InstaVM vs Sprites",
        "url": "https://www.anchorterminal.com/compare/instavm-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/maritime-vs-sprites.json",
        "title": "Maritime vs Sprites",
        "url": "https://www.anchorterminal.com/compare/maritime-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites.json",
        "title": "Microsoft Execution Containers vs Sprites",
        "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/modal-sandboxes-vs-sprites.json",
        "title": "Modal Sandboxes vs Sprites",
        "url": "https://www.anchorterminal.com/compare/modal-sandboxes-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/morph-cloud-vs-sprites.json",
        "title": "Morph Cloud vs Sprites",
        "url": "https://www.anchorterminal.com/compare/morph-cloud-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/offscreen-vs-sprites.json",
        "title": "Offscreen vs Sprites",
        "url": "https://www.anchorterminal.com/compare/offscreen-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/perplexity-space-vs-sprites.json",
        "title": "SPACE vs Sprites",
        "url": "https://www.anchorterminal.com/compare/perplexity-space-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites.json",
        "title": "Render Sandboxes vs Sprites",
        "url": "https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/runloop-vs-sprites.json",
        "title": "Runloop Devboxes vs Sprites",
        "url": "https://www.anchorterminal.com/compare/runloop-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sandbox0-vs-sprites.json",
        "title": "Sandbox0 vs Sprites",
        "url": "https://www.anchorterminal.com/compare/sandbox0-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sprites-vs-together-code-sandbox.json",
        "title": "Sprites vs Together Code Sandbox",
        "url": "https://www.anchorterminal.com/compare/sprites-vs-together-code-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/sprites-vs-vercel-sandbox.json",
        "title": "Sprites vs Vercel Sandbox",
        "url": "https://www.anchorterminal.com/compare/sprites-vs-vercel-sandbox"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agent37-vs-docker-sandboxes.json",
        "title": "Agent 37 Cloud vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/agent37-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agent37-vs-sprites.json",
        "title": "Agent 37 Cloud vs Sprites",
        "url": "https://www.anchorterminal.com/compare/agent37-vs-sprites"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deltabox-lite-vs-docker-sandboxes.json",
        "title": "DeltaBox Lite vs Docker Sandboxes",
        "url": "https://www.anchorterminal.com/compare/deltabox-lite-vs-docker-sandboxes"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deltabox-lite-vs-sprites.json",
        "title": "DeltaBox Lite vs Sprites",
        "url": "https://www.anchorterminal.com/compare/deltabox-lite-vs-sprites"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 35,
        "docker-sandboxes": 45,
        "edge": "sprites",
        "key": "reliability",
        "name": "Reliability",
        "sprites": 80,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 16,
        "docker-sandboxes": 90,
        "edge": "docker-sandboxes",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "sprites": 74,
        "weight": 13
      },
      {
        "by": 15,
        "docker-sandboxes": 83,
        "edge": "docker-sandboxes",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "sprites": 68,
        "weight": 13
      },
      {
        "by": 8,
        "docker-sandboxes": 69,
        "edge": "docker-sandboxes",
        "key": "security",
        "name": "Security \u0026 auth",
        "sprites": 61,
        "weight": 14
      },
      {
        "by": 60,
        "docker-sandboxes": 0,
        "edge": "sprites",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "sprites": 60,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 9,
        "docker-sandboxes": 71,
        "edge": "sprites",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "sprites": 80,
        "weight": 7
      },
      {
        "by": 11,
        "docker-sandboxes": 77,
        "edge": "docker-sandboxes",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "sprites": 66,
        "weight": 7
      }
    ],
    "summary": "Sprites scores 68 (B) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 3 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust. Both do code sandboxes.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "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.",
      "sprites": "A Sprite keeps a 100 GB ext4 disk between runs, bills compute only while active and can be checkpointed and restored through a published OpenAPI contract. The status page records five partial Sprites incidents since August, one lasting over seven hours, and outbound network access is unrestricted until a policy is set."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites",
    "json": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites.min.md"
  },
  "markdown": "Sprites scores 68 (B) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 3 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust. Both do code sandboxes.\n\n- Docker Sandboxes: grade B, 62.1/100, rank #698 of 1557. Markdown https://www.anchorterminal.com/tools/docker-sandboxes.md · JSON https://www.anchorterminal.com/api/v1/tools/docker-sandboxes.json\n- Sprites: grade B, 68/100, rank #411 of 1557. Markdown https://www.anchorterminal.com/tools/sprites.md · JSON https://www.anchorterminal.com/api/v1/tools/sprites.json\n- Best code execution sandboxes for AI agents: https://www.anchorterminal.com/best/code-sandboxes/index.md\n- All 325 sandboxes comparisons: https://www.anchorterminal.com/compare/code-sandboxes/index.md\n\n## Which one, for what\n\n### Docker Sandboxes (B)\n\nGood for: Running coding agents such as Claude Code or Codex in a disposable cloud VM, or the same kit locally for free.\n\nAhead on:\n- Schema \u0026 documentation, 90 against 74\n- Agent ergonomics, 83 against 68\n- Security \u0026 auth, 69 against 61\n- Transparency \u0026 trust, 77 against 66\n\nWatch for: Docker Agentic Platform, needed for every cloud interface, is experimental, and no SLA was found\n\n### Sprites (B)\n\nGood for: Agents that need a long-lived machine with installed tools and files kept between sessions, and rollback by checkpoint.\n\nAhead on:\n- Reliability, 80 against 45\n- Payments \u0026 pricing, 60 against 0\n- Maintenance \u0026 community, 80 against 71\n\nWatch for: Five partial Sprites incidents on the status page since 30 August 2026, including 7 hours 28 minutes of intermittent API failures on 23 September and 75 minutes of unreachable Sprite URLs on 11 October\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Sprites +60\n\n- 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 \u0026 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.\n- Sprites (60): No x402, MPP or L402 (0). Unit prices are public without a login, $0.0385 a CPU-hour, $0.021875 a GB-hour of memory, $0.000683 a GB-hour of hot storage and $0.000027 a GB-hour of cold storage (20). The product page and the pricing page now say every new user gets a $1 free trial with no credit card, invoices under $5 are waived, and new organisations get a $30 trial credit (20; was 10). A person signs up with a Fly.io account in a browser and creates the token (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.\n\n### Reliability: Sprites +35\n\n- Docker Sandboxes (45): Hosted lines, for the cloud Sandboxes API. dockerstatus.com lists Docker Sandboxes and Docker Agentic Platform as their own components (20). Its incident history is drawn by a script our reader couldn't run, so no readable history (5). Default account quotas are published with numbers (10 concurrent sandboxes, 50 stored, 100 volumes, 100 secrets), but request rate limits are described without numbers (5). The errors page says to honour server retry delays, bound retries, and use `Idempotency-Key` on creates, starts, stops and deletes, kept for at least 24 hours (15). No SLA found in the docs (0). Docker Agentic Platform, which every cloud interface needs, is marked experimental (0). 20+5+5+15+0+0 = 45.\n- Sprites (80): Hosted lines. status.flyio.net runs on incident.io with history and a Sprites component (20). Five Sprites incidents since 6 August, each partial in its own text, so minor under this run's reading. Deletion jobs failed for 47 minutes on 30 August, \"a subset of Sprites users\" had API errors for 1 hour 38 minutes on 2 September, intermittent API failures starting near SJC ran 7 hours 28 minutes on 23 September, creates failed in regions outside Europe for 28 minutes on 8 October, and \"some or all\" Sprite URLs on sprites.app were unavailable for about 75 minutes on 11 October after a certificate error (20; was 5, which isn't a checklist value). The product page gives creation limits of 10 a minute on pay-as-you-go and 60 to 240 on plans, and 100 running Sprites on the Hero plan. No general request limits were found in the docs (10). The docs and the OpenAPI document list no 429 response and no idempotency keys; the Go SDK reads `Retry-After` and `X-RateLimit` headers on a 429 and names a `sprite_creation_rate_limited` code, so Retry-After handling alone (10; was 7). Fly.io's published Service Level Agreement applies to the Services for customers on an Enterprise plan, with 99.9 per cent monthly availability and service credits of 10 to 30 per cent, and excludes no product, so it is read as covering Sprites (10; was 5, which isn't a checklist value). No beta or preview label was found on Sprites, so the surface is read as generally available, though the API document is version 0.1.12 and the SDKs are 0.x (10; was 8, which isn't a checklist value). 20 + 20 + 10 + 10 + 10 + 10 = 80.\n\n### Schema \u0026 documentation: Docker Sandboxes +16\n\n- 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.\n- Sprites (74): A public OpenAPI 3.1 document with 44 operations and 59 schemas, plus an AsyncAPI file for the WebSocket calls (25). llms.txt and a Markdown copy of every docs page (10). Concept pages say when to use Services, Tasks and checkpoints and when not to, while operation descriptions are one line each (15). Request bodies have required fields and examples, but the document has 6 enums and no schema for error bodies (10). 116 examples in the OpenAPI document. Error responses are a status code and a short phrase, and the product page's create and exec examples disagree with the OpenAPI document (8). Paths are versioned under `/v1`. No API changelog was found, and only the Python SDK keeps a changelog file (6).\n\n### Agent ergonomics: Docker Sandboxes +15\n\n- 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.\n- Sprites (68): List calls take `max_results`, and service logs take `lines` and `duration`. Exec returns command output directly, with a WebSocket route for streaming (17). Sprite lists page with `continuation_token` and filter by `prefix` (16). Status codes are listed per operation and the SDKs raise typed errors with a machine code, but no code list is published (10). No idempotency keys. Service creation is a PUT by name and Sprite names are unique per organisation, and the hosted MCP server marks tools as read-only or destructive (10). Creating a Sprite needs only a name, and there are official SDKs in four languages and a CLI (15).\n\n### Transparency \u0026 trust: Docker Sandboxes +11\n\n- 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.\n- Sprites (66): The SDKs are MIT and the platform is closed under terms of service effective 29 April 2026 (18). The privacy statement, effective 24 September 2026, keeps account data while the account is active and analytics data for at most 12 months. A pre-signed DPA is available on request. The terms grant Fly.io a licence to use customer data to run and improve the services. No retention period for Sprite data after deletion was found beyond the docs calling destruction permanent (18). No deprecation policy was found. The maintenance page says Sprites on Ubuntu 25.04 must upgrade, without a date (3). A sub-processor list of 34 vendors with countries and a dated change log, last updated 24 September 2026, names Tigris for Sprites object storage. The docs do not say which region a Sprite runs in (15). The four SDKs send coarse client-signal headers (interactive, CI or agent detection) by default; their READMEs disclose this and give the `SPRITES_CLIENT_SIGNALS=0` opt-out, so no deduction. 18 + 18 + 3 + 15 = 54.\n\n### Maintenance \u0026 community: Sprites +9\n\n- 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.\n- Sprites (80): `@fly/sprites` v0.2.4 and `sprites-go` v0.2.2 on 20 October 2026, 15 days ago, each with a code fix (HTTP exec exit frames; directory stat and connection diagnostics) (30). Since 6 August, tags v0.2.1 to v0.2.4 of the JavaScript SDK, v0.5.1 to v0.7.2 of `sprites-py`, v0.1.1 to v0.2.2 of the Go SDK and v0.2.1 to v0.2.4 of the Elixir SDK, many more than three even at half (20). No product changelog was found. Support is the community forum below the Hero plan and email above it. Issue response on GitHub was not read (7). Current official SDKs for JavaScript, Go, Python and Elixir (15). All four SDK repositories run a checks workflow in CI and take dependency updates. The JavaScript SDK requires Node.js 24 or later (8). 30 + 20 + 7 + 15 + 8 = 80.\n\n## Score by category\n\n| Category | Weight | Docker Sandboxes | Sprites | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 45 | 80 | Sprites +35 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 90 | 74 | Docker Sandboxes +16 |\n| Agent ergonomics | 13% | 83 | 68 | Docker Sandboxes +15 |\n| Security \u0026 auth | 14% | 69 | 61 | Docker Sandboxes +8 |\n| Payments \u0026 pricing | 10% | 0 | 60 | Sprites +60 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 71 | 80 | Sprites +9 |\n| Transparency \u0026 trust | 7% | 77 | 66 | Docker Sandboxes +11 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **62.1 · B** | **68 · B** | |\n\n## Facts side by side\n\n| Fact | Docker Sandboxes | Sprites |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Docker | Fly.io |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary. 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 | Proprietary service under the Fly.io Terms of Service. The JavaScript, Go, Python and Elixir SDKs are MIT |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-11-16 | 2026-10-20 |\n| Terms last updated | 2026-08-26 | 2026-04-29 |\n| Privacy policy last updated | 2026-08-26 | 2026-09-24 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 527 stars | 158k npm/wk, 59k PyPI/wk |\n\n## How the scores have moved\n\n### Docker Sandboxes\n\n- +4.7 on 18 November 2026 (C to B): terms, new evidence\n\n### Sprites\n\n- +2.5 on 13 November 2026: checklist\n- +6.9 on 4 November 2026 (C to B): security, new evidence, correction\n- +0.3 on 27 October 2026: checklist\n\n## Verdicts\n\n**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.\n\n**Sprites.** A Sprite keeps a 100 GB ext4 disk between runs, bills compute only while active and can be checkpointed and restored through a published OpenAPI contract. The status page records five partial Sprites incidents since August, one lasting over seven hours, and outbound network access is unrestricted until a policy is set.\n\n## Before you call either\n\n### Docker Sandboxes\n\n1. Create the Docker personal access token with Allow Cloud Sandboxes access. Registry permissions alone don't grant the `sandbox:use` scope\n2. Send the same `Idempotency-Key` when you retry a create, so a lost response doesn't start a second sandbox\n3. Pass the etag from your latest read in `If-Match`. A stale etag returns 412 and a missing one 428\n4. Set `--ttl` and `--on-timeout` at creation. The default deletes sandboxes that can't be resumed after one hour\n5. Set the account network policy to deny-all and add allow rules per sandbox, since allow-all lets the sandbox reach any host\n\n### Sprites\n\n1. Create a token at sprites.dev/account after a browser signup, and send it as `Authorization: Bearer \u003ctoken\u003e` to `https://api.sprites.dev`\n2. Follow the OpenAPI document, not the product page example. Create with `POST /v1/sprites` and a JSON `name`, and run commands with `POST /v1/sprites/{name}/exec` using `cmd` query parameters\n3. Set a network policy with `POST /v1/sprites/{name}/policy/network` before running untrusted code. Egress is open until one is set\n4. Processes started by exec stop on a cold wake. Define a Service for anything that must answer the request that wakes the Sprite\n5. Create a checkpoint before a restore. Restoring replaces the filesystem, ends active sessions and keeps no copy of the replaced state\n6. Sprite creation is limited to 10 a minute on pay-as-you-go. The Go SDK reads `Retry-After` and the error code `sprite_creation_rate_limited` on a 429\n7. Delete Sprites you no longer need. An idle Sprite still bills cold storage for the bytes it holds\n8. Set `SPRITES_CLIENT_SIGNALS=0` before the first SDK call if your operator doesn't want client-signal headers sent\n\n## Questions\n\n### Which is better for AI agents, Docker Sandboxes or Sprites?\n\nSprites scores 68 (B) on agent readiness against Docker Sandboxes's 62.1 (B), and leads in 3 of 7 scored categories. Docker Sandboxes leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust.\n\n### Do Docker Sandboxes and Sprites need an API key?\n\nDocker Sandboxes takes an API key or an OAuth sign-in. Sprites needs an API key.\n\n### Can an agent call Docker Sandboxes and Sprites without installing anything?\n\nNo hosted endpoint is listed for Docker Sandboxes. No hosted endpoint is listed for Sprites.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites.json, and with the fewest tokens: https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"docker-sandboxes\", \"b\": \"sprites\"}`. From a terminal: `anchor compare docker-sandboxes sprites`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/docker-sandboxes.json and https://www.anchorterminal.com/api/v1/tools/sprites.json\n\n## Other comparisons with Docker Sandboxes or Sprites\n\n- [Amazon Bedrock AgentCore Code Interpreter vs Docker Sandboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-docker-sandboxes.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Sprites](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-sprites.md)\n- [Blaxel Sandboxes vs Docker Sandboxes](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-docker-sandboxes.md)\n- [Blaxel Sandboxes vs Sprites](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-sprites.md)\n- [boat vs Docker Sandboxes](https://www.anchorterminal.com/compare/boat-vs-docker-sandboxes.md)\n- [boat vs Sprites](https://www.anchorterminal.com/compare/boat-vs-sprites.md)\n- [Celesto (formerly SmolVM) vs Docker Sandboxes](https://www.anchorterminal.com/compare/celesto-vs-docker-sandboxes.md)\n- [Celesto (formerly SmolVM) vs Sprites](https://www.anchorterminal.com/compare/celesto-vs-sprites.md)\n- [Cloudflare Sandbox SDK vs Docker Sandboxes](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-docker-sandboxes.md)\n- [Cloudflare Sandbox SDK vs Sprites](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-sprites.md)\n- [Daytona vs Docker Sandboxes](https://www.anchorterminal.com/compare/daytona-vs-docker-sandboxes.md)\n- [Daytona vs Sprites](https://www.anchorterminal.com/compare/daytona-vs-sprites.md)\n- [Deno Sandbox vs Docker Sandboxes](https://www.anchorterminal.com/compare/deno-sandbox-vs-docker-sandboxes.md)\n- [Deno Sandbox vs Sprites](https://www.anchorterminal.com/compare/deno-sandbox-vs-sprites.md)\n- [DigitalOcean Managed Agents vs Docker Sandboxes](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-docker-sandboxes.md)\n- [DigitalOcean Managed Agents vs Sprites](https://www.anchorterminal.com/compare/digitalocean-managed-agents-vs-sprites.md)\n- [Docker Sandboxes vs E2B](https://www.anchorterminal.com/compare/docker-sandboxes-vs-e2b.md)\n- [Docker Sandboxes vs Freestyle](https://www.anchorterminal.com/compare/docker-sandboxes-vs-freestyle.md)\n- [Docker Sandboxes vs InstaVM](https://www.anchorterminal.com/compare/docker-sandboxes-vs-instavm.md)\n- [Docker Sandboxes vs Maritime](https://www.anchorterminal.com/compare/docker-sandboxes-vs-maritime.md)\n- [Docker Sandboxes vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/docker-sandboxes-vs-microsoft-execution-containers.md)\n- [Docker Sandboxes vs Modal Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-modal-sandboxes.md)\n- [Docker Sandboxes vs Morph Cloud](https://www.anchorterminal.com/compare/docker-sandboxes-vs-morph-cloud.md)\n- [Docker Sandboxes vs Offscreen](https://www.anchorterminal.com/compare/docker-sandboxes-vs-offscreen.md)\n- [Docker Sandboxes vs SPACE](https://www.anchorterminal.com/compare/docker-sandboxes-vs-perplexity-space.md)\n- [Docker Sandboxes vs Render Sandboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-render-sandboxes.md)\n- [Docker Sandboxes vs Runloop Devboxes](https://www.anchorterminal.com/compare/docker-sandboxes-vs-runloop.md)\n- [Docker Sandboxes vs Sandbox0](https://www.anchorterminal.com/compare/docker-sandboxes-vs-sandbox0.md)\n- [Docker Sandboxes vs Together Code Sandbox](https://www.anchorterminal.com/compare/docker-sandboxes-vs-together-code-sandbox.md)\n- [Docker Sandboxes vs Vercel Sandbox](https://www.anchorterminal.com/compare/docker-sandboxes-vs-vercel-sandbox.md)\n- [E2B vs Sprites](https://www.anchorterminal.com/compare/e2b-vs-sprites.md)\n- [Freestyle vs Sprites](https://www.anchorterminal.com/compare/freestyle-vs-sprites.md)\n- [InstaVM vs Sprites](https://www.anchorterminal.com/compare/instavm-vs-sprites.md)\n- [Maritime vs Sprites](https://www.anchorterminal.com/compare/maritime-vs-sprites.md)\n- [Microsoft Execution Containers vs Sprites](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites.md)\n- [Modal Sandboxes vs Sprites](https://www.anchorterminal.com/compare/modal-sandboxes-vs-sprites.md)\n- [Morph Cloud vs Sprites](https://www.anchorterminal.com/compare/morph-cloud-vs-sprites.md)\n- [Offscreen vs Sprites](https://www.anchorterminal.com/compare/offscreen-vs-sprites.md)\n- [SPACE vs Sprites](https://www.anchorterminal.com/compare/perplexity-space-vs-sprites.md)\n- [Render Sandboxes vs Sprites](https://www.anchorterminal.com/compare/render-sandboxes-vs-sprites.md)\n- [Runloop Devboxes vs Sprites](https://www.anchorterminal.com/compare/runloop-vs-sprites.md)\n- [Sandbox0 vs Sprites](https://www.anchorterminal.com/compare/sandbox0-vs-sprites.md)\n- [Sprites vs Together Code Sandbox](https://www.anchorterminal.com/compare/sprites-vs-together-code-sandbox.md)\n- [Sprites vs Vercel Sandbox](https://www.anchorterminal.com/compare/sprites-vs-vercel-sandbox.md)\n- [Agent 37 Cloud vs Docker Sandboxes](https://www.anchorterminal.com/compare/agent37-vs-docker-sandboxes.md)\n- [Agent 37 Cloud vs Sprites](https://www.anchorterminal.com/compare/agent37-vs-sprites.md)\n- [DeltaBox Lite vs Docker Sandboxes](https://www.anchorterminal.com/compare/deltabox-lite-vs-docker-sandboxes.md)\n- [DeltaBox Lite vs Sprites](https://www.anchorterminal.com/compare/deltabox-lite-vs-sprites.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Docker Sandboxes vs Sprites",
        "url": ""
      }
    ],
    "description": "Sprites scores 68 (B) to Docker Sandboxes's 62.1 (B) for code sandboxes. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Docker Sandboxes B 62.1",
      "Sprites B 68",
      "scores"
    ],
    "h1": "Docker Sandboxes vs Sprites",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/docker-sandboxes-vs-sprites",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Docker Sandboxes vs Sprites for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/docker-sandboxes-vs-sprites"
  },
  "tokens": {
    "markdown": 5850,
    "slim": 1030
  },
  "version": 1
}
