Snowflake, Google Cloud unite on open lakehouse for AI agents

The announcement reflects a fundamental shift in how enterprises handle multi-engine data architectures. Historically, organizations faced a choice: either let each team use its preferred tool and accept data redundancy and inconsistency, or force all teams through a single engine and lose specialization. Apache Iceberg, developed at Netflix and donated to the Apache Software Foundation, solved the first layer of this problem by providing a shared open table format. However, format alone does not ensure governance. The Iceberg REST Catalog standard (an open API specification) became the second pillar, creating a single authority to manage table metadata, enforce access policies, and issue vended credentials that prevent engines from gaining persistent access to underlying storage.

Snowflake and Google Cloud's alignment on this stack is significant because it eliminates the need for custom integrations between their respective catalog systems (Horizon and Lakehouse runtime catalog). Through bidirectional federation, an organization can start with one managed catalog and incrementally add others as needs evolve, all while maintaining unified governance. This is operationally simpler than a DIY self-managed catalog (such as Apache Polaris), which shifts infrastructure and scaling responsibility to the customer's team.

The third layer—making the lakehouse AI-ready—addresses a different problem. Data accessibility does not ensure data usefulness to AI agents. Snowflake's Semantic View Autopilot and Google Cloud's Knowledge Catalog close the gap by automatically discovering and maintaining semantic models (business logic), and by attaching contextual metadata (data quality signals, authoritative source definitions, hierarchies) directly to the data. When an AI agent queries, it receives not just raw data but the institutional knowledge needed to interpret it correctly, which reduces hallucination and aligns answers with business rules.