Head to head · Code sandboxes · October 2026 research run

DigitalOcean Managed Agents vs Together Code Sandbox

DigitalOcean Managed Agents scores 72.1 (BB) on agent readiness against Together Code Sandbox's 56 (C), and leads in 5 of 7 scored categories. Both do code sandboxes.

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

Which one, for what

DigitalOcean Managed Agents BB

Best for Teams that want hosted coding agents or code execution with pause, fork and approval controls, and already use DigitalOcean.

Ahead on

  • Reliability, 60 against 32
  • Schema & documentation, 91 against 86
  • Security & auth, 86 against 46
  • Payments & pricing, 45 against 30
  • Transparency & trust, 72 against 59

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Public preview only. The preview terms exclude SLAs, support obligations and data durability guarantees

Together Code Sandbox C

Best for Teams already buying from Together, and former CodeSandbox SDK users, who want Docker-defined sandboxes with disk and memory snapshots from Python or TypeScript.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

The SDK and CLI work only for organisations Together has enabled, and the docs say to contact Together for access

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.

Security & auth DigitalOcean Managed Agents +40

DigitalOcean Managed Agents 86

DigitalOcean API tokens are full access, read-only or custom scoped (agent_harness_session:create on the operation read), and OAuth tokens are issued through the OAuth flow. Expiry and rotation weren't re-read for this listing (25 of 30). Permission policies allow, ask or deny actions, strict rules fail a session rather than run unenforced, the filesystem can be read-only, and ask pauses the agent for human approval. Without a permissions block each adapter keeps its own default (18 of 20). The permissions page says prompts and instructions are not a boundary and that a deny rule is, scoped secrets keep credentials out of the sandbox, and egress can be limited to an allowlist. Egress is open by default (12 of 15). Audit logs record each agent action, the policy decision and who answered an approval, per the concepts index. The audit log page itself wasn't read (13 of 15). security.txt valid to 5 April 2028, an Intigriti programme, and SOC 2 Type II and SOC 3 on the security page. Whether the SOC 2 scope covers the preview was not established (18 of 20). 25 + 18 + 12 + 13 + 18 = 86.

Together Code Sandbox 46

Project-scoped API keys, revocable within about five minutes, with optional expiry and rotation guidance, read as the Together inference and fine-tuning listings read the same key model (30). The in-VM OpenAPI document still lists ?token= as a documented way to authenticate the WebSocket exec path, so the checklist's fixed 10 comes off (20). Each sandbox is a virtual machine. Every port is open to everyone unless the experimental inbound policy is set, no outbound rules exist, and project roles are admin and editor with no read-only role (8). The sandbox returns the output of code the agent ran, with no guidance on untrusted output found (8). Sandboxes can be listed with tags and status_reason. No audit log found (3). A PGP-signed security.txt (Expires 2028-09-30) points Contact and Policy at HackerOne with no acknowledgement time, the value this run gives a disclosure route with no stated time (7). 20 + 8 + 8 + 3 + 7 = 46.

Reliability DigitalOcean Managed Agents +28

DigitalOcean Managed Agents 60

Hosted lines, for the Harness Runtime API. status.digitalocean.com is a Statuspage with product and region components, and it lists an Agent Runtime component under Agentic Inference Cloud. Whether that component covers Harness Runtime was not established, and nothing on the page names Managed Agents (15 of 20). The history feed, read on 18 November 2026, names no incident for Managed Agents, Harness Runtime, Action Gateway or the public API since the launch on 21 September, 58 days of history. The incidents in that time were regional or for other products, such as App Platform on 16 November. The public API incident of 24 and 25 August falls in the 90-day window but before launch (20). The API reference gives 5,000 requests an hour and 250 a minute per token, and the docs give 100 concurrent sessions a team (15). Every operation documents 429 with ratelimit-limit, ratelimit-remaining and ratelimit-reset headers, and the event stream returns Retry-After. Deletes and transfer cancels are idempotent, but only workspace creation takes an Idempotency-Key (10 of 15). The preview terms say no SLA applies (0). Public preview, not GA (0). 15 + 20 + 15 + 10 + 0 + 0 = 60.

Together Code Sandbox 32

