Every enterprise technology platform faces the relevance question when the market shifts. The question for MuleSoft in the agentic AI era is the same question it faced in the cloud transition and the API economy: does this platform remain relevant as the context changes?
I believe the answer is yes — but it requires being precise about why.
The Agentic Enterprise Context
Most enterprises approaching agentic AI are not starting from a clean slate. They have:
- Existing API estates that took years and significant investment to build
- Legacy systems that will not be replaced in the near term
- Regulated environments where governance is not optional
- Hybrid infrastructure that spans on-premises, cloud, and increasingly edge
Any AI platform that only works well in greenfield, cloud-native, unregulated environments has a relevance problem in enterprise. That's not where most enterprise workloads live.
Why CARGO Matters Here
CARGO — Composability, Actionability, Reusability, Governance, Orchestration — is my framework for evaluating platform relevance in the agentic enterprise. Let me apply it to MuleSoft specifically.
Composability: MuleSoft's entire architecture is built around composability. APIs are the building blocks. The ability to compose new capabilities from existing components — rather than building from scratch — is exactly what agentic AI needs. Agents don't need new integrations for every new capability; they need access to the existing integration estate.
Actionability: Agents need to act. MuleSoft's flow architecture enables agents to trigger real actions — not just retrieve data, but update records, initiate workflows, send notifications, and orchestrate downstream processes. This is a meaningful differentiator against pure data retrieval platforms.
Reusability: The API reuse case is straightforward: every API built on MuleSoft is potentially an agent action. Enterprises that have invested in building a well-governed API estate have already done much of the work required to expose those capabilities to AI agents. This reuse multiplier on existing investment is significant.
Governance: In regulated enterprise environments — financial services, healthcare, government — governance is not a nice-to-have. It is table stakes. MuleSoft's policy enforcement at the API gateway level applies to AI agent traffic the same way it applies to any other API consumer. This is not a trivial advantage.
Orchestration: Multi-agent architectures require orchestration — coordinating multiple agents, across multiple systems, with appropriate sequencing and error handling. MuleSoft's orchestration capabilities, built for complex integration scenarios, are well-suited to this challenge.
The Honest Assessment
No single platform wins all five dimensions for all enterprises in all contexts. MuleSoft's CARGO profile is strongest in regulated, hybrid, integration-heavy enterprise environments — which happens to describe most large enterprise buyers.
The relevance question is not "is this platform perfect for agentic AI?" The relevance question is "is this platform better suited than alternatives for the agentic AI use cases that matter most to our specific enterprise context?"
For the MuleSoft customer base, I believe the answer is yes.
Views are personal. I work at MuleSoft, and this reflects my own analysis.