Best Lakehouse Analytics Platforms (2026): Top 10 Compared
A lakehouse analytics platform runs SQL, BI and AI workloads directly on open table formats such as Apache Iceberg, Delta Lake and Apache Hudi in object storage. The ten platforms here split three ways. Databricks, Microsoft Fabric and Snowflake are broad data platforms with lakehouse storage built in. Dremio, Starburst, Cloudera and IBM watsonx.data are query and lakehouse engines that read open tables across clouds and on premises. Onehouse, e6data and Qlik Open Lakehouse focus on one layer: ingestion and table management, or a compute engine placed under existing tools. Billing ranges from per-unit compute meters to capacity subscriptions and quote-only contracts.
Order is not a ranking. How entries are ordered.
On this page
Compare at a glance
Select a vendor for details and sources. Scroll the table horizontally on smaller screens.
| Vendor | Consider for | Pricing notes | Standout |
|---|---|---|---|
| Databricksenterprise | Teams wanting one platform for data engineering, SQL analytics and ML on Delta Lake | Pay-as-you-go per DBU, no up-front cost; Azure Databricks Premium in East US lists Serverless SQL at $0.70 and Jobs at $0.30 per DBU-hour Checked Oct 2026 | Lakehouse built on the open-source Spark, Delta Lake and MLflow projects |
| Dremiomid-market | Iceberg-first teams wanting a lakehouse query engine with a built-in catalog and semantic layer | Dremio Cloud $0.20 per DCU, pay-as-you-go on AWS, $400 trial credit; Enterprise self-managed by quote; Community Edition free Checked Oct 2026 | Open Catalog built on Apache Polaris and automatic query acceleration on Iceberg |
| Starburstmid-market | Teams wanting managed Trino to query lakehouse tables and other sources in place | Galaxy Free $0 for up to 3 clusters; Pro from $0.50, Enterprise from $0.75, Mission-Critical from $1.00 per credit; annual discounts Checked Oct 2026 | Built on Trino, with federation across lakes and databases |
| Microsoft Fabricenterprise | Microsoft and Power BI organisations wanting a lakehouse inside one SaaS capacity | Shared capacity $0.18 per CU-hour pay-as-you-go in East US, one-minute minimum; reservations save ~41%; OneLake hot storage $0.026/GB/month Checked Oct 2026 | Lakehouse and warehouse share one SQL engine and Delta tables in OneLake |
| Snowflakeenterprise | Snowflake users wanting Iceberg tables on their own cloud storage | Consumption-based credits plus storage; per-credit rate by edition, cloud and region; Iceberg data on external volumes is billed by the cloud provider Checked Oct 2026 | Iceberg tables with Snowflake query semantics, or an external catalog |
| Clouderaenterprise | Hybrid enterprises needing one Iceberg lakehouse across public cloud and data centres | Cloud hourly per CCU: Data Warehouse $0.07, Data Engineering $0.07 Core or $0.20 All-Purpose, Data Hub $0.04; on-premises by annual subscription Checked Oct 2026 | Same open lakehouse on AWS, Azure, Google Cloud and on premises |
| IBM watsonx.dataenterprise | Enterprises wanting a hybrid open lakehouse with several engines for BI and AI | Pay Per Use from $1.00 per resource unit on AWS; Subscription from $83.30/month; core support 3.00 RUs/hour extra; free trial Checked Oct 2026 | Presto, Spark and Milvus engines on one Iceberg, Hive and Delta lakehouse |
| Onehousespecialist | Teams wanting a managed lakehouse in their own VPC readable as Hudi, Iceberg and Delta | Quote-based; pay-as-you-go or a flat yearly fee, no figures published; free trial available Checked Oct 2026 | From the creators of Apache Hudi and Apache XTable, with format interoperability |
| e6dataspecialist | Teams with high-concurrency SQL on open tables who want compute under existing tools | $0.175 per vCPU-hour pay-as-you-go, infrastructure included, no minimum; outcome-based contracts and bring-your-own-cloud licences by quote Checked Oct 2026 | Scales compute one vCPU at a time instead of fixed cluster sizes |
| Qlik Open Lakehousespecialist | Qlik Talend Cloud customers building Iceberg lakehouses on AWS with real-time ingestion | Quote-based; included from the Qlik Talend Cloud Standard plan upward, all plans by contact; compute runs on the buyer's AWS EC2 Checked Oct 2026 | Continuous Iceberg optimisation with change data capture into open tables |
These comparisons draw on public product information, not hands-on testing of every tool. Source records identify available references and checks; missing evidence is marked. Buyer fit is an editorial assessment, not a measured performance score. How to use this research.
Lakehouse analytics platforms let teams run SQL, dashboards and AI on data kept in open table formats in object storage, without first loading it into a proprietary warehouse. Buyers also search for this category as data lakehouse platforms, Iceberg query engines or open lakehouse software.
The ten platforms compared here fall into three groups. Databricks, Microsoft Fabric and Snowflake are broad data platforms that store or read lakehouse tables natively. Dremio, Starburst, Cloudera and IBM watsonx.data are lakehouse and query engines that run across clouds and, in most cases, on premises. Onehouse, e6data and Qlik Open Lakehouse address one layer: managed ingestion and table optimisation, or a compute engine placed under existing tools. All pricing notes were checked in October 2026. Entries with dated source checks appear first. That order records research readiness. It is not a measure of product quality or a ranking.
Related pages cover data warehouse solutions, semantic layer platforms, data catalog software and data orchestration tools.
Vendor details and trade-offs
Databricks describes its platform as a lakehouse. Tables are stored in Delta Lake format in the buyer's cloud object storage, and the same data serves Spark data engineering, Databricks SQL warehouses for BI, streaming jobs and machine learning with MLflow. The vendor's lakehouse page stresses that data stays in open formats under the buyer's control.
Billing is by the Databricks Unit, a normalised unit of processing. Each workload type has its own DBU rate, so jobs compute costs less per DBU than serverless SQL. Microsoft's published Azure Databricks Premium rates in East US show the spread: $0.30 for jobs, $0.55 for all-purpose and SQL Pro, and $0.70 for serverless SQL. On classic compute, the cloud provider also bills the instances.
Databricks also appears on the StatWharf data warehouse page, through Databricks SQL.
Potential strengths
- One toolset covers Python and SQL, notebooks and IDEs, batch and streaming, on AWS, Azure and Google Cloud
- Delta Sharing gives other computing platforms read access to live tables without copying them
Trade-offs
- DBU rates differ by workload type, tier, cloud and region, so estimating a bill takes the price list and a calculator
- On classic compute the cloud provider bills instances separately from the DBU charge, including during the trial
- Product reference
- Product documentation
- Pricing source
- Billing terms: Pay-as-you-go per DBU; committed-use contracts available
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
Dremio is a lakehouse platform built around Apache Iceberg, Apache Arrow and Apache Polaris. Its query engine runs SQL directly on Iceberg tables in object storage, and Reflections accelerate repeated queries without copies in a separate warehouse. Open Catalog, built on Polaris, lets other Iceberg engines read the same tables, and an AI Semantic Layer and AI Agent are listed as core capabilities.
Dremio Cloud is fully managed on AWS at $0.20 per DCU. The DCU measures engine runtime, so a 20-DCU engine running for ten hours consumes 200 DCUs; the vendor states that infrastructure costs are included. Dremio Enterprise is self-managed for buyers with on-premises or strict compliance needs, and is priced by sales.
In May 2026 SAP announced an agreement to acquire Dremio, and Dremio's site now states that it is part of SAP.
Potential strengths
- A published per-DCU rate that includes infrastructure, plus a $400 trial with no credit card
- Self-managed Enterprise runs on Kubernetes on premises or on AWS, Azure or Google Cloud
Trade-offs
- Dremio Cloud runs on AWS only, with Azure listed as coming soon
- SAP agreed to acquire Dremio in May 2026, so buyers should confirm roadmap and contract terms under the new owner
- Product reference
- Pricing source
- Billing terms: Pay-as-you-go per DCU; annual contracts available
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
Starburst sells commercial editions of Trino, the open-source distributed SQL engine. Starburst Galaxy is the fully managed service, which the documentation describes as a data lake analytics platform that handles provisioning, maintenance and security. Starburst Enterprise is the self-managed edition for buyers who run their own infrastructure.
Galaxy prices compute in credits. The credit is the same in every tier, so a two-worker cluster uses 12 credits an hour whether the account is on Pro or Mission-Critical; what changes is the price per credit, from $0.50 to $1.00, and the features and support attached. Pro adds flexible execution modes and streaming ingest. Enterprise adds autoscaling, ABAC and SCIM access controls and PrivateLink. Mission-Critical adds elite support and the highest uptime commitments.
The free tier stays available after the trial, with three clusters for ad hoc queries.
Potential strengths
- A free tier with three clusters that does not expire, and a $500 trial with Enterprise features
- Credits are consumed at the same rate in every tier, which makes tiers easy to compare
Trade-offs
- Fine-grained ABAC, SCIM and AWS PrivateLink start on the Enterprise tier
- AIDA token usage is billed separately from credits on Enterprise and Mission-Critical
- Product reference
- Product documentation
- Pricing source
- Billing terms: Per credit consumed; annual contracts may be discounted
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
Microsoft Fabric is a SaaS analytics suite in which the lakehouse is one item type among several. Microsoft's documentation describes a Fabric lakehouse as combining data lake scale with warehouse querying: data is stored once in OneLake in Delta Lake format, processed with Apache Spark in Python, Scala, SQL or R, and queried with T-SQL and Power BI.
All Fabric workloads draw on one capacity. Azure's retail price list shows $0.18 per capacity-unit hour pay-as-you-go in East US, and reservations save about 41%. Storage is billed separately in OneLake by tier, from $0.026 per GB a month hot down to $0.004 cold. Autoscale Billing for Spark moves Spark onto its own pay-as-you-go meter.
Fabric also appears on the data warehouse page through Fabric Data Warehouse.
Potential strengths
- Built-in integration with Power BI, pipelines and dataflows on the same capacity
- OneLake shortcuts reach external data without duplicating it
Trade-offs
- One capacity is shared by every Fabric workload, so heavy Spark jobs can compete with BI unless capacity is sized or Spark is billed separately
- Multi-table transactions are supported in the Fabric warehouse but not in the lakehouse
- Product reference
- Product documentation
- Pricing source
- Billing terms: Pay-as-you-go per CU-hour or 1- or 3-year reservation
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
Snowflake began as a cloud data warehouse and now supports Apache Iceberg tables as its route into the lakehouse. Its documentation describes Iceberg tables as combining the performance and query semantics of standard Snowflake tables with external cloud storage the buyer manages. They suit existing data lakes that a team cannot, or prefers not to, load into Snowflake storage.
Two storage choices exist. With Snowflake-managed storage, Snowflake stores the files, protects permanent tables with Fail-safe and bills for storage. With an external volume, files sit in the buyer's Amazon S3, Google Cloud Storage or Azure bucket, the cloud provider bills storage and the buyer handles recovery. Snowflake can be the Iceberg catalog, or a catalog integration connects it to an external one.
Compute is billed in credits, with rates set by edition and region. Snowflake also appears on the data warehouse page.
Potential strengths
- Snowflake can act as the Iceberg catalog or connect to an external catalog through a catalog integration
- Snowflake-managed Iceberg storage keeps Fail-safe protection for permanent tables
Trade-offs
- Iceberg tables on an external volume get no Fail-safe, and the buyer is responsible for data protection and recovery
- Per-credit rates appear only after selecting edition, platform and region, which complicates quick comparison
- Product reference
- Product documentation
- Pricing source
- Billing terms: On demand or pre-purchased capacity
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
Cloudera's Open Data Lakehouse is built on Apache Iceberg and aimed at enterprises with data in both public clouds and their own data centres. The product page describes unified security, governance, metadata and lineage across both, with built-in ingestion and pipelines and zero-copy sharing between business units.
Cloudera Data Warehouse provides the SQL layer. Its documentation covers Apache Hive, Apache Impala and Trino in virtual warehouses, plus the Hue editor. Data engineering runs on Spark, and Data Hub manages clusters for Spark, Hive, Impala, Kafka, Flink and other open-source services.
Pricing on cloud is hourly per CCU, with a separate rate for each service, from $0.04 for Data Hub to $0.20 for all-purpose data engineering. Cloudera states that on-premises annual subscriptions are aligned with those rates for hybrid use.
Potential strengths
- Published per-CCU hourly rates for each cloud service
- Several SQL engines in one warehouse service: Hive, Impala and Trino, with the Hue editor
Trade-offs
- Each service carries its own CCU rate, so a full lakehouse bill combines several meters
- On-premises pricing is not published and needs a sales conversation
- Product reference
- Product documentation
- Pricing source
- Billing terms: Hourly per CCU, monthly or prepaid credits; annual subscriptions on premises
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
IBM describes watsonx.data as a hybrid, open data lakehouse for analytics and AI. It reads and writes Apache Iceberg, Hive and Delta Lake tables on Amazon S3 and IBM Cloud Object Storage, and applies consistent access controls, policies and lineage across them.
Instead of a single engine, buyers provision the engines they need. The pricing page lists Presto in C++ and Java versions for SQL, Spark with the Gluten accelerator for data processing, Milvus for vector search and Cassandra for operational data, each sized in resource units an hour.
The managed service on AWS starts at $1.00 per RU pay-as-you-go, metered per second, or $83.30 a month on subscription. A core support charge of 3.00 RUs an hour is added per account. Self-managed software for on-premises use is also offered.
Potential strengths
- Engine sizes are published in resource units an hour, so cost per engine is visible before purchase
- Runs as SaaS on IBM Cloud or AWS, or in the buyer's own on-premises environment
Trade-offs
- The 3.00 RU-an-hour support charge applies on top of engine compute, which raises the floor for small deployments
- Listed prices are indicative and may vary by country
- Product reference
- Pricing source
- Billing terms: Pay per use per RU, or monthly subscription
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
Onehouse was founded by the team behind Apache Hudi and Apache XTable, and sells a lakehouse platform that runs in the buyer's own cloud account or Kubernetes cluster. Data never leaves that account, which lets buyers keep cloud discounts they have already negotiated.
The platform has several parts. Oneflow ingests from cloud storage, database change data capture and streams. Quanton runs Spark and SQL ETL. Table Optimizer handles compaction and maintenance. Open Engines runs managed Trino, Ray and other clusters. Lakegres adds a Postgres-compatible, autoscaling SQL endpoint for interactive and agent-driven queries on Hudi and Iceberg tables. OneSync keeps one copy of data readable as Hudi, Iceberg and Delta in every catalog.
Onehouse states pricing as pay-as-you-go or a flat yearly fee, without published rates.
Potential strengths
- Deploys in the buyer's VPC on any cloud, on managed or on-premises Kubernetes, or on NeoCloud providers such as Nebius and CoreWeave
- Lakegres serves Iceberg and Hudi tables through a Postgres-compatible SQL endpoint with indexing and caching
Trade-offs
- No published price, so cost comparison needs a sales conversation
- Lakegres is documented for Hudi and Iceberg tables; its page does not list Delta Lake
- Product reference
- Product documentation
- Billing terms: Pay-as-you-go or flat yearly fee
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
e6data describes itself as a lakehouse compute engine. Its Query Engine is a Kubernetes-native SQL engine that runs inside the buyer's cloud account and reads Iceberg, Delta Lake, Hudi and Hive tables where they already live. It connects through Python, JDBC, the PostgreSQL protocol and a REST API, and the documentation covers catalog registration, row filters and column masking.
The main distinction is sizing. Instead of fixed cluster sizes, e6data allocates compute in single vCPUs, so cost follows load. The engine sits beneath existing platforms such as Databricks, Snowflake and Trino rather than replacing them, and deploys on AWS, Google Cloud, Azure or on premises.
Pay-as-you-go is $0.175 per vCPU-hour, all infrastructure included. Buyers moving from a warehouse can instead sign an outcome-based contract that guarantees a percentage saving.
Potential strengths
- A published all-inclusive vCPU-hour rate with no minimum commitment
- Reads Iceberg, Delta Lake, Hudi and Hive tables in place and works alongside Databricks, Snowflake and Trino
Trade-offs
- Self-managed installation is listed as coming soon in the documentation
- Answer Engine token pricing is scoped per customer and not published
- Product reference
- Product documentation
- Pricing source
- Billing terms: Pay-as-you-go per vCPU-hour; committed and outcome-based contracts by quote
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
Qlik Open Lakehouse is a feature of Qlik Talend Cloud rather than a standalone product. Qlik's documentation describes it as a fully managed service to ingest, process and optimise data in an Iceberg-based lakehouse, built on AWS EC2 and S3 in the buyer's account.
A data movement gateway captures changes from databases, SAP and mainframes and lands them in S3. Lakehouse clusters, EC2 auto-scaling groups that Qlik manages on Spot Instances by default, process that data into Iceberg tables registered in a catalog such as AWS Glue. The Adaptive Iceberg Optimizer then compacts and cleans the tables continuously.
Querying happens in other engines. Qlik lists Snowflake, Amazon Athena, Apache Spark, Trino and Presto, and offers zero-copy mirroring into Snowflake. Pricing follows the Qlik Talend Cloud plans, from Standard upward, by quote.
Potential strengths
- Batch and real-time ingestion from databases, SaaS apps, SAP, mainframes and streams such as Kafka and Kinesis directly into Iceberg
- Tables can be queried by Snowflake, Amazon Athena, Spark, Trino and Presto, or mirrored into Snowflake without copying
Trade-offs
- Runs on AWS components (EC2 and S3) only, according to the architecture documentation
- Qlik does not provide the SQL query engine itself; analysis runs in a separate engine or in Qlik Cloud Analytics
- Product reference
- Product documentation
- Pricing source
- Billing terms: Qlik Talend Cloud subscription by quote; AWS infrastructure billed by AWS
- Source review: checked Oct 20, 2026
- Vendor confirmation: not confirmed
Frequently asked questions
What is a lakehouse analytics platform?
A lakehouse analytics platform runs warehouse-style SQL, BI and machine learning directly on data stored in open table formats, such as Apache Iceberg, Delta Lake or Apache Hudi, in low-cost object storage. The table format adds transactions, schema evolution and time travel to plain files. One copy of data then serves several engines, instead of being loaded into a separate proprietary warehouse.
What is the difference between a data lakehouse and a data warehouse?
A traditional warehouse stores data in its own managed format and runs its own engine on it. A lakehouse keeps data in open formats in object storage the buyer controls, so several engines can read and write it. The line has blurred: Snowflake now supports Iceberg tables, and Microsoft Fabric's lakehouse and warehouse share one SQL engine on Delta tables in OneLake.
How much do lakehouse analytics platforms cost?
Most bill compute by a vendor-specific unit. Published rates include $0.175 per vCPU-hour for e6data, $0.20 per DCU for Dremio Cloud, $0.50 to $1.00 per Starburst credit, $1.00 per watsonx.data resource unit, $0.18 per Fabric capacity-unit hour and $0.07 per Cloudera CCU for its data warehouse service. Onehouse and Qlik Open Lakehouse are quote-based. Units differ, so the same workload should be tested on each.
Should a team choose Apache Iceberg, Delta Lake or Apache Hudi?
Iceberg has the broadest support on this page: Snowflake, Dremio, Cloudera, Qlik, e6data, Onehouse and watsonx.data all document it. Delta Lake is native to Databricks and Microsoft Fabric. Hudi is supported by Onehouse and e6data. Onehouse's OneSync keeps one copy readable as Hudi, Iceberg and Delta, which reduces the cost of choosing wrongly.
Can a lakehouse run inside the buyer's own cloud account?
Yes. Onehouse deploys in the buyer's VPC or Kubernetes cluster. e6data runs in the buyer's cloud account, with a bring-your-own-cloud licence option. Qlik Open Lakehouse runs clusters on EC2 in the buyer's AWS account. Dremio Enterprise and Starburst Enterprise are self-managed, and Cloudera and watsonx.data also run on premises.
Can a lakehouse engine work alongside an existing warehouse?
Several are positioned that way. e6data states that it works beneath Databricks, Snowflake and Trino. Dremio publishes guidance on offloading dashboard queries from Snowflake, Redshift and Databricks. Qlik Open Lakehouse mirrors Iceberg tables into Snowflake without copying. Starburst federates queries across lakes and databases.
Which platforms suit hybrid cloud and on-premises deployments?
Cloudera states that its cloud hourly rates and on-premises annual subscriptions are aligned for hybrid use. IBM watsonx.data runs as SaaS on IBM Cloud or AWS, or on premises. Dremio Enterprise runs on Kubernetes on premises or in any major cloud. Onehouse supports on-premises Kubernetes, and e6data lists on-premises deployment.
How was this list compiled?
Candidates came from buyer queries for lakehouse analytics platforms and from vendor websites. Each vendor's pricing page and product or documentation page was read on 20 October 2026, and every figure comes from those pages or from Microsoft's Azure retail price list. Warehouse-first vendors already covered on the data warehouse page were limited to three with documented lakehouse features. No product was tested hands-on, and no entry is vendor-confirmed.
Suggest a vendor or correction
Send factual corrections to editorial@statwharf.com. Corrections are free. For inclusion or placement enquiries, contact partnerships.
First published October 2026. Page update dates reflect editorial changes, not a fresh check of every vendor.