MCP
Model Context Protocol is becoming the default interoperability layer for tool and service connections.
Platform support:3 of 3 tracked clouds
Microsoft FoundryAmazon BedrockGemini Enterprise Agent Platform
Enterprise AI tooling landscape
Tracking what Azure, AWS, and GCP offer alongside the best open source alternatives.
Updated weekly. Compare the cloud foundations, then the agent, orchestration, governance, and assistant layers.
Categories4
Tools tracked48
Updated2026-06-13
Foundation AI platforms
The base stack behind much of the market. Category pages then break out each vendor's own services versus the open-source and commercial tools teams pair with them.
Microsoft Foundry
Microsoft
11,000+
Broadest model catalog plus agents, governance, and sovereign deployment options.
Amazon Bedrock
AWS
100+
Framework-agnostic model access with strong AWS-native agent and safety integration.
Gemini Enterprise Agent Platform
Google
200+
Model Garden plus Gemini, Agent Development Kit, and enterprise MLOps in one stack.
AI Agent Frameworks
Cloud agent platforms and open source frameworks.
View all →
AI Orchestration
Workflow engines, pipelines, and automation layers.
View all →
AI Governance
Guardrails, safety controls, and policy tooling.
View all →
AI Assistants
Coding copilots, productivity assistants, and platforms.
View all →
What is changing in the enterprise AI market
Teams now evaluate the control plane, delivery layer, governance boundary, and standards layer separately. This tracker follows those seams.
Foundation clouds set the defaults
Microsoft, AWS, and Google define identity, model access, and the first route to production.
Delivery layers compete above the cloud
Agent, orchestration, and assistant layers compete on openness and integration depth.
Governance is a hard adoption gate
Guardrails matter where they touch approvals, auditability, and data handling.
Standards support starts to matter
MCP, A2A, and OpenAPI signal ecosystem fit and tool portability.
Protocol tracking: MCP, A2A, and OpenAPI
Where the major cloud foundations expose protocol alignment for MCP, A2A, and OpenAPI.
A2A
Agent2Agent support matters where teams expect cross-agent handoffs instead of single-vendor agent silos.
Platform support:3 of 3 tracked clouds
Microsoft FoundryAmazon BedrockGemini Enterprise Agent Platform
OpenAPI
OpenAPI still matters as the stable enterprise contract for API exposure, governance review, and gateway alignment.
Platform support:2 of 3 tracked clouds
Microsoft FoundryGemini Enterprise Agent Platform
Compare tools side-by-side
8 curated head-to-head comparisons across agent platforms, guardrails, and assistants — every governance dimension laid out column-by-column.
- Microsoft Foundry Agent Service vs Amazon Bedrock Agents
- Microsoft Foundry Agent Service vs Google Agent Builder & ADK
- Amazon Bedrock Agents vs Google Agent Builder & ADK
Latest update · 2026-06-12
PlatformsMarket EventHigh impact
Amazon Bedrock
Amazon Bedrock
AWS announced Claude Fable 5 on Amazon Bedrock, then updated the notice to say Anthropic asked AWS to revoke access to Claude Fable 5 and Claude Mythos 5 under a US export-control directive.
Source: AWS announces Claude Fable 5, the first generally available Mythos-class model
Frequently asked questions
What does enterpriseai.tools track?
Microsoft Foundry, Amazon Bedrock, and the Gemini Enterprise Agent Platform as the cloud foundation layer, plus the leading agent, orchestration, governance, and assistant tools that enterprises pair with them — each tracked record carries a verifiable source URL.
How often is the data updated?
A weekly source-backed scan refreshes every tracked record. Each per-tool page shows a 'last reviewed' date alongside its governance posture, and the /updates feed surfaces newly verified releases, license changes, certifications, and acquisitions.
Is there a signup, paywall, or data capture?
No. The whole site runs as a static export with no accounts, no analytics, no third-party trackers, and no email capture. The 'Help me evaluate' flow runs entirely in your browser.
Where do the underlying facts come from?
Vendor trust centers, compliance documentation, repository LICENSE files, and primary product docs. Every governance claim on a per-tool page links its source URL directly so claims can be audited.