Cost grows in ways you cannot model
Bills mix connection-minutes, messages, traffic and rule actions. Forecasting next year’s cost becomes a spreadsheet project.
UltraMQ is an MQTT broker for device makers and fleet operators. It connects vehicles, chargers and devices across regions and charges one price per connection, so you can model the cost before you scale.
Bills mix connection-minutes, messages, traffic and rule actions. Forecasting next year’s cost becomes a spreadsheet project.
When the broker is down, cars, chargers and devices go dark in front of your customers, not just your team.
Managed is faster to start, self-hosted gives control. Switching later is expensive if the platform locks you in.
Teams moving off a cloud provider’s IoT service need a migration path that does not touch every device at once.
You pay for connected devices, with no surprise line items. Model the cost before you scale. [Pricing model to confirm]
Run close to your devices in several regions. [Regions to confirm]
Devices publish telemetry and receive commands over the same MQTT connection, with topic-level permissions. [Security features to confirm]
Move from another broker or a hyperscaler IoT service step by step, running both in parallel. [Migration guides to confirm]
Start managed, move into your own cloud account or onto your own servers later, with the same broker. [BYOC providers to confirm]
Devices speak plain MQTT, so firmware does not depend on a proprietary SDK. [Supported MQTT versions to confirm]
Values in [brackets] are not confirmed yet.
Each device opens one MQTT connection over TLS to the nearest region.
CONNECT
fleet/ev-0042
[TLS details to confirm]Devices publish telemetry such as state of charge, location or errors.
PUBLISH
fleet/ev-0042/socYour backend subscribes to the fleet and streams data to storage and analytics.
SUBSCRIBE
fleet/+/socYour backend sends commands to one device or a group of devices.
COMMAND
cmd/ev-0042/limit-power| Role | Their question | What we work through with you |
|---|---|---|
| Firmware / backend engineer | How do devices connect? | Client setup, topic design, authentication per device |
| Cloud lead / architect | Will it scale across regions? | Regions, cluster sizing, high availability [limits to confirm] |
| VP Engineering / CTO | What will it cost at 10× the fleet? | Pricing per connection for your fleet size today and planned |
| Security and procurement | Can we sign it? | Hosting location, DPA, SLA [support tiers and SLA to confirm] |
You pay a fixed price for each connected device. Tiers, prices and any message limits are [to confirm]; tell us your fleet size and we send you a quote.
UltraMQ is built for large fleets across several regions. Published connection limits per cluster are [to confirm]; until then, all figures on this site are illustrative.
Yes. MQTT is an open standard, so devices can move by changing endpoint and credentials. The usual path is to run both brokers in parallel and move devices in groups [migration guides to confirm].
Both. UltraMQ runs as a managed service in EU regions, in your own cloud account, or on your own servers [details to confirm].
Not announced yet. [Free tier to confirm.] Talk to us about a pilot for your fleet.
Tell us what you want to connect, where it has to run and what the data should feed. We reply by email.