Google Cloud Next '26 dropped a lot of flashy headlines — eighth-gen TPUs, Gemini Enterprise Agent Platform, AI-powered security ops. But the announcement I keep coming back to is quieter, more infrastructural, and arguably more consequential for everyday developers: the **Cross-Cloud Lakehouse.
Opening Keynote replay — the Agentic Data Cloud segment starts around the 45-minute mark. Look for Karthik Narain on stage.
A Little Context
If you watched the Day 1 keynote, you heard Google Cloud CPO Karthik Narain say something that stuck with me:
"Existing data infrastructure was designed as a static repository — information that sits until a human asks it a question."
That framing landed for me immediately. Because it's true. The entire modern data stack — warehouses, lakes, pipelines — was engineered for human-scale, human-paced querying. You run a report. You pull a dashboard. You wait.
But AI agents don't work that way. They need to act, not just answer. And they need to do it across all your data, wherever it lives, in milliseconds — not after a 3-day ETL migration project.
That's the problem the Agentic Data Cloud is trying to solve. And the Cross-Cloud Lakehouse is the most interesting piece of it.
What Is the Cross-Cloud Lakehouse, Actually?
Here's the short version: Google has built a zero-copy data access layer that lets you query data sitting in AWS S3 or Azure Data Lake — without moving it to Google Cloud.
It's standardized on Apache Iceberg (the open table format that's been quietly eating the data world), and it hooks directly into Google's Cross-Cloud Interconnect at the network level. The result? An AI agent running on Google Cloud can treat an S3 bucket as if it were local BigQuery storage — no egress fees, no migrations, no vendor lock-in headaches.
BEFORE: Multi-cloud data reality
──────────────────────────────────
AWS S3 ──┐
Azure ADLS ──┼──► ETL ──► GCS ──► BigQuery
GCS ──┘ (weeks, $ egress)
AFTER: Cross-Cloud Lakehouse
──────────────────────────────────
AWS S3 ──┐
Azure ADLS ──┼──► Lakehouse ──► AI Agents
GCS ──┘ (Iceberg, zero-copy)
Key Takeaway: The Cross-Cloud Lakehouse isn't just a data feature. It's Google's Trojan horse into enterprises already locked into AWS or Azure — competing on openness rather than captivity.
They've also added bi-directional federation with Databricks Unity Catalog, Snowflake Polaris, and AWS Glue — meaning this isn't a Google-flavored silo. It's genuinely trying to be interoperable.
The keynote demo showed partner integrations with Palantir, Salesforce Data360, SAP, ServiceNow, Snowflake, and Workday. That's a lot of enterprise logos for a feature that got maybe 4 minutes of stage time.
Why This Matters for Developers (More Than It Sounds)
Let me explain why I think this is the sleeper announcement of the conference.
1. It Changes the Agent Context Problem
The biggest unsolved problem with deploying AI agents in production is context. An agent that doesn't understand what "gross margin" means at your specific company is a liability, not an asset.
Today, solving that requires months of data engineering:
# The painful reality of enterprise AI data prep (today)
steps_to_make_data_agent_ready = [
"Pull data from 12 different source systems",
"Resolve naming conflicts ('revenue' vs 'net_revenue' vs 'rev_adj')",
"Clean inconsistent schemas and null-handling conventions",
"Build a semantic layer that maps terms to business definitions",
"Write documentation no one will maintain",
"Wait 3–6 months",
"Repeat from step 1 when anything changes",
]
# Time to first useful agent query: ~forever
The Cross-Cloud Lakehouse, combined with the new Knowledge Catalog (Google's evolved Dataplex that auto-enriches data with business context the moment it lands in storage), is designed to collapse that timeline.
The claim: "Zero manual data engineering. The second an image or PDF hits Google Cloud Storage, it's instantly enriched and made agent-ready."
Bold claim. But if it holds up at production scale, it removes one of the most painful bottlenecks in the entire agentic AI pipeline.
2. Apache Iceberg Is a Smart Bet
The decision to standardize on Apache Iceberg is worth calling out explicitly. Iceberg has won the table format wars. Delta Lake and Hudi are fine, but the ecosystem momentum is clearly behind Iceberg — supported natively by Spark, Flink, Trino, DuckDB, Snowflake, and now Google BigQuery.
By building on Iceberg's open REST catalog spec, Google is betting on the open standard rather than a proprietary lock-in play. That's... not always how Google behaves. It's worth acknowledging when they get this right.
3. Spanner Omni Changes the Multi-Cloud Calculus
Quietly bundled alongside the Lakehouse announcement: Spanner Omni — Google's globally consistent distributed database, now deployable on-premises or in rival clouds.
This is significant. Google's most technically impressive database can now run on AWS or Azure. It suggests Google is willing to compete on technical merit rather than platform captivity — a meaningful signal.
My Honest Critique
I don't want to just hype this. There are real questions before any of this becomes a production recommendation.
"⚠️ The things I'm skeptical about"
1. Latency is everything.
Zero-copy cross-cloud access sounds beautiful until you remember "cross-cloud" means packets are traversing expensive private interconnects between AWS, Azure, and GCP. The performance story for latency-sensitive agent workflows hasn't been proven in the wild. The keynote showed demos — not production benchmarks.
2. The "zero manual data engineering" claim is doing heavy lifting.
Every enterprise has messy, inconsistent, undocumented data. The Knowledge Catalog's auto-enrichment via Gemini is impressive in demos. But reliably understanding your company's definition of "active customer" across 15 legacy systems? That still requires human data governance work. This tool accelerates it — it doesn't eliminate it.
3. The pricing model is unclear.
Google announced the feature. They didn't clearly announce what egress, compute, or catalog indexing costs look like at scale. For data-heavy organizations, those numbers will determine whether this is a game-changer or an expensive convenience.
The Bigger Picture: Google's Trojan Horse
Here's what I think Google is actually doing — and it goes beyond the Lakehouse.
Google is betting that enterprise AI value will accrue to whoever owns the reasoning layer over data, not just the storage layer. AWS and Azure charge you for compute and storage. Google wants to charge you for context and intelligence.
The strategic read: Google is repositioning BigQuery and the Knowledge Catalog from "data warehouse" to "reasoning surface" — the place where AI agents go to understand your business, not just query it. That's a different and much larger market.
The Cross-Cloud Lakehouse says: "We don't care where your data lives. Bring your agents to Google, and we'll make them smarter than they can be anywhere else."
Whether that bet pays off depends on whether the technical claims hold up at production scale. The demos looked compelling. The enterprise logos were convincing. The real test comes in the next 6 months when developers start kicking the tires.
For a sharp 13-minute recap of the full keynote strategy:
What To Do Right Now
If you're a developer or data engineer evaluating this:
Watch the Agentic Data Cloud breakout — the full session playlist is on YouTube. Andi Gutmans (Google VP, Data Cloud) goes significantly deeper than the keynote.
Get familiar with the Apache Iceberg REST catalog spec. This is increasingly the lingua franca of multi-cloud data access and will serve you regardless of vendor. The official Iceberg docs are a solid starting point.
Sign up for the Cross-Cloud Lakehouse preview if your org has multi-cloud data. Early access is available through the Google Cloud console.
Benchmark before you commit. Don't trust demos. Run your own workload against BigQuery's cross-cloud federation and measure latency against a local query. That delta tells you everything about whether the product fits your use case.
Final Thought
Google Cloud Next '26 was headlined by AI agents and shiny new chips. Those are real and important. But the story I'll be watching over the next year is whether the Agentic Data Cloud actually delivers on its promise: a data infrastructure that doesn't just store information, but actively makes AI agents smarter.
The Cross-Cloud Lakehouse isn't the most glamorous announcement from Las Vegas. But it might be the one that ages best.