Softwr

Databases · head to head

EMQX vs Sigma Computing

EMQX logo

EMQX

Databases

Erlang MQTT broker for large IoT fleets, relicensed to BSL with production free use limited to one node

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

  • EMQX starts at $234/mo; Sigma Computing prices on request.
  • Only EMQX lists erlang clustering; only Sigma Computing lists spreadsheet interface over SQL.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

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

Attributes where EMQX and Sigma Computing differ
AttributeEMQXSigma Computing
Starting priceFreeOn request
Pricing modelPer month by connection and session volumeQuote
Free tierYesNo
PlatformsLinux, Self-hosted, Web, macOSWeb
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 EMQX

  • Erlang clustering
  • MQTT 5.0 and QUIC
  • Rule engine
  • Data integration sinks
  • Session persistence
  • Multi protocol gateways
  • Authentication and authorisation
  • Dashboard and REST API

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.

EMQX

  • A connected vehicle platform needing millions of persistent MQTT sessions with QUIC for handover across mobile networksnot Sigma Computing
  • An industrial operator routing sensor telemetry straight into TimescaleDB or Kafka without writing a consumer servicenot Sigma Computing
  • An IoT product team that has outgrown a single Mosquitto instance and needs clustering and shared subscriptionsnot Sigma Computing
  • A smart building deployment mixing MQTT, CoAP and LwM2M devices on one brokernot Sigma Computing

Sigma Computing

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

Where each one falls short

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

EMQX

  • The move to Business Source Licence 1.1 at version 5.9 in May 2025 limits free production use to a single node, so the clustering that justifies choosing EMQX now requires a paid subscription from the second node onward
  • The relicensing arrived in a minor release, which caught users who had pinned to 5.x expecting Apache 2.0 terms and forced legal review of existing deployments
  • Running an Erlang/OTP cluster well requires operational knowledge most teams do not have, and diagnosing distribution, mnesia or memory issues means learning a runtime you use for nothing else
  • Enterprise pricing is quoted rather than published for the self-managed edition, so the cost of the clustered configuration you actually need is invisible until you talk to sales
  • The Serverless tier caps at around a thousand connections and shares infrastructure, which makes it a prototyping tier rather than a genuine small production option

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

EMQX

Free
  • Open Source single nodeFree
    • BSL 1.1 licence since version 5.9
    • Free production use of one node only
    • All former enterprise features visible
  • ServerlessFree
    • Free monthly quota then pay as you go
    • Up to 1,000 connections
    • 8 by 5 support
  • Dedicated Flex$234/mo
    • Single tenant cluster
    • Traffic allowance included
    • 24/7 support
  • Enterprise self-managedOn request
    • Deploy on premises, at the edge or in any cloud
    • Clustering licensed
    • 256 MB maximum message size

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 EMQX if

  • You need erlang clustering.
  • You want to start without paying.
  • You work on Linux, Self-hosted, Web, macOS.
  • You also want mqtt 5.0 and quic.

Choose Sigma Computing if

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

Questions people ask

Is EMQX or Sigma Computing better?
Neither clearly leads. EMQX 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, EMQX or Sigma Computing?
EMQX has a free tier; the other does not. Paid plans start at Free for EMQX and On request for Sigma Computing.
Does EMQX or Sigma Computing run on more platforms?
EMQX runs on Linux, Self-hosted, Web, macOS. Sigma Computing runs on Web.
Can I use EMQX for free?
Yes. EMQX has a free tier, so you can try it without paying. Sigma Computing starts at On request.
What is EMQX best used for?
EMQX is most often used for a connected vehicle platform needing millions of persistent mqtt sessions with quic for handover across mobile networks, an industrial operator routing sensor telemetry straight into timescaledb or kafka without writing a consumer service, an iot product team that has outgrown a single mosquitto instance and needs clustering and shared subscriptions, a smart building deployment mixing mqtt, coap and lwm2m devices on one broker. Of those, a connected vehicle platform needing millions of persistent mqtt sessions with quic for handover across mobile networks and an industrial operator routing sensor telemetry straight into timescaledb or kafka without writing a consumer service are not what Sigma Computing is typically brought in for.
What can EMQX do that Sigma Computing cannot?
EMQX covers Erlang clustering, MQTT 5.0 and QUIC, Rule engine, Data integration sinks. Sigma Computing covers Spreadsheet interface over SQL, No extract layer, Input tables and write-back, Workbooks.

Answered from the vendors’ own pages

EMQX: Is EMQX still open source?

Not in the OSI sense since version 5.9. It is source-available under Business Source Licence 1.1, reverting to Apache 2.0 four years after each release.

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.

EMQX: Can I run a free cluster?

No. The additional use grant permits free production use of one node; clustering requires a commercial licence.

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.

EMQX: What changed for existing users?

Community and enterprise editions merged, so all features are now visible, but the licence terms tightened in the same minor release.

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.

EMQX: Which version is still Apache 2.0?

Releases before 5.9 remain under Apache 2.0, and each BSL release converts to Apache 2.0 four years after publication.

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