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

Side by side, read 10 Nov 2026

**The short answer.** DualBird and Onehouse are set out here in the same rows: published speed and cost results, code changes and migration, table upkeep, Spark versions and table formats, and where each runs. Each cell carries its source and read date, and the Compute Bill line for each is in the table.

## The same rows for both

| Row | DualBird | Onehouse |
| --- | --- | --- |
| Kind | FPGA Spark plugin for AWS F2 | Managed lakehouse in your cloud account |
| Does well | DualBird says onboarding is two changes: switch the EC2 instance type to F2 and add the DualBird Spark plugin, with Spark still handling planning and scheduling (read 2026-11-10). DualBird published a 100 GB sort-based Iceberg compaction run on June 11, 2026, run by DualBird, and states about $2 per TB for itself against about $6 per TB for CPU clusters. | 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 | DualBird is not a lakehouse. It speeds up Spark on EMR and EKS; a team on a fully managed platform cannot add it. It documents no Spark version list and no table-format support list; Iceberg appears only in its own compaction benchmark. A price for the plugin and a benchmark run by a party other than DualBird: 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 | The home page body text states the headline claim as 10x-30x faster data processing with 50%-90% lower costs and no changes required. The same wording appears in the page's JSON-LD organization description and in the April 28, 2026 blog post. The raw HTML of the home page has a different range in its meta description and og:description (and twitter:description): 10x-100x faster. This is the meta tag, not body text. The February 5, 2026 funding blog post also says 10-100x faster and 50-90% cost savings. The body text of the home and product pages says 10x-30x, so the two ranges differ by site location. The product page repeats the 10x-30x end-to-end figure labeled 'Instance for instance' and 50%-90% cost reduction labeled 'Workload for workload'. The meta description of the product page is only 'Plug-and-play Spark acceleration.' Home and product pages show a '110GB Enrichment Pipeline (JOIN Denormalization)' benchmark: 50%-85% lower EC2 cost with 6x-18x higher performance ceiling. The pages give no hardware, baseline, dates or method, and no link to a write-up was found. Sort-based Iceberg compaction on 100 GB, compared with vanilla Spark and with an unnamed 'C++ accelerated Spark' (unnamed) with tuned EBS, memory and parallelism at each cluster size. Dataset is synthetic: about 370 million rows, 64 mixed-type columns, ZSTD level 3. Results: roughly 12-20x faster single-task execution, 55-85% lower EC2 cost, stable cost across scaling, about 6x higher practical performance ceiling. Cost per terabyte compacted is stated as about $2/TB for DualBird versus about $6/TB rising past $13/TB for CPU clusters. Part of the saving is attributed to F2 local NVMe replacing EBS volumes. The home page shows 'X15-X20' single-task speedup for the same benchmark, while the June 11, 2026 blog and the white paper landing page say 12-20x. The two do not match. The 'Single Task Performance' home-page tile says X15-X20 speedup for the same cluster size while reducing cost by over 50%. The blog describes the single-task comparison as against vanilla Spark, and the April 28 post as against 'a high-end C++ columnar engine running on a single CPU core'. The baseline wording is therefore not consistent across pages. | 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 | No pricing, price list or marketplace listing was found on the site. Cost claims are only percentages (50%-90% lower, 55%-85% lower EC2) and the about $2/TB versus $6-13/TB compaction figure. The pricing model for the plugin itself is not stated, so users cannot tell whether F2 instance price or license fee is included in the claimed savings. | 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 | Onboarding is two changes: switch the EC2 instance type to F2 and add the DualBird Spark plugin. The page shows three steps: change instance type, use our Spark plugin, see the results. The about page says 'No infrastructure changes. No code changes.' The compaction blog says Spark still handles planning, scheduling and fault tolerance and no pipeline rewrite or platform migration is needed. A DualBird engineer states the FPGA path accelerates a defined set of operators (sort, join, aggregation and others). Workloads dominated by Python UDFs or unsupported operators fall back to CPU and do not see the same benefit yet. Coverage is described as expanding. | 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 | DualBird claims tens of Spark settings (executor sizing, CPU-memory ratios, parallelism) become irrelevant, disk spills effectively disappear and data skew stops causing spills, because only a few tasks run at once on the FPGA. The product page says the majority of common Spark performance configurations do not exist when using the solution. Cluster sizing reduces to the number of F2 nodes. These are vendor claims, not independently tested. Part 2 of the series (Sep 1, 2026) says skew still costs time, but less, and that it does not need repartitioning or salting. | 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 home page says the plugin is compatible with Apache Spark, Amazon EMR and Amazon EKS. It lists 'Optimized out of the box', 'Migration-free' and 'No more performance tuning and troubleshooting'. No Spark version numbers, Databricks support or Iceberg/Delta/Hudi support list are stated on the home, product, about or resources pages. Iceberg appears only in the compaction benchmark and in the meta description of the Dec 1, 2025 demo post ('Accelerate Apache Spark and Apache Iceberg'). | 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 | DualBird needs AWS EC2 F2 instances. AWS describes F2 as second-generation FPGA instances with up to 8 AMD Virtex UltraScale+ HBM VU47P FPGAs, 16 GiB HBM per FPGA, 3rd-gen AMD EPYC (Milan) CPUs up to 192 vCPU, up to 2 TiB memory and up to 7.6 TiB NVMe. Sizes: f2.6xlarge (1 FPGA, 24 vCPU, 256 GiB), f2.12xlarge (2 FPGAs, 48 vCPU, 512 GiB), f2.48xlarge (8 FPGAs, 192 vCPU, 2,048 GiB). The AWS 'instance types by Region' doc lists F2 in eight regions: us-east-1 (N. Virginia), us-west-2 (Oregon), ap-northeast-1 (Tokyo), ap-northeast-2 (Seoul), ap-southeast-2 (Sydney), ca-central-1 (Canada Central), eu-central-1 (Frankfurt) and eu-west-2 (London). F2 is not listed in other regions on that page (for example us-east-2, eu-west-1). DualBird is AWS-only: no other cloud is mentioned. The product page says deployment runs on the customer's own servers in their AWS environment and 'Everything stays under your control'. | 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 | The white paper (dated July 1, 2026) has a landing page that restates the results and says methodology, system architecture and detailed analysis are in a download. The full document is gated behind a form and was not readable. The blog gives dataset shape and baselines but not instance counts, Spark version, configs or scripts. No public repo was found (github.com/dualbird returns 404). | 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 | DualBird on Amazon EMR (F2 instances): $49.50 | 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

- DualBird: dualbird.io: https://dualbird.io/ (read 10 Nov 2026)
- DualBird: dualbird.io/product: https://dualbird.io/product (read 10 Nov 2026)
- DualBird: dualbird.io/resources/blog/a-simpler-spark: https://dualbird.io/resources/blog/a-simpler-spark (read 10 Nov 2026)
- DualBird: dualbird.io/resources/blog/iceberg-compaction-benchmark-faster-spark-low: https://dualbird.io/resources/blog/iceberg-compaction-benchmark-faster-spark-lower-cost (read 10 Nov 2026)
- DualBird: dualbird.io/resources/blog/spark-iceberg-compaction-benchmark-whitepaper: https://dualbird.io/resources/blog/spark-iceberg-compaction-benchmark-whitepaper (read 10 Nov 2026)
- DualBird: aws.amazon.com/ec2/instance-types/f2: https://aws.amazon.com/ec2/instance-types/f2/ (read 10 Nov 2026)
- DualBird: docs.aws.amazon.com/ec2/latest/instancetypes/ec2-instance-regions.html: https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-instance-regions.html (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/dualbird-vs-onehouse/
