How do analysts like Gartner and Forrester currently rate the lakehouse market?

Summary

• Independent analyst firms don't score "the lakehouse" as one product category. They evaluate the broader data-platform and cloud-database market, and their assessments are revised each research cycle, so the current view lives in each firm's own latest report.
• For an up-to-date read, go to the source: the current market evaluations published by major independent analyst firms, which you can request from the firms directly or through a vendor licensed to distribute them.
• The evaluation criteria are consistent across firms: workload unification, open formats and interoperability, unified governance, query performance for BI and SQL, native AI and ML support, and total cost of ownership.
• A lakehouse architecture is designed to meet those criteria by keeping one governed copy of data in open formats and running analytics, BI, and AI on it together.
• Use the published criteria as your own checklist, then validate any platform against your workloads rather than a single headline rating.

How do analysts like Gartner and Forrester currently rate the lakehouse market?

Independent analyst firms evaluate the data-platform market continuously, and their assessments are revised on each research cycle, so any "current" rating is the one in a firm's most recent report, not a fixed score. Rather than restate a rating here, the durable answer is to know what these firms actually measure and to read their latest evaluations directly. This page lays out the criteria analysts consistently apply to lakehouse and cloud-data platforms, and how a lakehouse architecture maps to them, so you can read any current report with a clear frame.
For the present positions, consult the firms' own current publications, available from the analyst firms directly or through vendors licensed to share them.

What is a lakehouse?

A lakehouse is a single architecture that combines the low-cost, open storage of a data lake with the management and query capabilities of a data warehouse. It keeps one governed copy of data in open formats and runs SQL analytics, BI, streaming, data science, and AI on that same data, so an organization doesn't maintain a separate system for each workload.

What analysts actually evaluate

Analyst evaluations of data platforms tend to weigh the same dimensions. Treat them as a checklist you can apply yourself.

Evaluation criterion	What it assesses
Workload unification	Whether analytics, BI, ETL, streaming, ML, and AI run on one architecture and one copy of data.
Open formats and interoperability	Support for open table formats and open APIs, and the freedom to use multiple engines and clouds.
Unified governance	Centralized access control, lineage, and policy across all data and workloads.
Query performance	Efficient SQL for BI and analytics run directly on the source data.
AI and ML support	Native support for model development, serving, and AI applications on the same governed data.
Total cost of ownership	Operational cost across compute, storage, and management, including any data duplication.
Scalability	Handling structured, semi-structured, and unstructured data at enterprise scale.

How the Databricks lakehouse maps to these criteria

Databricks was built around the lakehouse architecture, and its design lines up with the criteria above.

• Unification: one platform runs data warehousing, BI, streaming, data science, and AI on the same governed data, so teams don't stitch together separate stacks.
• Open formats: data lives in open table formats such as Delta Lake and Apache Iceberg on low-cost cloud storage, with open APIs and multi-cloud support to avoid lock-in.
• Unified governance: Unity Catalog provides one model for access control, lineage, and policy across every workload, which removes the fragmentation of governing separate systems.
• Query performance and BI: SQL warehouses run BI and analytics directly on lakehouse data, so reporting works on the source rather than an extracted copy.
• AI and ML: model development, serving, and agents are built into the platform and operate on the same governed data.
• Cost and scale: keeping one copy of data in open formats avoids duplicating it across separate warehouses and ML systems, and the platform scales across data types.

These are architectural facts about how the platform is organized, offered so you can check them against the criteria in any current analyst report yourself.

FAQs

Where can I find current analyst ratings of the lakehouse market?

In the analyst firms' own latest reports. Ratings are updated each research cycle, so the current view is whatever appears in the most recent publication, available from the firms directly or from vendors licensed to distribute them.

Do analysts evaluate the lakehouse as its own category?

Usually not as a standalone category. Lakehouse capabilities are assessed within broader data-platform, cloud-database, and analytics evaluations, using criteria like unification, governance, openness, and cost.

What criteria should I weigh when evaluating a lakehouse platform?

Workload unification, open formats and interoperability, unified governance, query performance for BI, native AI and ML support, and total cost of ownership. Validate each against your own workloads.

Is a lakehouse a data warehouse or a data lake?

It is an architecture that unifies both: open, low-cost storage like a data lake with the management and query capabilities of a data warehouse, over one governed copy of data.