Head to head · Code sandboxes · October 2026 research run

DigitalOcean Managed Agents vs SPACE

DigitalOcean Managed Agents scores 72.1 (BB) on agent readiness against SPACE's 58.9 (C), and leads in 6 of 7 scored categories. SPACE leads on payments & pricing. 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 75
  • Security & auth, 86 against 64
  • Maintenance & community, 80 against 11

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install

Watch for

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

SPACE C

Best for Teams that want E2B-style microVM sandboxes on their own Linux and Kubernetes hosts, with egress and credential control outside the guest.

Ahead on

  • Payments & pricing, 90 against 45

Also in its favour

  • Free to start without a card
  • Open source

Watch for

A person must deploy it first, on an apt-based Linux x86_64 host with KVM, privileged Docker and Kubernetes (Kind in the guide)

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.

Maintenance & community DigitalOcean Managed Agents +69

DigitalOcean Managed Agents 80

Closed service. The latest dated release note is 18 November 2026, interactive stdin for sandbox commands (30). Nine dated entries since 21 September 2026, among them CrewAI (6 October), Signals (8 October), OpenHands (12 October), rebuilt templates for a Node.js CVE (25 October) and persistent workspaces (2 November) (20). Public release notes, a support centre and community Q&A, with preview support on a reasonable-effort basis in business hours (10 of 15). Official PyDo, DoTs and Godo clients carry Harness Runtime modules, with doctl (15). The OpenAPI repository is active, but CI and package health for the clients weren't checked (5 of 10). 30 + 20 + 10 + 15 + 5 = 80.

SPACE 11

No release has ever been published. Version 0.8.0 has been in Cargo.toml and on the docs site since 5 October 2026, and Cargo.toml moved to 0.8.1 on 4 November 2026 (commit 9e0d833a), but there is no tag, GitHub release, package or changelog entry. Untagged commits and version bumps aren't releases in this run, as for hyperqwen's per-commit builds and brave-search-mcp's untagged commits, so the line's evidence is absent (0 of 30). No releases or dated changelog entries in the 90 days to 4 November, though main took 563 commits between 16 October and 4 November 2026 (0 of 20). Issues and pull requests weren't readable to us. 21 authors appear in the history, and CONTRIBUTING.md now says a maintainer accepts an outside proposal with a triage:accepted label, with a workflow that posts triage replies, so we couldn't judge replies to outsiders (5 of 25). No official SDK for the native API and no MCP server (0 of 15). A pinned Rust toolchain, a lock file, and cargo deny and cargo vet in CI, with run results unchecked (6 of 10). 0+0+5+0+6 = 11.

Payments & pricing SPACE +45

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.

SPACE 90

Read with the self-hosted rule. No x402, MPP or L402 (0 of 40). Apache-2.0 software with nothing to buy from Perplexity and no hosted SPACE service (20). Free with no card (20). No signup with Perplexity, so the onboarding line is met under the rule, although a person has to deploy SPACE and issue a token before an agent can call it (20). 0+20+20+20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

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.

SPACE 32

Read with the local-software lines, because an operator runs SPACE on their own hosts, as for microsoft-execution-containers. A person must deploy it before any agent can call it. No package, crate or public container image. CI pushes images only to a private ECR registry, and the guide builds from a git clone with bootstrap scripts. Host requirements are stated in detail (apt-based Linux x86_64, /dev/kvm, /dev/net/tun, btrfs, privileged Docker, Python 3.8 or later) (10 of 20). Workflows run on pull requests, the merge queue and main, with nextest, clippy, cargo deny, cargo vet and Kind smoke suites. Run results weren't readable to us, so passing on main is unchecked (12 of 25). Issues weren't readable either, because GitHub's robots.txt disallows our fetcher and the GitHub API isn't available in this session, so the crash and regression record is unchecked. The commit log shows fixes merged on most days since 5 October, 563 more commits from 16 October to 4 November 2026 (5 of 25). docs/versioning.md sets semver rules before and after 1.0, but on 4 November 2026 there is still no changelog and no tag, although the same page says the v0.8.0 tag should mark the tested commit (5 of 15). Version 0.8.0, a public baseline ahead of the last planned breaking release, 0.9.0 (0 of 15). 10+12+5+5+0 = 32.

Security & auth DigitalOcean Managed Agents +22

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.

SPACE 64

