ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog

Whose Agents Run Your Operations? The Managed Agent War

Jaione AmigotSeptember 24, 2026
Premium

Five vendors now sell managed enterprise agent platforms, from AWS Bedrock AgentCore in October 2025 to Google's Gemini Enterprise Agent Platform in April 2026. All of them operate the agents for you, and that is the whole buying decision.

The Short Answer

Every major vendor now sells a managed agent platform: AWS Bedrock AgentCore reached GA on 13 October 2025, Microsoft announced Agent 365 on 18 November 2025, OpenAI launched Frontier on 5 February 2026, Anthropic shipped Claude Managed Agents on 8 April 2026, and Google announced its Gemini Enterprise Agent Platform on 22 April 2026. Each operates the agents for you. With ibl.ai you own all the code and the data, so the agents running your operations stay yours.

When five vendors sell the same category, capability stops being the differentiator. Operating custody starts being it.

Which enterprise agent platforms do OpenAI, Anthropic, Microsoft, Google and AWS actually sell today?

All five ship a named product, and the products are more alike than their marketing suggests.

Vendor Product Announced Who operates the agents
AWS Bedrock AgentCore 13 Oct 2025 (GA) AWS
Microsoft Agent 365 18 Nov 2025 Microsoft
OpenAI Frontier 5 Feb 2026 OpenAI
Anthropic Claude Managed Agents 8 Apr 2026 Anthropic
Google Gemini Enterprise Agent Platform 22 Apr 2026 Google

The feature lists converge almost line for line. AgentCore ships Runtime, Gateway, Memory, Browser, Code Interpreter, Identity and Observability.

Google's platform ships Agent Studio, Agent Runtime, Agent Sandbox, Agent Memory Bank, Agent Identity, Agent Registry and Agent Gateway, with access to more than 200 models through Model Garden.

Microsoft's Agent 365 calls itself a control plane, with an agent registry, risk-based access controls and hooks into Entra, Purview and Defender.

Same primitives, five control planes, none of them yours.

Did the managed agent war start this month, or has it been building since late 2025?

It has been building for roughly a year, and the timeline matters because it changes what the announcements mean.

The first of these platforms reached general availability on 13 October 2025. The most recent of the five landed on 22 April 2026. Anything framed this week as the opening shot is describing a market that is already consolidating.

What is new is the layer above the platform. Both frontier labs moved into the implementation layer in May 2026.

On 4 May 2026 Anthropic joined Blackstone, Hellman & Friedman and Goldman Sachs in an AI-native enterprise services company valued at roughly $1.5 billion, including a $300 million commitment each from Anthropic, Blackstone and Hellman & Friedman.

Goldman is a founding partner with no disclosed commitment.

And OpenAI was reported the same day to be raising $4 billion from 19 investors at a $10 billion pre-money valuation for a separate venture, launched 11 May as the OpenAI Deployment Company, with TPG, Brookfield, Advent and Bain Capital.

The services layer is filling in around them, and two examples in the brief that prompted this post need correcting.

CrowdStrike did not build AI security with HCLTech. On 14 September 2026 the two expanded an existing partnership so that HCLTech delivers CrowdStrike Falcon Guardian inside its own advisory and managed services, using HCLTech's TRiBe framework and VERITY Frontier AI Resilience, a cybersecurity operating model. CrowdStrike supplies the product; HCLTech operates it. That extends a CTEM partnership announced 31 March 2026.

Codos is real, but its numbers are not independently sourced. The company describes a "Virtual CAIO" with on-premise deployment and a16z Speedrun backing. The impact figures circulating with its launch come from the founder's own posts, not from a newsroom or an audited filing, so they are not cited here.

What do managed agent platforms genuinely do well?

A great deal, and pretending otherwise would misread the decision.

They solve agent identity. Giving every agent a cryptographic identity, scoping its permissions and revoking them centrally is unglamorous infrastructure that most organizations should not rebuild.

They solve sandboxed execution. Running model-generated code safely, with resource limits and network isolation, is a security problem with a long tail of failure modes.

They solve observability and evaluation. Tracing a multi-step agent run, clustering failures and scoring changes before they reach production is engineering that takes a dedicated team quarters to get right.

And they solve deployment mechanics. AgentCore added VPC and PrivateLink support at GA, and reached AWS GovCloud (US-West) in May 2026.

None of that is marketing. It is the reason the category exists, and a team evaluating one of these platforms should weigh it honestly.

What can you not get from any managed agent platform?

Three things, and they are structural rather than a matter of vendor goodwill.

The source code. Every platform above is consumed as a service. You configure it, you extend it through supported interfaces, and you cannot read or modify the orchestration layer that decides how your agents behave.

Your data inside your own perimeter, end to end. The closest any of them comes is instructive. Anthropic's Managed Agents now let agents operate inside your own perimeter with self-hosted sandboxes and MCP tunnels, phrasing that comes from a later "What's new" note rather than the 8 April launch announcement.

