TITLE: DigitalOcean Launches Managed Agents, Removing the Infrastructure Barrier to Running AI at Work DATE: 2026-09-24 COMPANY: DigitalOcean TOPIC: Agent Systems SUMMARY: DigitalOcean launched Managed Agents in public preview on 22 September 2026, giving developers a single environment to run, tool, and infer AI agents without building the underlying infrastructure. Each agent session runs in an isolated microVM, connects to 16,000 plus tools through a managed MCP endpoint called Action Gateway, and draws from 75 plus models. CPU billing pauses when the agent is idle, so businesses pay only for active work. WHAT CHANGED: DigitalOcean announced the public preview of Managed Agents on 22 September 2026, describing it as "agent execution, tool access, and inference together on one cloud." The announcement positions the product as a complete stack rather than a component. Developers create agent sessions in the Cloud Console or through the doctl CLI, selecting a harness (Claude Code, Codex CLI, OpenCode, Hermes, or LangGraph) and connecting tools through Action Gateway. Action Gateway is the mechanism that differentiates Managed Agents from earlier DigitalOcean AI products. It acts as a single managed MCP endpoint, handling authentication to connected services on behalf of the agent so that developers do not need to share credentials directly. The gateway covers 500 plus providers across 16,000 plus individual tools. Businesses can also connect their own MCP servers through the same endpoint. Each agent session runs in its own isolated microVM, a lightweight virtualisation unit that provides resource and process isolation between concurrent sessions. When a session is idle, it pauses and retains its state, and CPU billing stops. When work resumes, billing restarts. This pause-and-resume approach is designed specifically for agentic workloads that may run in bursts rather than continuously. Serverless Inference is included in the same platform, giving agents access to 75 plus models from open and proprietary providers. The billing structure runs from the same DigitalOcean account, consolidating what previously required separate API keys and invoices across multiple providers. WHY IT MATTERS: The infrastructure problem was always the blocker, not the model. Teams that could not ship AI agents to production were not stuck on capability. They were stuck on where to run the agent, how to connect it to internal tools safely, how to manage credentials, and how to prevent spiralling cloud costs. Managed Agents addresses all four. Governed tool access is the compliance story many businesses have been missing. Action Gateway gives organisations a single point to review, scope, and revoke what any agent can do. For regulated industries, or any company with client data in its systems, this matters more than raw capability. The alternative, running agents with unrestricted API access to business tools, is not a governance architecture most organisations can defend. Claude Code as a first-class harness is significant. DigitalOcean has named Claude Code alongside Codex CLI and OpenCode as supported harnesses. This is not incidental support. It means businesses running Claude Enterprise or Claude Team can extend those deployments into DigitalOcean-managed agent infrastructure with a clear integration path, without managing separate cloud environments. Pay-when-active billing changes the economics of agent pilots. One of the most common objections to running more agents is cost uncertainty. Managed Agents addresses this by pausing billing when the agent is idle. For businesses running agents on recurring tasks rather than continuous pipelines, the effective cost is substantially lower than provisioning always-on compute. DigitalOcean's market is the business that most needs this. DigitalOcean built its business serving developers at companies too small for AWS enterprise support and too technical for no-code tools. Managed Agents is aimed directly at that segment. A 40-person business wanting to run a HubSpot-connected sales agent on Claude Code no longer needs a cloud architect to make it happen. DAVID & GOLIATH ANALYSIS: The announcement that will define AI in business over the next 12 months is not a new model. It is the infrastructure layer that makes running agents simple enough to be a normal business decision rather than a technical project. DigitalOcean has made a credible move toward that layer with Managed Agents. The combination of isolated execution, governed MCP tool access, and pay-per-use billing is exactly the architecture an operator needs to say yes to AI agents in production rather than keeping them in a controlled demo. Action Gateway is the part that deserves the most attention. MCP (Model Context Protocol) defined how AI systems connect to tools. Action Gateway operationalises that standard for businesses that do not want to build their own integration infrastructure. When a team can say "our agent connects to HubSpot and Stripe through a single governed endpoint that lives in our DigitalOcean account," they have an AI architecture story that holds up to scrutiny from finance, legal, and security. For businesses already using Claude, the Managed Agents announcement closes a gap. You could run Claude in a chat interface or through the API, but deploying Claude Code as an agent with persistent state, governed tool access, and per-use billing required assembling those pieces yourself. That assembly work is now done. The path from a Claude Enterprise subscription to a production agent doing real work in your business systems is shorter than it has ever been. RELEVANT SYSTEMS: Employee Amplification Systems, AI Growth Engine, Organisational Intelligence System SOURCE URL: https://davidandgoliath.ai/daily-ai-briefing/digitalocean-managed-agents-mcp-smb-launch FEED URL: https://davidandgoliath.ai/daily-ai-briefing/feed --- Published by David & Goliath | https://davidandgoliath.ai Daily AI Briefing: one AI development per day, decoded for business operators. This is a structured companion file optimised for LLM retrieval and citation.