WSO2 Releases Agent Manager as Enterprises Look to Control Growing AI Agent Sprawl

Masonry The interesting part of this WSO2 launch is that it assumes the hard problem is no longer building one cute agent. It's cleaning up the mess after five teams built fifteen of them.

Eyre Right.

Eyre And honestly, that feels correct. The GA release is WSO2 Agent Manager, open source, and the whole pitch is a central control plane for governance, identity, security, and ops across different models, frameworks, and environments.

Masonry Yeah, which is such an Exploring Next thing to end up back at. We keep crawling toward the same boring conclusion that the wrapper is not the product, the receipts are.

Eyre Okay, that's good.

Masonry But it does matter right now. If you've got one agent in Bedrock, another thing someone glued together with LangChain, and a custom internal one talking over MCP, your actual job becomes permissions and audit, not prompt craft.

Eyre Mm-hm.

Eyre That's also why this slots straight into that unresolved fight we've had about where governance lives. Data layer, gateway, identity, runtime. WSO2's answer is basically, not one of those alone, you need a layer that can sit across them.

Masonry And after the hook, tiny catch-up beat, because apparently this is episode nine eighty-one and we still do this. I cannot believe we're spending another Wednesday-adjacent conversation on coordination machinery.

Eyre We started in November and somehow arrived at, wow, identity for robots. Which, to be fair, is where the pain actually is.

Masonry Exactly.

Masonry So the GA bits are pretty concrete. They added deeper agent identity, governance controls for MCP interactions, and a Kubernetes-native sandboxed runtime. That's not vague platform vapor. Those are three pretty specific pressure points.

Eyre Yeah.

Eyre The identity piece is the center of it for me. The article calls out verifiable agent identity, role-based access, delegation, token exchange, revocation, plus lifecycle controls like moving agents through dev, staging, prod, and suspending them when needed.

Masonry Which is a real buyer story. If you're an enterprise platform team, you do not want every agent framework inventing its own little badge system and emergency stop button. You want one inventory, one place to say this agent can touch that API and absolutely not this other one.

Eyre Right, right.

Eyre And the MCP part is sneakily important. A lot of agent risk now comes from tool access and egress, not just model output. So governance at the MCP layer means you can treat tool calls as policy objects instead of trusting every app team to be careful forever.

Masonry No way.

Masonry Well, and that's the thing that keeps this from being governance theater. If policy only exists in a slide deck, great, lovely. If it can actually sit on the agent, MCP, and L L M layers, with stuff like P I I masking and rate limiting across more than forty built-in controls, now we're talking about something that might ship into a real org.

Eyre The runtime is the other half. They added a sandboxed execution environment that's Kubernetes-native, which tells you they're worried about agents touching files, tools, APIs, enterprise systems, all the usual foot-guns. That is the structural move. Otherwise governance is just very sincere logging after the damage.

Masonry Very sincere logging is such a brutal category.

Eyre You know it's true.

Masonry It is. Also, quick sideways riff, the phrase agent estate always makes me picture tiny little suburban developments of bots with identical lawns and terrible H O A rules.

Eyre Oh, that's upsettingly vivid.

Masonry Anyway. The adoption story here is strongest for teams that already know they're going multi-framework or multi-cloud. WSO2 supports LangChain, CrewAI, Amazon Bedrock, Azure, Ballerina, and custom agents, so the pitch is you don't rebuild governance every time the model stack changes.

Eyre And I buy that more than I buy a lot of single-vendor agent studios. But I'd still keep the caveat on. The article itself nods to the wider view that nobody has the complete governance stack across every layer, so this probably joins identity systems, policy engines, and infra controls rather than replacing all of them.

Masonry Yeah, no, you're completely right. I think the win is narrower and better: separate the control plane from agent logic early enough that switching frameworks doesn't mean redoing auth, policy, tracing, and evals from scratch. OpenTelemetry tracing and ongoing rule-based plus L L M-based evals help there too, because drift is part of the product, not an afterthought.

Eyre Masonry, that's also why open source matters here. If you're asking an enterprise to put governance above the agent layer, they are going to care a lot about not stapling that governance to one model vendor's roadmap.

Masonry Yep. This is not the glamorous side of agents, but it might be the side that survives contact with procurement. Okay, that's enough intellectual honesty for one Friday, Eyre.