# Dremio and Onehouse: the published facts in the same rows

Side by side, read 10 Nov 2026

**The short answer.** Dremio (Lakehouse with its own SQL engine) and Onehouse (Managed lakehouse in your cloud account) are set out here in the same rows: published speed and cost results, code changes, table upkeep, table formats and where each runs. On the Compute Bill's reference job: Dremio Cloud (Large engine): $102.40; Onehouse (Quanton, bring-your-own-cloud): no total (see the Compute Bill for why).

## The same rows for both

| Row | Dremio | Onehouse |
| --- | --- | --- |
| Kind | Lakehouse with its own SQL engine | Managed lakehouse in your cloud account |
| Does well | Per Dremio documentation, Iceberg tables in the Open Catalog get automatic optimization: data file compaction, row-level delete handling, clustering, partition evolution and manifest rewriting (read 2026-11-10). Dremio publishes DCU rates by engine size, from 16 DCUs per hour for 2XSmall to 2048 for 3XLarge, with a 60-second minimum (read 2026-11-10). | Per Onehouse documentation, its jobs are fully compatible with Apache Spark and EMR code can be reused unless it uses AWS-specific features (read 2026-11-10). Onehouse published the setup for its 10 TB TPC-DS and 1 TB LakeLoader comparison against EMR 7.12, and open-sourced LakeLoader under Apache-2.0 (read 2026-11-10). |
| Limited | Per Dremio documentation, queries run on its own columnar engine, not on Spark, and the pages read describe no mode that runs existing Spark jobs. Dremio Cloud documentation lists Iceberg and Delta Lake as table formats; Hudi support: none found on 2026-11-10. | Per Onehouse documentation, billing is in OCUs on a bring-your-own-cloud model, and no dollar rate per OCU was found on 2026-11-10. Onehouse's results against EMR 7.12 are its own and shown as charts; a confirmation by another party: none found on 2026-11-10. |
| Published speed results | Dremio's founder reported a full 1 TB TPC-DS run (all 99 queries) in 22 seconds on an 8-node m7gd.4xlarge cluster, with no caching, and attributes it to Autonomous Reflections and automatic Iceberg clustering. This is a BI query benchmark run by the vendor, not a Spark batch ETL or compaction test. | Onehouse benchmarked Quanton against open-source Spark on Iceberg: TPC-DS up to about 3.1x, TPCx-BB 2x, TPC-DI (1 TB) 2x with 3-4x on MERGE INTO, and LakeLoader 4.1x for writes. The baseline is open-source Spark, not EMR. Onehouse reran its benchmarks against EMR 7.12 after AWS announced it: it reports EMR improved 32% over earlier versions and that Onehouse 'still comes out with a 2.5x better price/performance advantage'. Setup: 10 TB TPC-DS for read/transform, 1 TB LakeLoader merges for load, latest general-purpose Graviton instances. Results are shown as charts; Onehouse also reports Hudi and Delta query performance on EMR 7.12 was very similar to Iceberg. A B2B SaaS customer (unnamed) ran its UDF-heavy pipeline on EMR and on Quanton in its own AWS account on m8gd nodes. Quanton was faster at p50, p97 and p99 tenant sizes; on the largest tenant (21 billion rows) EMR filled local disks on 180 nodes and was aborted after 3.7 hours, and finished on 300 nodes. The write-up is published by Onehouse. |
| Published prices and cost results | Dremio Cloud is priced at $0.20 per DCU (Dremio Compute Unit). Dremio Enterprise (self-managed) pricing is 'contact sales'. The free trial for Dremio Cloud is a $400 credit for 30 days. DCUs are consumed only while engines run. Usage equals engine and replica uptime in seconds (60-second minimum) times the DCU rate for the engine size. Published rates per hour: 2XSmall 16, XSmall 32, Small 64, Medium 128, Large 256, XLarge 512, 2XLarge 1024, 3XLarge 2048. Storage billed in TB-months only for Dremio-hosted storage; LLM tokens billed separately. Billable usage is DCUs (compute), LLM tokens (AI features) and storage. Compute is billed in DCUs only while engines are running. | Onehouse bills in Onehouse Compute Units (OCU) on a bring-your-own-cloud model: 1 OCU is a 4-core instance for 1 hour in your account, plus support costs; no separate volume or storage fee, and the customer pays its own AWS or GCP infrastructure bill. The docs page does not state a dollar rate per OCU. Vendor claims at the Quanton launch: 2-3x better price-performance for ETL, and a guaranteed greater-than-50% cost reduction for existing Hudi users moving Spark jobs from AWS EMR or open-source Spark. These are guarantees stated by the vendor, not results from an independent party. |
| Code changes and migration | Dremio runs queries on its own columnar execution engine built on Apache Arrow, not on Spark. Docs describe Spark and Flink only as external engines that can use the Open Catalog (Iceberg REST) alongside Dremio. The pages read describe no mode that runs existing Spark jobs, so Spark ETL would stay on Spark or be rewritten as Dremio SQL. | Onehouse docs say its Jobs are fully compatible with Apache Spark and that EMR code can be reused unless it uses AWS-specific features. Migration work listed: map EMR steps to Onehouse Jobs created through its API or Airflow operators (CREATE CLUSTER, CREATE JOB, RUN JOB, DELETE CLUSTER), and configure Glue catalog sync or contact support to make Glue the primary catalog. At the May 20, 2025 launch Onehouse said users can run existing Spark and SQL jobs on new cluster types and that existing Hudi/Spark jobs can be pointed at Onehouse 'with no code changes'. The Quanton Kubernetes Operator is described as a 'drop-in replacement' for an existing Spark Kubernetes operator. |
| Tuning and table upkeep | For Iceberg tables in the Open Catalog, Dremio runs automatic optimization on a dedicated engine it configures: data file compaction, row-level delete handling (position deletes on v2, deletion vectors on v3), clustering, partition evolution and manifest rewriting. The same operations can be run by hand with OPTIMIZE TABLE. Optimization works in batches sized to engine resources. Engines have settings the admin chooses: size (executors per replica), min and max replicas, last-replica auto-stop (default 2 hours), enqueued time limit (default 5 minutes) and query runtime limit. Default concurrency per replica ranges from 2 (2XSmall) to 20 (3XLarge). | Each cluster needs min and max OCU limits. Docs warn that if usage reaches Max OCU the cluster stops scaling up, which can delay processing; Min OCU keeps a cluster warm. The Onehouse docs pages read give no per-job Spark tuning list; Onehouse claims automatic scaling and automated async table services. |
| Spark versions and table formats | The Dremio Cloud data formats page lists Apache Iceberg and Delta Lake as table formats (plus Parquet and text formats). Hudi is not listed on that page. The Open Catalog is built on Apache Polaris and supports the Iceberg REST Catalog API; the docs list AWS Glue Data Catalog as a connectable catalog. | Quanton runs Spark and SQL jobs that read and write Hudi, Iceberg and Delta Lake. Docs: Iceberg 1.10.0 is installed automatically when a job uses an Iceberg REST Catalog (AWS Glue and Snowflake Open Catalog are documented); for Delta Lake the user installs Delta Spark as a dependency in the JAR or Python job. In the Nov 12, 2025 Iceberg post Onehouse said Delta acceleration is 'up next'. Apache XTable (formerly OneTable) translates table metadata between Hudi, Delta Lake and Iceberg without being a new format. It is incubating at the Apache Software Foundation; Onehouse says it created Hudi and XTable. |
| Where it runs | Dremio Cloud runs on AWS (Azure listed as coming soon). Supported regions: us-east-1, us-east-2, us-west-2, eu-west-1 and eu-central-1. Dremio Enterprise can be deployed on Kubernetes, on premises, or in AWS, Azure or GCP. | Onehouse runs EC2 or Google Compute Engine instances inside the customer's AWS or GCP account (Azure not listed in the billing docs). Standard instance types map to Graviton m8g sizes on AWS (oh-general-4 = m8g.xlarge, oh-general-8 = m8g.2xlarge, oh-general-16 = m8g.4xlarge). A project is scoped to one region and account; adding a region needs a support ticket. |
| How open its benchmarks are | Dremio published a 2020 TPC-DS methodology post (SF1000 and SF10000, Parquet on S3, Apache JMeter test plans, 58 of 99 queries that ran unmodified on Dremio and Presto distributions). The 2025 22-second TPC-DS post pages read give cluster type but no scripts, scale-factor files or configuration repository. | Onehouse open-sourced LakeLoader, a tool that generates incremental update/insert loads for benchmarking write performance. The repository is Apache-2.0 licensed, last pushed 2026-10-30. The Quanton engine itself and the full Iceberg benchmark configurations were not found as a repository in the pages read. |
| Compute Bill | Dremio Cloud (Large engine): $102.40 | Onehouse (Quanton, bring-your-own-cloud): no total (see the Compute Bill for why) |