That is a real improvement. Our reading of the arrangement is that execution runs in your environment while orchestration stays on Anthropic's, which is a precise illustration of the boundary; Anthropic does not describe it in those terms.

Model freedom that survives a change of vendor. Google's platform reaches 200-plus models and AgentCore works with any model in or outside Bedrock, so model choice is genuinely broad. But the platform is not portable: switching the control plane means rebuilding the agents, the evaluations and the integrations on someone else's primitives.

Put together, these decide what you retain if you leave. On a managed platform, you keep your data exports and your prompts. The operating layer stays with the vendor, which is the part that actually runs your processes.

Why is per-seat pricing the wrong shape for agents that run operations?

Because headcount stopped being a proxy for consumption the moment agents started doing the work.

Microsoft publishes Microsoft 365 Copilot at $30.00 per user per month, paid yearly, on top of a qualifying Microsoft 365 license. At 5,000 employees that is $1.8 million a year before a single agent runs, and the bill is identical whether 5,000 people use it daily or 400 do.

The agent platforms themselves have already moved. Anthropic prices Managed Agents at $0.08 per session-hour of active runtime plus standard token rates β€” a meter, not a seat count.

That split is the tell. Per-seat licensing survives where the product is a person's assistant. Where the product is an agent executing a process, every vendor including the per-seat incumbents bills by what runs, because seats describe nothing about the workload.

An agent that reconciles invoices overnight has no seat. Charging for one is a pricing artifact inherited from software humans opened, and above a few hundred users it detaches from cost entirely.

How does ibl.ai let you own the agents that run your operations?

By making the operating layer itself part of what you buy.

With ibl.ai you own all the code and the data.

The full source code transfers under a perpetual license and runs on your infrastructure, so the orchestration layer that decides how your agents behave is one you can read, audit and modify.

The platform is model-agnostic across any LLM β€” Claude, GPT, Gemini, Llama, Command, or your own fine-tune β€” and switching providers does not mean rewriting the platform.

Billing is usage-based with no per-seat pricing, against a budget cap you set. And you can deploy anywhere: your own cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

The practical difference shows up in the exit question. Leaving a managed platform means rebuilding your agents on another vendor's primitives.

Leaving ibl.ai is not an event, because the stack is already yours; the Agentic OS keeps running on your hardware whether or not the relationship continues.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY.

Related reading: how enterprise organizations are deploying autonomous AI agents in 2026 β€” the governance architecture these platforms are competing to supply, and enterprise AI consolidation on what happens as the vendor field narrows.

Sources: AgentCore general availability from AWS and its GovCloud launch from AWS; Agent 365 from the Microsoft 365 blog; Frontier from TechCrunch; Managed Agents, session-hour pricing and self-hosted sandboxes from Anthropic; the Gemini Enterprise Agent Platform from Google Cloud; the joint ventures from CNBC and TechCrunch; the HCLTech partnership from CrowdStrike; Copilot pricing from Microsoft.

Why does owning the AI stack matter?

ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing β€” so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.

  • You own all the code and the data

    Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform β€” the stack itself is yours.

  • Model-agnostic

    Run any LLM β€” Claude, GPT, Gemini, Llama, Command, or your own fine-tune β€” and switch providers without rewriting the platform.

  • No per-seat pricing

    Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.

  • Deploy anywhere

    Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY β€” a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies
Work with our team

Pilots, deployment, and full ownership

Most enterprise engagements are one-time, not subscriptions. You integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the work β€” so the price tracks the scope, not your headcount.

Start here

Pilot

from $15K

fixed scope Β· fixed timeline

A time-boxed proof of value on your real data β€” not a slide deck.

Best for: Teams that want to see ibl.ai working before committing.

  • Deployed on your infrastructure or our cloud
  • 1–2 production agents wired to a slice of your data
  • One integration (LMS / SIS / SSO / data source)
  • Weekly working sessions with our engineers
  • Pilot fee credits toward a full engagement
Scope a pilot
Most common

Integration & Deployment

$25K – $80K

one-time Β· not a subscription

Full deployment integrated with your data and systems. Engineering hours scale with scope.

Best for: Organizations rolling ibl.ai out across a department, campus, or business unit.

  • Platform deployed in your VPC, on-prem, or air-gapped
  • Integrated with your data + identity (SSO / SAML)
  • Multiple custom agents built to your workflows
  • Engineering hours proportional to scope
  • You own the data Β· run any LLM you choose
Plan a deployment
Full ownership

Codebase Transfer + Custom AI Engineering

Custom quote

perpetual license Β· you own the stack

We transfer the full source code. You own and self-host the entire platform β€” outright.

Best for: Organizations and enterprises that benefit from perpetual ownership and sovereignty.

  • Complete source-code transfer + perpetual license
  • Dedicated AI engineering team on your roadmap
  • Custom agents, models, and integrations to spec
  • Air-gapped capable Β· zero vendor lock-in
  • Family-owned, New York–based long-term partner
Talk about ownership
You own the code and data Run any LLM β€” Claude, GPT, Gemini, Llama Family-owned & operated from New York, NY