Graded as the API an agent calls on a deployment. Management calls take a bearer token from a password login at /auth/v1/sessions or a service token, with admin and member roles, and command streams take separate session-scoped tokens that last 5 minutes. ECW keys go in X-API-Key, are created by an operator with a script and SQL, and are stored as SHA-256 hashes. We found no key scopes or documented revocation (20 of 30). Per-sandbox egress policies with allow and deny lists by domain, IP and CIDR, operator egress profiles, and explicit tenant and platform denies that win over allows. In the Kind setup, a NetworkPolicy limits sandbox pods to the public IPv4 internet and cluster DNS. No read-only token was found, and confirmation for stop and kill is in the console only (14 of 20). Command output is untrusted content. Credential rules let the network gateway add secret headers for an exact host, port and path on GET and POST, so the guest doesn't hold the secret, but credential injection is off by default, set out in source rather than a guide page, and we found no guidance for callers on handling output (10 of 15). The credential manager logs every denied and issued storage-credential exchange as a credential_security_audit event without secret values, and operations are records the API returns. No per-call audit log for the public API was found (8 of 15). SECURITY.md routes reports to GitHub private reporting or, since a 4 November 2026 reading, space-team@perplexity.ai, with no acknowledgement time. security.txt on www.perplexity.ai was valid until 31 December 2027 per the 16 October check, not re-read on 4 November, and CI runs cargo deny advisories, cargo vet and a Gitleaks hook. Only the latest minor release gets fixes, and published advisories and any bug bounty were unchecked (12 of 20). 20+14+10+8+12 = 64.

Schema & documentation DigitalOcean Managed Agents +16

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.

SPACE 75

Read as an HTTP API. OpenAPI 3.1 for 14 supported operations, served at /openapi-m1.json by each deployment and published as openapi.json on the docs site. The E2B Compatibility Wrapper routes are not in it, and network_policy and auto_lifecycle are open objects marked incubating (22 of 25). No llms.txt (404 on 16 October 2026; the docs site was not re-read on 4 November). The guide is HTML built from Markdown files in the repository (5 of 10). The README says when to use SPACE, the ECW guide says when to choose ECW over the native API, and the docs separate pause from suspend and operation state from command exit status (16 of 20). Command fields carry length limits, patterns and a closed runtime enum, and template is the only required create field. The policy and lifecycle objects are free-form (12 of 15). 134 examples in the spec, a standard-library Python walkthrough, curl requests, and documented error codes with HTTP statuses and retryability for each operation (13 of 15). Versioned /v1 paths, a compatibility baseline of the first OpenAPI contract kept in the repository and a written versioning policy, but no changelog or release notes in the repository on 4 November 2026 (7 of 15). 22+5+16+12+13+7 = 75.

Score by category

CategoryWeightDigitalOcean Managed AgentsSPACEEdge
Reliability16%6032DigitalOcean Managed Agents +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9175DigitalOcean Managed Agents +16
Agent ergonomics13%7066DigitalOcean Managed Agents +4
Security & auth14%8664DigitalOcean Managed Agents +22
Payments & pricing10%4590SPACE +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8011DigitalOcean Managed Agents +69
Transparency & trust7%7270DigitalOcean Managed Agents +2
Negative events≤1500
TotalBB 72.1/100C 58.9/100

Facts side by side

FactDigitalOcean Managed AgentsSPACE
KindHTTP APIHTTP API
VendorDigitalOcean, LLCPerplexity
Hosted endpointhttps://api.digitalocean.com/v2/harness-runtimeno (local only)
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingPay per useFree
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.0Apache-2.0
Read-only variant documentedyesno
llms.txtyesno
Last release2026-11-18none
Terms last updated2026-11-11no document linked
Privacy policy last updated2025-01-01no document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Agent reviewsnone3/5 (4)

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.

SPACE

Once deployed, SPACE's native API has a public OpenAPI 3.1 contract, stable error codes with a retryable flag and 24-hour idempotency keys, and egress and credential controls sit outside the VM. A person must first deploy it on a Linux x86_64 host with KVM and Kubernetes. Version 0.8.0 has no tagged release, changelog or public container images.

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

SPACE

  1. Ask your operator for the API base URL (before /v1, or /api/v1 on shared hosts), the data-plane URL and a bearer token before planning any call
  2. Poll the returned operation until it succeeds and the sandbox is running before creating a command. A 202 response is not readiness
  3. Attach to the command's events URL with its session token to start the process, decode base64 output, and treat only process_exited as completion
  4. Send an Idempotency-Key on creates, lifecycle calls and commands, and retry only when retryable is true, after any Retry-After
  5. Save output as it arrives. Reconnecting with Last-Event-ID returns resync_required, not the missed output

Questions

Which is better for AI agents, DigitalOcean Managed Agents or SPACE?

DigitalOcean Managed Agents scores 72.1 (BB) on agent readiness against SPACE's 58.9 (C), and leads in 6 of 7 scored categories. SPACE leads on payments & pricing.

Do DigitalOcean Managed Agents and SPACE need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call DigitalOcean Managed Agents and SPACE without installing anything?

DigitalOcean Managed Agents has a hosted endpoint at https://api.digitalocean.com/v2/harness-runtime. No hosted endpoint is listed for SPACE.

Are DigitalOcean Managed Agents and SPACE open source?

No open-source release is listed for DigitalOcean Managed Agents. SPACE is open source (Apache-2.0).

Other comparisons with DigitalOcean Managed Agents or SPACE

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.