DigitalOcean Harness Runtime Limitspublic

Last verified 1 Oct 2026

DigitalOcean Harness Runtime provides managed, hardware-isolated microVM sandboxes with built-in tools such as Chromium to run harnesses and execute arbitrary code. Rich lifecycle APIs preserve conversational history and working state across sessions, letting you pause, resume, and fork work to control costs and adapt to the nonlinear nature of agentic workflows. Scale complete agents such as Claude Code or use sandboxes independently for code execution, all through the same service. See What You Can Build for example use cases.

Copy page as Markdown View page as Markdown
  • You can run up to 100 sessions at once per team, depending on your resource tier. Your limits depend on your account history and spend with DigitalOcean. To request higher limits, including more concurrent sessions, go to the Resource Limits page in the control panel and request an increase.
  • Agent Droplets plans allow unlimited agents, subject to fair use.
  • Idle suspend defaults to 15 minutes. The LangGraph guest has a 10-minute session idle timeout. Paused sessions don’t incur compute charges. See Harness Runtime Pricing.
  • Sessions pause when all your balances are empty. See What Happens When All Your Balances Are Empty.
  • Each session has a monthly active compute cap of 744 hours.
  • Default sandbox size is mars-2vcpu-4gb (2 vCPUs and 4 GB memory). Available sizes are mars-1vcpu-1gb, mars-2vcpu-2gb, mars-2vcpu-4gb, mars-4vcpu-8gb, and mars-16vcpu-32gb. See Sandbox Sizes.
  • Maximum file size for upload and download is 50 GiB per file.
  • Sandbox egress is unrestricted unless the environment spec sets an allowlist. Naming any allowed host restricts the session to that list, plus the platform and adapter hosts merged in automatically.
  • Webhook notifications for run lifecycle events are currently not supported.
  • Live preview of a running app is currently not available.
  • Connecting to private VPC resources and VPC peering is not supported.
  • Model access keys scoped to a VPC network are not supported. Use a non VPC-scoped key instead.

We can't find any results for your search.

Try using different keywords or simplifying your search terms.