The best AI platform for enterprises with a multi-year agent roadmap
Google wins on a generally available agent runtime and governance tools; OpenAI and Anthropic suit buyers tied to other clouds.
We crown Google for an enterprise planning agents across several years because its Agent Runtime is the one managed agent runtime of the three that has reached general availability. OpenAI's Agents API and Anthropic's Claude Managed Agents both carry a beta label. Google's Agent Registry, Agent Gateway and Agent Observability tools are generally available as well. Its model lifecycle page publishes retirement dates for the stable Gemini models it names, and Alphabet's annual report carries an audit opinion.
OpenAI is the better pick when your cloud contract is with AWS or Microsoft Azure and you want the GPT models sold on Amazon Bedrock or directly by Azure, with a direct API that offers European processing to approved customers. Anthropic is the better pick when the same Claude family has to be available through AWS, Google Cloud and Microsoft Foundry.
What an enterprise with a multi-year agent roadmap should weigh
Google's notice on its pre-release Managed Agents API, a product separate from Agent Runtime, says such products are not to be used "for commercial or production purposes." A release label is a term of use as well as a maturity signal, and a program budgeted over several years runs on whatever the label permits. Check the label on the runtime itself, because a vendor's models can be generally available on a channel where its agent product is in preview.
ISG's Buyers Guide for AI Agents recommends prioritizing governance, security and observability controls, along with integration into the enterprise's data infrastructure and existing applications. An agent holds credentials and calls tools on its own, so the security team needs a catalog of what is running and a record of what each agent did before it approves the next one.
Vendors publish two different promises about a model's life: how long it stays available after release, and how much notice comes before retirement. They are separate measures, and a long notice period says nothing about the first. An agent's prompts and tests are tuned to one model version, so each retirement means a re-test of every agent built on it.
All three vendors sell through more than one channel, and the terms change with the channel. Anthropic's retirement notice, for example, covers its own API and Microsoft Foundry and leaves Amazon Bedrock and Google Cloud to set their own schedules. The channel also decides who bills you and where requests are processed, so match it to the cloud commitment and the data location rules you already have.
Federal Reserve guidance on third-party relationships tells banking organizations that due diligence on a supplier's financial condition can draw on audited financial statements, annual reports and SEC filings. The guidance is written for banks, and the same documents serve any risk team that has to sign off on a dependency lasting years. A public audited filing gives that team a record to review without a nondisclosure agreement, and it makes no forecast.
Runtime status, governance, model terms and channels compared
| OpenAI | Anthropic | ||
|---|---|---|---|
| Managed agent runtime | Agent Runtime: generally available since March 4, 2025 under its earlier name, Agent Engine; renamed April 22, 2026 | Agents API: public beta since September 10, 2026 | Claude Managed Agents: public beta since April 8, 2026 |
| Governance controls documented | Agent Registry, Agent Gateway and Agent Observability, each generally available June 18, 2026 | Admin and Audit Log APIs (August 1, 2024); workload identity federation (July 28, 2026); Terraform provider (August 26, 2026); mTLS and X.509 federation generally available (August 29, 2026) | Workload identity federation (May 4, 2026); versioned agent configurations with version pinning and allow, ask or deny permission policies, both in the beta API; session event history |
| Published availability after release | Named stable Gemini models: at least 12 months, with listed retirement dates not moved earlier | Microsoft Foundry: retirement date set 18 months out when a model launches as generally available | Per-model earliest dates; Opus 5.5, released September 22, 2026, retires no sooner than September 22, 2027 |
| Retirement notice | Shorter-availability models: at least 45 days to migrate; Gemini API preview models: at least 2 weeks | Direct API: at least 6 months for generally available models, 3 months for specialized variants; Microsoft Foundry: at least 60 days | At least 60 days on the Claude API, Claude Platform on AWS and Microsoft Foundry; Amazon Bedrock and Google Cloud set their own schedules |
| Channels that sell the models | Gemini Enterprise Agent Platform on Google Cloud; Gemini API | OpenAI API; Amazon Bedrock; Microsoft Foundry | Claude API; Claude Platform on AWS; Amazon Bedrock; Google Cloud; Microsoft Foundry |
| European processing | EU multi-region endpoint keeps ML processing in EU member states; United Kingdom and Switzerland excluded | Europe endpoint (EEA and Switzerland) with approval and a Modified Retention amendment; 10% uplift on eligible models | First-party API inference geography: global or US; Claude Sonnet 5.5 on Google Cloud: Europe multi-region |
| On your own infrastructure | Gemini on Google Distributed Cloud air-gapped: generally available since August 28, 2025; Flash models in preview on connected deployments | Self-hosted sandboxes for tool execution; model inference stays on the OpenAI service | Self-hosted sandboxes for tool execution; inference and orchestration stay with Anthropic |
| Financial reporting item | Alphabet Form 10-K for fiscal 2025 with an Ernst & Young LLP audit opinion | Confidential draft S-1 submitted to the SEC, as reported by StorageNewsletter | Confidential draft S-1 submitted to the SEC, announced June 1, 2026 |
Google: a released runtime with a registry, a gateway and observability
Google's Vertex AI release notes record Agent Engine as generally available, with billing starting the same day. The Gemini Enterprise Agent Platform release notes record its rename to Agent Runtime in April 2026, when Vertex AI took the Agent Platform name. The runtime an enterprise deploys on today is the same released product under a new name.
Three governance tools reached general availability on the same day in June 2026. The release notes describe Agent Registry as "a centralized catalog for discovering and registering agents and Model Context Protocol (MCP) servers" and Agent Gateway as the networking component that secures and governs connectivity for agent interactions. Agent Observability went to general availability beside them. The Registry entry lists its limits at launch: Access Transparency logs and Access Approval are not available for Registry configurations, and data residency detective controls are limited.
Google's model lifecycle page lists stable Gemini models that stay available for at least 12 months after initial release, each with a retirement date, and says the dates "won't be moved to an earlier date than what is listed." The commitment covers the models named in that table. A second group on the same page comes with a shorter commitment, a migration window of at least 45 days, and preview models on the separate Gemini API carry shorter terms of their own.
Requests sent to Google's EU multi-region endpoint keep machine learning processing inside EU member states, according to its data residency page, which excludes the United Kingdom and Switzerland from that endpoint and says global endpoints "don't provide any data residency guarantees." For sites cut off from the public cloud, Google announced general availability of Gemini on Google Distributed Cloud air-gapped, and its Next '26 post on Distributed Cloud puts the latest Gemini Flash models in preview for connected deployments. Both announcements concern Gemini models on that hardware.
Alphabet's annual report on Form 10-K for fiscal 2025 carries an audit opinion from Ernst & Young LLP, which states it has served as the company's auditor since 1999. Google's Best Buy customer story describes virtual assistants and AI-powered self-service on customer calls, built with Gemini Enterprise for Customer Experience.
Google's newer Managed Agents API, a separate product that builds an autonomous agent from configuration, carries a Pre-GA notice. A team that wants that style of agent on Google is choosing a pre-release product there too, and should build on Agent Runtime for anything headed to production.
OpenAI: GPT models on AWS and Azure, with a European route on the direct API
AWS states that OpenAI models and Codex are "now generally available on Amazon Bedrock," and Microsoft lists GPT-6.1 Sol and GPT-6 Luna among the models sold directly by Azure. An enterprise with a spending commitment on either cloud can buy the GPT family under that contract.
OpenAI's changelog records the Agents API release in public beta, and the quickstart requires a beta header on requests. The overview describes an OpenAI-managed API that gives an application the agent software behind Codex, run in OpenAI-hosted sandboxes or in sandboxes you host. Self-hosting moves tool execution onto your infrastructure; the Bedrock comparison page says the managed layer and model inference "still use the OpenAI service." AWS labels its own Bedrock Managed Agents, powered by OpenAI as a preview, so on AWS the models are released and the managed agent product is in preview.
Admin and Audit Log APIs have been part of the OpenAI API since 2024, per the changelog. In July 2026 OpenAI added workload identity federation, which issues short-lived tokens so workloads stop carrying long-lived API keys. An official Terraform provider and general availability of mTLS and X.509 federation followed in August.
On the direct API, OpenAI's deprecations page promises at least six months' notice before a generally available model retires and three months for specialized variants, with shorter notice for previews and exceptions where safety or compliance requires. Buy through Microsoft and the terms change: its Foundry retirement policy gives at least 60 days' notice, with a retirement date set 18 months out when a model launches as generally available. AWS's Bedrock lifecycle page says GPT-6.1 Sol follows OpenAI's first-party lifecycle terms.
OpenAI's data residency documentation lists a Europe endpoint covering the European Economic Area and Switzerland. Using it requires approval for abuse monitoring controls and a signed Modified Retention amendment, and eligible models released on or after March 5, 2026 carry a 10% price uplift. The residency commitment leaves out system data such as account and usage records.
OpenAI has confidentially submitted a draft S-1 to the SEC, StorageNewsletter reported, adding that the full filing "with audited financials, will not be released until OpenAI elects to make it public." A risk team that needs statements asks OpenAI for them directly.
Anthropic: one Claude family across AWS, Google Cloud and Microsoft Foundry
Anthropic says Claude Opus 5.5 is available across AWS, Google Cloud and Microsoft Azure, alongside its own Claude API. On AWS there are two routes. Claude Platform on AWS is Anthropic's API on Anthropic-managed infrastructure with AWS billing and IAM, and Amazon Bedrock is operated by AWS with its own region and retirement tables. Microsoft's hosting comparison names Anthropic as seller and operator of Claude in Foundry, whether the deployment is hosted on Azure or by Anthropic.
Claude Managed Agents launched in public beta, and its overview carries the Beta label and a required beta header. The overview also says the runtime is not eligible for Zero Data Retention or HIPAA business associate coverage, because sessions store history, sandbox state and outputs on Anthropic's servers. That makes it a weaker fit for a team whose agents handle protected health information.
An agent in Managed Agents is a reusable, versioned configuration with its own ID, and a session can pin a version, which gives a team a controlled record of what each agent is. Permission policies return allow, ask or deny for tool calls with reason codes for audit records, and Anthropic notes the built-in policies do not cover custom tools. Both features are part of the beta API. The release notes add workload identity federation, and the event stream keeps session history that the Console shows as transcripts and tool calls.
Anthropic's deprecations page promises at least 60 days' notice before retiring a publicly released model with active deployments, on the Claude API, Claude Platform on AWS and Microsoft Foundry. Amazon Bedrock and Google Cloud set their own schedules. Individual models get a tentative earliest date: Opus 5.5, released September 22, 2026, is listed to retire no sooner than September 22, 2027.
Google Cloud lists Claude Sonnet 5.5 as generally available with Europe multi-region processing. AWS's Bedrock region table marks the same model as Global only in its listed US and EU regions, and Anthropic's own data residency page offers global or US inference geography on the first-party API. A European enterprise picks the channel by the processing location it needs for the model it has chosen.
Notion integrated Claude Managed Agents to run long-running agent sessions, product manager Eric Liu says in Anthropic's customer story. Anthropic announced that it had confidentially submitted a draft S-1 to the SEC, a submission that is not a public registration statement.
Which AI platform is best for an enterprise with a multi-year agent roadmap?
We crown Google because the product an agent program depends on most, the managed runtime, is a released product there and a beta at the other two. The catalog, the traffic control point and the monitoring around that runtime are released as well, which gives a security team documented controls to approve against. Google's lifecycle page lets you put a retirement date beside each listed Gemini model in the plan, and Alphabet's annual report answers a financial due diligence request from a public filing.
Google's released tools come with a documented gap: Access Transparency logs and Access Approval are not available for Agent Registry configurations. If your access policy requires those two controls, ask Google to demonstrate whether the deployment you propose meets it before you sign. The Registry limits do not change the release status of Agent Runtime, and we weigh that status more, because at OpenAI and Anthropic the beta label is on the runtime itself.
OpenAI is the better pick when procurement runs through AWS or Azure and the team wants the GPT family on that contract. AWS states the models are generally available on Bedrock, and Microsoft sells them directly through Azure. The direct API adds a European endpoint for approved customers. Plan the agent layer with care: the managed runtime is in beta on the direct API and in preview on Bedrock, and retirement notice differs between the direct API and Foundry.
Anthropic is the better pick when one model family has to serve business units on different clouds. Claude is sold through AWS, Google Cloud and Microsoft Foundry and on Anthropic's own API, so a group standardized on Claude can buy it under each of those contracts. Check the regions and the retirement schedule for your model on each channel before you commit, because they are set channel by channel.
Other AI platform providers in this category
| Provider | Website |
|---|---|
| Microsoft | microsoft.com |
| Amazon Web Services | aws.amazon.com |
| Mistral AI | mistral.ai |
| Cohere | cohere.com |
| IBM | ibm.com |
| Oracle | oracle.com |
| Databricks | databricks.com |
| NVIDIA | nvidia.com |