Read with the hosted lines. status.together.ai lists the website, the playground and inference models with no component for the sandbox service, and a vendor status page with no component for the product takes 15. Incident line kept at 5. The Together page posts no incident since 6 January 2025, while status.codesandbox.io, which lists the CodeSandbox API and two clusters, wasn't re-read on 4 November (codesandbox.io answers a bot check, so its terms are unread), per the 8 October check (5). No rate or concurrency limits found, and the migration guide says the concurrency count and limit are not exposed (0). Both SDKs retry 408, 429, 500, 502, 503 and 504 three times with exponential backoff from 0.5 seconds plus jitter, and the SDK references say snapshots.create is not idempotent and should be excluded from retries. That is safe-retry guidance with no idempotency keys (12). No SLA found, and the terms make no uptime guarantee outside an order form (0). The docs still say the SDK must be enabled for an organisation, on request to sales, which is not general availability (0). 15 + 5 + 0 + 12 + 0 + 0 = 32.

Payments & pricing DigitalOcean Managed Agents +15

DigitalOcean Managed Agents 45

No x402, MPP or L402 (0). Per-unit prices are published without a login, $0.044 per vCPU-hour, $0.0095 per GB-hour, $0.05 per GiB-month and $0.10 per 1,000 Action Gateway calls (30). New customers get a $5 credit. Whether sign-up needs a card was not established, so this line takes half, as the digitalocean-mcp listing did (15 of 30). A person signs up, opts in to the preview terms and creates a token in the control panel (0). 0 + 30 + 15 + 0 = 45.

Together Code Sandbox 30