Alphabetical order. Vendor statements are the vendor's own. Read 10 Nov 2026.

## How to read this page

The rows hold what each vendor or a named third party published, with no conclusion drawn. Benchmarks in the two columns ran on different hardware, data and baselines, so their numbers are not comparable across columns. The [Compute Bill method](/compute-bill/method/) explains the cost lines.

## Sources

- Dremio: dremio.com/pricing: https://www.dremio.com/pricing (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/admin/engines: https://docs.dremio.com/dremio-cloud/admin/engines/ (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/admin/subscription/usage: https://docs.dremio.com/dremio-cloud/admin/subscription/usage (read 10 Nov 2026)
- Dremio: docs.dremio.com/current/what-is-dremio/architecture: https://docs.dremio.com/current/what-is-dremio/architecture (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/developer/data-formats: https://docs.dremio.com/dremio-cloud/developer/data-formats/ (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/manage-govern/optimization: https://docs.dremio.com/dremio-cloud/manage-govern/optimization (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/about/regions: https://docs.dremio.com/dremio-cloud/about/regions (read 10 Nov 2026)
- Dremio: dremio.com/blog/breakthrough-announcement-dremio-is-the: https://www.dremio.com/blog/breakthrough-announcement-dremio-is-the-fastest-lakehouse-20x-faster-on-tpc-ds/ (read 10 Nov 2026)
- Dremio: dremio.com/blog/dremio-benchmarking-methodology: https://www.dremio.com/blog/dremio-benchmarking-methodology/ (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/jobs/emr-migration: https://docs.onehouse.ai/product/jobs/emr-migration (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/announcing-spark-and-sql-on-the-onehouse-compute-runtim: https://www.onehouse.ai/blog/announcing-spark-and-sql-on-the-onehouse-compute-runtime-with-quanton (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/project-settings/usage-and-billing: https://docs.onehouse.ai/product/project-settings/usage-and-billing (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/jobs: https://docs.onehouse.ai/product/jobs/ (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): xtable.apache.org: https://xtable.apache.org/ (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/compute/create-cluster: https://docs.onehouse.ai/product/compute/create-cluster (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/apache-iceberg-on-quanton-3x-faster-apache-spark-worklo: https://www.onehouse.ai/blog/apache-iceberg-on-quanton-3x-faster-apache-spark-workloads (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/onehouse-quanton-vs-the-latest-aws-emr-for-apache-spark: https://www.onehouse.ai/blog/onehouse-quanton-vs-the-latest-aws-emr-for-apache-spark-workloads (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/emr-migration-to-quanton-spark-udf-jobs: https://www.onehouse.ai/blog/emr-migration-to-quanton-spark-udf-jobs (read 10 Nov 2026)
- Onehouse (Onehouse Compute Runtime with the Quanton engine): api.github.com/repos/onehouseinc/lake-loader: https://api.github.com/repos/onehouseinc/lake-loader (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalakehousecompare.com/compare/dremio-vs-onehouse/
