Cloud Renames Contribute
RenamedData & BIGoogle Cloud

BigLake Google Cloud Lakehouse

Open-format Apache Iceberg storage engine and unified table management across clouds and engines.

Naming timeline

  1. BigLake

    · Google Cloud Data Summit 2022

    Unified storage engine for data lakes and warehouses launched in Preview in April 2022.

  2. Google Cloud LakehouseCurrent name

    · Google Cloud Next '26

    Rebranded from BigLake to Google Cloud Lakehouse (Lakehouse) on April 20, 2026 around open-format Apache Iceberg storage and table management.

What is BigLake called now?

BigLake is now called Google Cloud Lakehouse, with the latest change on 20 April 2026 (Google Cloud Next '26). Open-format Apache Iceberg storage engine and unified table management across clouds and engines. Only the customer-facing name changed; the underlying technical identifiers remain backward compatible.

Also known as

  • Lakehouse for Apache Iceberg
  • 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.

REST / gRPC APIsbiglake.googleapis.com
gcloud / CLI Commandsgcloud biglake
IAM Predefined Rolesroles/biglake.*
Terraform Resourcesgoogle_biglake_*

API display name is Lakehouse API; endpoint, CLI, IAM, and Terraform identifiers remain biglake.

Notes & disambiguation

  • As of April 20, 2026, BigLake is officially called Google Cloud Lakehouse (or simply Lakehouse) in the documentation and Google Cloud console.
  • API display name in Cloud Console is 'Lakehouse API', though the endpoint (biglake.googleapis.com), CLI (gcloud biglake), client libraries, IAM roles (roles/biglake.*), and Terraform resources (google_biglake_*) remain unchanged and still reference BigLake.

Sources & official documentation

Catalog last updated . Spotted an error? Suggest an edit