Within a 48-hour stretch, three large platform vendors each tried to define a different floor of the enterprise agent stack. AWS used its New York summit to introduce Context, a managed, self-learning knowledge graph designed to give agents governed access to enterprise data without manual curation, paired with Continuum for agent security and expansions to Bedrock AgentCore, Kiro and a DevOps agent. The framing across both AWS's own materials and outside coverage is consistent: agents are only as trustworthy as the data they can reach, and AWS wants that reachability to run through its services.
Databricks pushed at an adjacent layer. Lakehouse//RT, announced at its Data + AI Summit and covered alongside a new transactional/analytical processing approach, claims sub-100ms query latency at high concurrency and up to 16x performance gains over dedicated real-time serving systems, with named customers reporting multi-fold response-time improvements. The strategic argument is consolidation: collapse separate operational and analytical systems so agents and dashboards read from the same governed substrate. These are vendor- and customer-reported figures from a beta product, not independent benchmarks, and should be read as directional architecture signals rather than settled performance facts.
Adobe took the same logic into a very different surface. Its creative agent entered public beta across Premiere, Photoshop, Illustrator, InDesign and Frame.io, and was simultaneously wired into ChatGPT, Claude, Copilot, Gemini and Slack. Adobe's own survey of more than 16,000 creators, cited in its announcement, reports that 75% describe creative AI as integrated or essential to their work while 85% insist final creative decisions should remain human — a useful tell about how vendors are positioning agents as orchestrators of multi-step production rather than as replacements for judgment.
Read together, the three announcements describe a shared pitch: a context and governance layer (AWS), a unified data and serving layer (Databricks), and an embedded action layer inside the tools end users already open (Adobe). For technology and operations leaders, the practical question is less which vendor wins than how many of these layers a given organization wants under one roof — and what that implies for lock-in, integration cost, and the speed at which agents can be deployed against real workflows.
Sources: VentureBeat AI (https://venturebeat.com/data/aws-enters-the-context-layer-race-with-a-graph-that-learns-from-agents-not-manual-curation); cio-dive (https://ciodive.com/news/AWS-continuum-AI-security-claude-mythos/823184); aws.amazon.com (https://aws.amazon.com/blogs/machine-learning/context-intelligence-for-your-data-and-ai-agents-at-scale/); aboutamazon.com (https://www.aboutamazon.com/news/aws/aws-summit-nyc-2026-ai-agents); databricks.com (https://www.databricks.com/company/newsroom/press-releases/databricks-launches-lakehousert-bring-real-time-analytics-directly); siliconangle.com (https://siliconangle.com/2026/06/16/databricks-declares-end-pipelines-unified-platform-operational-analytical-data/); news.adobe.com (https://news.adobe.com/news/2026/06/adobe-unveils-major-expansion); blog.adobe.com (https://blog.adobe.com/en/publish/2026/06/18/more-time-spend-on-your-craft-adobe-brings-power-creative-agent-creative-cloud-apps); 9to5mac.com (https://9to5mac.com/2026/06/18/adobe-expands-firefly-capabilities-extends-agentic-tools-to-creative-cloud-apps/)