AIToday
AI Business & IndustrySnowflake AI BlogPublished: Jul 30, 2026, 22:01 JST

Snowflake and Google Cloud unite data platforms for AI with open standards

Snowflake and Google Cloud unite data platforms for AI with open standards

3 Key Points

  1. What happened

    Snowflake and Google Cloud announced an integrated architecture using Apache Iceberg (an open table format) and catalog federation to let multiple data engines—BigQuery, Spark, Trino, Snowflake, and others—read and write directly to the same data without copying it. Snowflake's Horizon Catalog and Google Cloud's Lakehouse Runtime Catalog can now coexist and share data through standardized REST API endpoints (Iceberg REST Catalog protocol), enabling bidirectional federation so each platform accesses the other's tables with governed, time-limited credentials.

  2. Why it matters

    Organizations no longer face a choice between flexibility (letting teams use different tools but duplicating data) and consistency (forcing one engine but losing specialization). The open-format approach applies the Data Locality principle—moving code to data rather than moving massive data volumes across the network—which reduces costs, redundancy, and security risks. For AI specifically, the combination of semantic models (like Semantic View Autopilot) and contextual metadata (Horizon Context, Knowledge Catalog) lets AI agents query data with business logic baked in, reducing hallucination and enabling accurate, governed answers.

  3. What to watch

    Snowflake's Semantic Studio (in private preview) allows teams to version-control and review semantic models like code via Git integration, while Snowflake CoWork is positioned as a personal work agent for knowledge workers. Google Cloud's Universal Semantic Layer now integrates BigQuery Graph and Snowflake Semantic Views for in-database analytics models. The architecture's success depends on adoption of the Iceberg REST Catalog standard across multi-vendor environments.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The announcement reflects a fundamental shift in how enterprises approach multi-engine analytics. For years, organizations faced a binary choice: replicate data across systems and accept redundancy and drift, or lock teams into a single engine and lose the ability to pick specialized tools. The Apache Iceberg standard, combined with standardized catalog protocols, eliminates that trade-off by keeping data in one place and bringing compute to it—a principle known as Data Locality.

The catalog layer is the governance linchpin. Without a shared authority managing table metadata, access policies, and concurrent writes, open formats alone create ungoverned data. Snowflake's Horizon Catalog and Google Cloud's Lakehouse Runtime Catalog each provide managed, serverless catalog services that expose their tables via the Iceberg REST Catalog (IRC) standard, allowing engines built by competitors to access each other's tables with fine-grained, time-limited credentials. This two-way federation is the technical enabler of what the industry calls an "open lakehouse."

For AI specifically, the architecture bridges three critical gaps: programmatic access (via Model Context Protocol and REST APIs so agents can query data like human analysts), semantic grounding (embedding business logic in semantic models so AI inherits correct definitions), and contextual intelligence (layering table descriptions, data quality signals, and usage patterns so agents interpret data correctly). Snowflake's Semantic View Autopilot and Google Cloud's Knowledge Catalog automate much of this work, reducing the manual overhead of maintaining semantic models at scale. The result is not just interoperability for its own sake, but a platform designed from the ground up to let AI agents operate with high accuracy, governance, and trust.

FAQ
What is Apache Iceberg and why does it matter here?
Apache Iceberg is an open table format developed at Netflix and donated to the Apache Software Foundation. It allows multiple engines—Spark, BigQuery, Snowflake, Trino, Flink, and others—to read and write to the same table directly without proprietary adapters, solving the interoperability problem.
How do Snowflake and Google Cloud catalogs work together?
Through catalog federation, Snowflake's Horizon Catalog and Google Cloud's Lakehouse Runtime Catalog can coexist in the same organization. When Google Cloud manages a catalog, Snowflake connects via Catalog-Linked Database (CLD) to discover and sync tables; when Snowflake manages a catalog, Google Cloud services like BigQuery connect through Horizon's Iceberg REST Catalog endpoint. Each catalog issues narrow, time-limited credentials so governance is enforced regardless of which engine initiates a request.
What is Semantic View Autopilot and how does it help AI?
Semantic View Autopilot, part of Horizon Context, automatically discovers and maintains semantic models by learning from query patterns, user behavior, table relationships, and BI tool integrations. This embeds business logic and verified definitions in the data layer so every AI system inherits the same correct logic, reducing hallucination and inconsistency.
Snowflake AI BlogRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleLinkedIn Skips Data Center Expansion, Doubles GPU Efficiency Instead