You pay per connection
Each connected device or client counts as one connection. That is the number on your invoice. [Tiers to confirm]
UltraMQ charges per connected device, so the cost of a fleet follows the number of devices. Prices are not published yet [pricing model to confirm]: tell us your connection count and we send you a quote.
Each connected device or client counts as one connection. That is the number on your invoice. [Tiers to confirm]
Model the cost at today’s fleet size and at ten times that before you commit. No surprise line items.
Managed in the EU, in your cloud account or on your own servers, with the same unit. [Per-option terms to confirm]
| Deployment | What you get | Price |
|---|---|---|
| Managed cloud | Serverless or dedicated clusters in EU regions, operated by us [regions and SLA to confirm] | Per connection, on request |
| Your cloud | Deployed into your own cloud account; your data stays there [providers to confirm] | Per connection, on request |
| Self-managed | On your own servers, on-prem or air-gapped, with enterprise support [support tiers to confirm] | Per connection, on request |
| Vendor | Billing unit | Source |
|---|---|---|
| UltraMQ | A fixed price per connection [tiers to confirm] | — |
| EMQX | Varies by offer: session minutes, traffic, rule actions, hours, sessions + TPS, credits | EMQX pricing |
| HiveMQ | Fixed monthly tiers (self-managed); runtime plus messages (Cloud Starter); capacity (Enterprise) | HiveMQ pricing |
Last checked: 19 November 2026
UltraMQ charges a fixed price per connection. Prices are not published yet [to confirm]; send us your connection count and we reply with a quote.
A connection is one MQTT client connected to the broker, such as a device, a gateway or a backend service. [Exact definition to confirm]
The pricing unit is the connection. Whether plans include message or throughput limits is [to confirm]; we answer it in your quote.
Not announced yet [to confirm]. Talk to us about a pilot for your use case.
[To confirm.] Tell us which marketplace you use and we tell you what is possible.
Tell us what you want to connect, where it has to run and what the data should feed. We reply by email.