Softwr

Databases · head to head

Dremio vs Sigma Computing

Dremio logo

Dremio

Databases

SQL query engine and lakehouse layer over Iceberg tables in object storage

From
Free
Free plan
Yes
Sigma Computing logo

Sigma Computing

Spreadsheets

Spreadsheet-style analytics that queries a cloud data warehouse directly with no extract layer

From
On request
Free plan
No

The short version

  • Dremio starts at $0.2/mo; Sigma Computing prices on request.
  • Only Dremio lists arrow-based execution; only Sigma Computing lists spreadsheet interface over SQL.
  • Where Dremio falls short: Dremio Cloud is AWS-first, which leaves Azure and Google Cloud customers on the self-managed path with the operational burden that entails.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which Dremio and Sigma Computing actually diverge.

Attributes where Dremio and Sigma Computing differ
AttributeDremioSigma Computing
Starting priceFreeOn request
Pricing modelPer Dremio Compute Unit consumedQuote
Free tierYesNo
PlatformsLinux, Self-hosted, WebWeb
CategoryDatabasesSpreadsheets

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Dremio

  • Arrow-based execution
  • Reflections
  • Semantic layer
  • Iceberg catalogue
  • Federated queries
  • Autonomous management
  • Fine-grained access control
  • BI connectors

Only in Sigma Computing

  • Spreadsheet interface over SQL
  • No extract layer
  • Input tables and write-back
  • Workbooks
  • Embedded analytics
  • Version control and dbt awareness

What people use each for

The jobs each tool is most often brought in to do.

Dremio

  • A company with petabytes of Parquet in S3 that wants BI dashboards without duplicating it into a warehousenot Sigma Computing
  • A data platform team standardising on Apache Iceberg and needing a SQL engine plus catalogue that does not lock the tables innot Sigma Computing
  • An analytics group accelerating slow lake queries with Reflections instead of hand-built aggregate tablesnot Sigma Computing
  • A regulated enterprise that must keep data on premises but wants a modern lakehouse SQL layernot Sigma Computing

Sigma Computing

  • A finance or operations team that lives in spreadsheets and needs warehouse-scale data without exporting CSVsnot Dremio
  • An organisation that has consolidated on Snowflake or Databricks and wants one governed access layer rather than several desktop toolsnot Dremio
  • Planning and scenario work where users need to type assumptions back into governed tables rather than into a local filenot Dremio
  • Embedding customer-facing analytics into a product where each tenant must only see their own rowsnot Dremio

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Dremio

  • Reflections consume compute and storage to build and refresh continuously, so a team that enables them widely discovers that background maintenance rather than user queries drives the DCU bill
  • Self-managing Dremio on Kubernetes requires real platform engineering capacity for tuning executors, memory and coordinator sizing, and it is not comparable in effort to running a managed warehouse
  • The Community Edition lacks the security and governance features most enterprises require, so the free tier is a trial path rather than a viable production option for regulated buyers
  • Dremio Cloud is AWS-first, which leaves Azure and Google Cloud customers on the self-managed path with the operational burden that entails
  • Query performance without Reflections on raw, poorly laid out files is often unremarkable, so the promise of querying the lake as is depends on file layout work you still have to do

Sigma Computing

  • Every user interaction is a live warehouse query, so compute costs rise with adoption and land on the warehouse invoice rather than the BI line item, which routinely surprises the team that approved the purchase
  • It cannot work without a supported cloud data warehouse, so an organisation running analytics on an on-premises database or a plain application database has nothing to connect to
  • Pricing is not published and seats are differentiated by capability, so budgeting requires a sales cycle and a headcount forecast before you can compare it with a tool you could simply buy
  • Performance is only as good as the warehouse behind it, which means slow or badly modelled tables surface as a slow interface and the fix is a data engineering project, not a Sigma setting
  • Statistical and scientific visualisation is limited compared with dedicated tools, so anything beyond standard business charting has to be done elsewhere and brought back in

Pricing, plan by plan

Dremio

Free
  • Community EditionFree
    • Self-managed on your own hardware
    • SQL engine and semantic layer
    • No vendor support
  • Dremio Cloud$0.2/hour
    • Billed at $0.20 per Dremio Compute Unit
    • Includes query execution, Reflections and background processing
    • 400 dollar trial credit for 30 days
  • EnterpriseOn request
    • Self-managed on Kubernetes, on premises or any cloud
    • Enterprise security, SSO and governance
    • Vendor support with SLA

Sigma Computing

On request
  • Sigma ComputingOn request
    • Quoted per organisation
    • Seat types are differentiated by whether a user views, explores or authors
    • Warehouse compute is billed separately by your cloud data warehouse vendor

Which should you pick?

Choose Dremio if

  • You need arrow-based execution.
  • You want to start without paying.
  • You work on Linux, Self-hosted, Web.
  • You also want reflections.

Choose Sigma Computing if

  • You need spreadsheet interface over sql.
  • You also want no extract layer.

Questions people ask

Is Dremio or Sigma Computing better?
Neither clearly leads. Dremio starts at Free and Sigma Computing at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dremio or Sigma Computing?
Dremio has a free tier; the other does not. Paid plans start at Free for Dremio and On request for Sigma Computing.
Does Dremio or Sigma Computing run on more platforms?
Dremio runs on Linux, Self-hosted, Web. Sigma Computing runs on Web.
Can I use Dremio for free?
Yes. Dremio has a free tier, so you can try it without paying. Sigma Computing starts at On request.
What is Dremio best used for?
Dremio is most often used for a company with petabytes of parquet in s3 that wants bi dashboards without duplicating it into a warehouse, a data platform team standardising on apache iceberg and needing a sql engine plus catalogue that does not lock the tables in, an analytics group accelerating slow lake queries with reflections instead of hand-built aggregate tables, a regulated enterprise that must keep data on premises but wants a modern lakehouse sql layer. Of those, a company with petabytes of parquet in s3 that wants bi dashboards without duplicating it into a warehouse and a data platform team standardising on apache iceberg and needing a sql engine plus catalogue that does not lock the tables in are not what Sigma Computing is typically brought in for.
What can Dremio do that Sigma Computing cannot?
Dremio covers Arrow-based execution, Reflections, Semantic layer, Iceberg catalogue. Sigma Computing covers Spreadsheet interface over SQL, No extract layer, Input tables and write-back, Workbooks.

Answered from the vendors’ own pages

Dremio: How is Dremio Cloud billed?

At 0.20 US dollars per Dremio Compute Unit, which counts query execution, Reflection building and platform overhead, not just user queries.

Sigma Computing: Does Sigma store a copy of my data?

No. Queries are executed on your warehouse and results are returned for display, which is why there is no extract refresh to manage.

Dremio: Is there a free version?

Yes, a Community Edition you self-manage, but it omits the enterprise security and governance features and comes with no support.

Sigma Computing: What does it actually cost?

The vendor does not publish prices. Expect an annual contract priced by seat type, plus a warehouse compute increase you should model separately.

Dremio: Does it lock in my data?

No, tables stay in Apache Iceberg or Parquet in your own object storage and can be read by Spark, Trino or other engines.

Sigma Computing: Can business users break the warehouse?

They can run expensive queries. Warehouse sizing, query limits and materialised tables are the controls, and they need configuring before a wide rollout.

Dremio: Do I still need a warehouse?

Often not for analytics, but Dremio is not a transactional store and high-concurrency operational serving is not its strength.

Sigma Computing: Is it a replacement for a modelling layer like dbt?

No. Sigma works best on top of modelled tables and is usually deployed alongside dbt rather than instead of it.

Share

Related pages

Other head to heads