The rise and risks of agent management platforms


the-rise-and-risks-of-agent-management-platforms-v2

Tharon Green/ZDNET/Getty Images

Follow ZDNET: Add us as a preferred source on Google.


ZDNET’s key takeaways

  • The number of agents continues to grow, increasing the risk of sprawl.
  • Professionals must consider using agent management systems.
  • These systems can help manage agent sprawl, but beware of challenges.

Enterprises worldwide have 28.6 million active agents, a figure forecast to exceed 2.2 billion by 2030, according to Statista.

Also: These top 30 AI agents deliver a mix of functions and autonomy

Agent wranglers are required to bring management sensibilities to this growing space. So, can AI agent sprawl be tamed? Some vendors are giving it a try, leading to a new technology category, agent management systems, that are tasked with managing networks of AI agents. 

Building a platform

An agent management platform essentially acts as a digital HR department for AI agents, and experts suggest now is the right time for such offerings. 

Agents running outside of management frameworks are essentially the AI equivalent of shadow IT. 

“It works until it doesn’t, and when it stops working, you have no audit trail, no version control, and no governance to fall back on,” noted Shelly Palmer, professor at Syracuse University and CEO of The Palmer Group.

Agent management solutions on the market include Google Vertex AI Agent Builder, Amazon Bedrock Agents, Microsoft 365 Copilot, Decagon AI, and Sierra AI, serving various purposes from orchestrating systems to multi-agent automation. 

These platforms are essential to the future of agentic automation. The key to success is to “treat agents as infrastructure rather than features,” said Diptamay Sanyal, principal engineer at CrowdStrike. 

Also: AI agents are fast, loose, and out of control, MIT study finds 

Agents aren’t one-off builds. “The problem is you end up with dozens of agents with no shared context model, no consistent governance, and no reusable patterns,” Sanyal said. “A proper management platform gives you composable primitives, multi-tenant isolation, model routing across LLM providers, and observability into what agents are actually doing.”

Fighting sprawl 

With agents multiplying by the millions, handling everything from sales to software development, the big hurdle is that they all want access to the same data.

“This creates an AI governance challenge,” said Manu Narayan, CIO at GitLab. “If you don’t build your AI stack intentionally, you could end up with dozens of vendors, and all of their agents, holding the keys to the kingdom.”  

Also: How to build better AI agents for your business – without creating trust issues

This situation leads to agent sprawl, “a fragmented ecosystem of loosely managed agents with inconsistent behavior, duplicated functionality, and unclear ownership,” said Yash Vijay Patil, software engineer with Texas A&M University. “Without strong governance, this sprawl can lead to operational inefficiencies and increased risk exposure.”  

Many vendors and internal teams are building agent solutions for specific use cases, but often they lack shared identity models, lifecycle policies, or risk frameworks, said Monika Malik, a lead data and AI engineer at AT&T. “That approach creates duplication, inconsistent behavior, hidden costs, and security exposure. The problem will not be too few agents, but too many unmanaged ones.”

Then there is the complexity of agent networks exacerbated by the popularity of consumer options like OpenClaw, said Brian Jackson, principal research director at Info-Tech Research Group. “It’s safe to assume some employees will try to automate their work tasks with those. This leads to a problem in tracking all the agents you have deployed in the enterprise environment. While different management platforms claim they can discover the agents deployed in your system, the truth is that they are limited by the identity management layer.”  

Agent management platforms offer benefits such as observability, so you know which agents you’re using and what they’re doing, Jackson said. 

Also: Worried AI agents will replace you? 5 ways you can turn anxiety into action at work

In addition, these platforms enable governance by “using a central policy to set guardrails for what agents can and can’t do and keep them aligned with enterprise goals.” Ultimately, these systems enable value realization, as they “monitor performance over time and ensure agent costs and outputs fall within expectations, and add value to work,” he added.  

The role of such management platforms is to “provide a control layer for how organizations deploy, monitor, secure and enhance their agents over time,” said AT&T’s Malik. “The major advantage of these platforms is not just orchestration, but operational discipline: visibility into what agents are doing; where they are pulling data from; how they are making decisions; when human oversight is required.”

