"Cross-cloud" Lakehouse "Borderless" Lakehouse
Legacy names "Cross-cloud" Lakehouse, "Multi-cloud" Lakehouse
Official product and architecture terminology for cross-cloud and multi-cloud data lakehouses on Google Cloud.
Naming timeline
- "Cross-cloud" / "Multi-cloud" Lakehouse
Earlier architecture and feature phrasing for cross-cloud analytics and federated catalog access.
- "Borderless" LakehouseCurrent name
Official Lakehouse release notes and documentation replace 'Cross-cloud Lakehouse' with 'borderless Lakehouse' on July 31, 2026.
Is "Cross-cloud" Lakehouse the same as "Borderless" Lakehouse?
"Borderless" Lakehouse is the current official term; "Cross-cloud" Lakehouse refers to the earlier scope or wording of the same offering, with the latest change on 31 July 2026 (July 31, 2026 Lakehouse release notes). Earlier names covered by this entry also include "Multi-cloud" Lakehouse. Official product and architecture terminology for cross-cloud and multi-cloud data lakehouses on Google Cloud. Only the customer-facing name changed; the underlying technical identifiers remain backward compatible.
Also known as
- Borderless Lakehouse
Technical identifiers
Technical identifiers unchanged. Only the customer-facing product name changed; the APIs, CLI commands, IAM roles and Terraform resources below keep their legacy identifiers for backward compatibility.
| Identifiers | N/A (Architecture & documentation style rule) |
|---|
Architecture & feature terminology under Google Cloud Lakehouse (biglake.googleapis.com).
Notes & disambiguation
- In the July 31, 2026 Lakehouse release notes, Google Cloud officially announced: 'Cross-cloud Lakehouse is now called borderless Lakehouse'.
- Does not apply to the networking product Cross-Cloud Interconnect, which retains its name.
Sources & official documentation
Catalog last updated . Spotted an error? Suggest an edit