No x402, MPP or L402 found (0). The pricing page still lists Code Sandbox at $0.0446 per vCPU-hour and $0.0149 per GiB of RAM per hour without a login, and does not say whether the rate covers the new SDK as well as the legacy one (20). The billing docs say Together has no free trial and that platform access needs a minimum $15 credit purchase (0). Access needs a browser signup, a payment and a request to Together to enable the organisation (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Transparency & trust DigitalOcean Managed Agents +13

DigitalOcean Managed Agents 72

Closed service under DigitalOcean's terms and the preview terms of 11 November 2026 (15 of 30). The preview terms promise no training on Action Gateway inputs or results, but give no data durability guarantee, say data and traces may be lost without notice, and enable Insights by default with opt-out only through support. The privacy policy and DPA weren't re-read (12 of 30). The preview terms allow breaking changes and deprecation without warning. In practice the 26 October rename of agent to harness kept the old name working, and legacy template bases stayed available (8 of 20). The preview terms point to DigitalOcean's subprocessor list, which wasn't read, and Insights telemetry may be stored outside the region, including in the United States (13 of 20). 15 + 12 + 8 + 13 = 48.

Together Code Sandbox 59

A closed service under Together's terms of service (19 May 2026). The SDKs, CLI and OpenAPI documents are MIT, which doesn't raise the line for a closed API, as for the Together inference and fine-tuning listings (15). The privacy policy (17 December 2025) says data is not used for training without opt-in. Its table of data types covers inference, fine-tuning and GPU clusters with no sandbox row, and no retention period for sandbox filesystems or snapshots was found beyond an optional snapshot ttl (12). The legacy @codesandbox/sdk page is still marked deprecated with no end date, the deprecations page covers models only, and breaking SDK changes are marked in the changelog. Kept as a partial (8). No sub-processor list or data locations for sandboxes found. A docs example names a cluster na-us-ce-01, and the trust centre was unread (3). 15 + 12 + 8 + 3 = 38.

Schema & documentation DigitalOcean Managed Agents +5

DigitalOcean Managed Agents 91

DigitalOcean's public OpenAPI description (Apache-2.0, digitalocean/openapi, last commit 18 November 2026) has 54 Harness Runtime paths, and the API reference generated from it lists 67 operations (25). llms.txt and a Markdown copy of every docs page, announced at the top of each page for AI agents (10). The concept pages say when to pause rather than remove a session, what a persistent workspace keeps, what is and isn't a permission boundary, and when rules are enforced at the agent or the gateway (18 of 20). Typed parameters such as per_page as int32 at least 0, 62 enums in the agents resource files, and required fields (13 of 15). curl and doctl examples on each operation, and specific 400 descriptions such as invalid page tokens and incompatible credentials (15). Paths are versioned under /v2, with dated release notes for each service (10). 25 + 10 + 18 + 13 + 15 + 10 = 91.

Together Code Sandbox 86

Two public OpenAPI documents in the repository and on GitHub Pages, the management API (3.1.0, 17 operations) and the in-VM API (3.0.3, 25 operations) (25). docs.together.ai has llms.txt and a Markdown twin of the page, and each package ships an LLMS.md with the references (10). The concept docs say when to snapshot memory rather than disk only and what ephemeral means, while 36 of 114 typed nodes in the management document carry a description (14). Enums for status, bounds on cpu, memory_bytes, ttl and limit, with experimental left loose (12). Examples in Python, TypeScript and the CLI, and an error object with code, message and errors. No list of error codes found, and 429 is not in the document (10). /v1 paths, semver packages and a generated CHANGELOG.md (15).

Score by category

CategoryWeightDigitalOcean Managed AgentsTogether Code SandboxEdge
Reliability16%6032DigitalOcean Managed Agents +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9186DigitalOcean Managed Agents +5
Agent ergonomics13%7070even
Security & auth14%8646DigitalOcean Managed Agents +40
Payments & pricing10%4530DigitalOcean Managed Agents +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8083Together Code Sandbox +3
Transparency & trust7%7259DigitalOcean Managed Agents +13
Negative events≤1500
TotalBB 72.1/100C 56/100

Facts side by side

FactDigitalOcean Managed AgentsTogether Code Sandbox
KindHTTP APIHTTP API
VendorDigitalOcean, LLCTogether AI
Hosted endpointhttps://api.digitalocean.com/v2/harness-runtimehttps://api.bartender.codesandbox.io
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service under DigitalOcean's Terms of Service Agreement and the Managed Agents Public Preview Terms. The OpenAPI description in digitalocean/openapi is Apache-2.0Proprietary service under Together's terms of service. The SDKs, CLI and OpenAPI documents on GitHub are MIT
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-11-182026-10-07
Terms last updated2026-11-11no date given
Privacy policy last updated2025-01-01no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone3 stars, 1.3k npm/wk

How the scores have moved

Verdicts

DigitalOcean Managed Agents

Harness Runtime has a public OpenAPI contract, per-second CPU billing, pause, fork and rollback, and permission policies that can block or hold an agent's actions for approval. The whole product is a public preview whose terms rule out SLAs and data durability and allow breaking changes without warning.

Together Code Sandbox

Two public OpenAPI documents, MIT clients for Python and TypeScript, cursor pagination and SDK retries with guidance on which writes not to retry make the surface easy for an agent to drive. Access is the limit. Together enables the SDK per organisation on request, publishes no rate limits or SLA, and its status page has no sandbox component.

Before you call either

DigitalOcean Managed Agents

  1. Pause sessions you are not using. A paused session keeps its files and history and stops compute charges
  2. Set permissions.default explicitly. Without a permissions block, each adapter keeps its own default
  3. Set an egress allowlist in the environment spec. Without one the sandbox can reach any host
  4. If a create times out, list sessions before retrying, because session creation has no idempotency key
  5. Keep copies of important work outside the preview. The terms say data and execution state may be lost without notice

Together Code Sandbox

  1. Confirm the organisation is on Together's allowlist before installing. A valid TOGETHER_API_KEY alone is not enough
  2. Build a snapshot first with snapshots.create. No default image exists, and every sandbox needs snapshot_id or snapshot_alias
  3. Set ttl at creation or call terminate(). Nothing stops a sandbox otherwise, and closing the Python client leaves it running
  4. Store the snapshot alias, not the sandbox ID. A terminated sandbox can't restart, and its state lives at sandbox:<id>
  5. Exclude snapshots.create from retries with should_retry, and set experimental.network_policy before serving anything private on a port

Questions

Which is better for AI agents, DigitalOcean Managed Agents or Together Code Sandbox?

DigitalOcean Managed Agents scores 72.1 (BB) on agent readiness against Together Code Sandbox's 56 (C), and leads in 5 of 7 scored categories.

Do DigitalOcean Managed Agents and Together Code Sandbox need an API key?

DigitalOcean Managed Agents takes an API key or an OAuth sign-in. Together Code Sandbox needs an API key.

Can an agent call DigitalOcean Managed Agents and Together Code Sandbox without installing anything?

Yes. DigitalOcean Managed Agents has a hosted endpoint at https://api.digitalocean.com/v2/harness-runtime and Together Code Sandbox at https://api.bartender.codesandbox.io.

Other comparisons with DigitalOcean Managed Agents or Together Code Sandbox

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.