Understanding market trends

However, the competition between vendors to own the agentic management space is fierce, Jackson observed. 

“It will be a strategic position where enterprises are building their workflows and crafting deeper ties into an ecosystem,” he said. 

Also: 5 security tactics your business can’t get wrong in the age of AI – and why they’re critical

Consequently, many agent implementations will be tied to familiar systems of record within varying lines of business, Jackson continued. “You end up with a situation where marketing is managing agents out of what used to be the CRM platform, while IT is managing agents from an asset management and observability platform.”

As agents become more autonomous, “defining clear boundaries, monitoring behavior, and maintaining trust will be critical,” said Patil of Texas A&M. “In short, agent management platforms offer powerful leverage, but only when paired with disciplined governance and thoughtful adoption strategies.”

Eliminating complexity is a challenge, “when agents act across multiple interconnected systems simultaneously,” said Narayan.

“Consolidation through agent management platforms helps,” he said. “They establish the context, permission models, security controls, and data boundaries that simplify agent orchestration at scale. Combining this type of platform with a hub-and-spoke model can help you become more intentional across your AI stack without slowing adoption speed.”

Implementing the tech

Another challenge with agent management platforms is “they are harder to change than most cloud choices because they shape workflows, integrations, permissions, and operating models,” said Malik. 

That situation is why adopting agents needs to be an enterprise decision. All stakeholder departments — from engineering to security to legal to data governance to business owners — need to be involved in decisions about the agent management platform. “The primary obstacle is averting fragmented adoption. Organizations should view agent platforms as long-term operating infrastructure, not just another purchase of an AI tool,” said Malik.

Agent platform decisions are difficult to reverse because they are deeply embedded in workflows, data pipelines, and business logic, said Patil. “Evaluate platforms based on interoperability, extensibility, vendor lock-in risks, and support for open standards. Crucially, decisions should not be left solely to engineering — cross-functional stakeholders, including security, data, and business leaders, must be involved.”  

Also: Why enterprise AI agents could become the ultimate insider threat

In addition, professionals should remember that it’s already difficult to get “data and workflows out of legacy software platforms,” said Jackson. “Adding an AI layer on top of that means that the integration goes even deeper into the platform. Trying to migrate an agent management system will be like trying to perform a brain transplant.”  

Businesses should, therefore, prioritize flexibility when moving to an agent management platform. “Evaluating where you are comfortable placing bets on platforms, versus trying to set up on a self-hosted platform,” said Jackson. 

“Given the unpredictability of consumption costs for agentic workloads, it may be wise to architect a system that leverages internal infrastructure and avoids tying business processes to metered charges or consumption-based pricing.”

Professionals should also treat the development and implementation of an agent management platform “like a database selection, not a SaaS tool evaluation,” said Sanyal. “Involve platform engineering, security, and legal from day one. Not after the pilot succeeds. Plus, the decision shouldn’t sit with a single line-of-business owner. It needs platform engineering, security, and whoever owns your identity and access model in the same room.”





Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


When you pick out a phone, you’re also picking out the operating system—that typically means Android or iOS. What if a phone didn’t follow those rules? What if it could run any OS you wanted? This is the story of the legendary HTC HD2.

Microsoft makes a mess with Windows Mobile

The HD2 arrives at an unfortunate time

windows mobile 6.5 Credit: Pocketnow

Officially, the HTC HD2 (HTC Leo) launched in November 2009 with Windows Mobile 6.5. Microsoft had already been working on Windows Phone for a few years at this point, and it was planned to be released in 2009. However, multiple delays forced Microsoft to release Windows Mobile 6.5 as a stopgap update to Windows Mobile 6.1.

Microsoft’s plan for mobile devices was a mess at this time. The HD2 didn’t launch in North America until March 2010—one month after Windows Phone 7 had been announced at Mobile World Congress. Originally, the HD2 was supposed to be upgraded to Windows Phone 7, but Microsoft later decided no Windows Mobile devices would get the new OS.

This left the HD2 stuck between a rock and a hard place. Launched as the final curtain was dropping on one OS, but too early to be upgraded to the next OS. Thankfully, HTC was not just any manufacturer, and the HD2 was not just any phone.

The HD2 was better than it had any right to be

HTC made a beast of a phone

HTC HD2 Credit: HTC

HTC was one of the best smartphone manufacturers of the late 2000s and 2010s. It manufactured the first Android phone, the first Google Pixel phone, and several of the most iconic smartphones of the last two decades. Much of the company’s reputation for premium, high-quality hardware stems from the HD2.

The HD2 was the first smartphone with a 4.3-inch touchscreen—considered huge at the time—and one of the first smartphones with a 1 GHz Qualcomm Snapdragon processor. That processor, along with 512GB of RAM, made the HD2 more future-proof than HTC probably ever intended. Phones would be launching with those same specs for the next couple of years.

For all intents and purposes, the HD2 was the most powerful phone on the market. It just so happened to run the most limiting mobile OS of the time. If the software situation could be improved, there was clearly tons of potential.

The phone that could do it all

Android, Windows Phone, Ubuntu, and more

The key to the HD2’s hackability was HTC’s open design philosophy. It had an easily unlockable bootloader, and it could boot operating systems from the NAND flash and SD cards.

First, the community took to righting a wrong and bringing Windows Phone 7 to the HD2. This was thanks to a custom bootloader called “MAGLDR”—Windows Phone 7.5 and 8 would eventually get ported, too. The floodgates had opened, and Windows Phone was the least of what this beast of a phone could do.

Android on the HTC HD2? No problem. Name a version of the OS, and the HD2 had a port of it: 2.2 Froyo, 2.3 Gingerbread, 4.0 Ice Cream Sandwich, 4.1/2/3 Jelly Bean, 4.4 Kitkat, 5.0 Lollipop, 6.0 Marshmallow, 7.0 Nougat, and 8.1 Oreo. Yes, the HD2 was still getting ports seven years after it launched.

But why stop at Android? The HD2 was ripe for all sorts of Linux builds. Ubuntu—including Ubuntu Touch—, Debian, Firefox OS, and Nokia’s MeeGo were ported as well. The cool thing about the HD2 was that it could dual-boot OS’. You didn’t have to commit to just one system at a time. It was truly like having a PC in your pocket, and the tech community loved it.

Do a web search for “HTC HD2” now, and you’ll find many articles about the phone getting yet another port of an OS. It became a running joke that the HD2 would get new versions of Android before officially supported Android phones did. People called it “the phone that refuses to die,” but it was the community that kept it alive.

The last of its kind

“They don’t make ‘em like they used to”

HTC HD2 close up Credit: TechRepublic

The HTC HD2 was a phone from a very different time. It may have gotten more headlines, but there were plenty of other phones being heavily modded and unofficially upgraded back then. Unlockable bootloaders were much more common, and that created opportunities for enthusiasts.

I can attest to how different it was in the early years of the smartphone boom. My first smartphone was another HTC device, the DROID Eris from Verizon. I have fond memories of scouring the XDA-Developers forums for custom ROMs and installing the latest Kaos builds on a whim during college lectures. Sadly, it’s been many years since I attempted that level of customization.

It’s not all doom and gloom for modern smartphones, though. Long-term support has gotten considerably better than it was back in 2010. As mentioned, the HD2 never officially received Windows Phone 7, and it never got any other updates, either. My DROID Eris stopped getting updates a mere eight months after release.

Compare that to phones such as the Samsung Galaxy S26, Google Pixel 10, and iPhone 17, which will all be supported through 2032. You may not be able to dual-boot a completely different OS on these phones, but they won’t be dead in the water in less than a year. We will likely never see a phone like the HTC HD2 from a major manufacturer again.

HTC Droid Eris


A Love Letter to My First Smartphone, the HTC Droid Eris

No, not that DROID.



Source link