You sell the SIM — then the customer asks where their device data should go. Give every enterprise customer a private, isolated MQTT broker on ConnectMQ, with its own endpoint, credentials, topic ACLs and live dashboard, and turn connectivity into a data service.
No card required
PUBLISH devices/359881234567890/telemetry
{"rat":"LTE-M","rsrp":-104,"bat":3.61,"lat":52.3702,"lon":4.8952,"ts":1761120000}QoS 1 · TLS 8883 · PUBACK
IoT SIM and private APN contracts compete on price, while enterprise customers still need somewhere for their trackers, meters and gateways to send data. Building a multi-tenant MQTT platform in-house — clustering, TLS certificates, tenant isolation, upgrades and round-the-clock operations — is a product line few operator teams can staff. System integrators hit the same wall on every project: one more broker to build and run.
When an enterprise signs up for your IoT bundle, create a private ConnectMQ broker for it — Basic or Scale, depending on the fleet — with its own endpoint.
Trackers, meters and gateways on your SIMs connect over MQTT/TLS on port 8883. Small packets and persistent sessions suit LTE-M, NB-IoT and roaming links that come and go.
The customer’s ERP, fleet portal or cloud data pipeline subscribes over TLS or secure WebSockets, with its own credentials and topic permissions.
Your support team checks connected clients, message flow and alerts in each broker’s live dashboard. Billing, SIM lifecycle and APN settings stay in your BSS and connectivity management platform.
Each customer gets a separate broker instance with its own credentials and ACLs — no shared topic tree where one tenant’s mistake exposes another tenant’s data.
Username/password per device or gateway and publish/subscribe rights per topic, so a tracker writes only its own topics and an application reads only what it should.
MQTT 3.1.1 and MQTT 5 with QoS 0/1/2, persistent sessions and Last Will: devices on patchy coverage reconnect without losing queued commands, and drop-outs are visible.
Basic $39 and Scale $199 per broker per month, with no overage charges, so you know the cost behind every customer bundle. Start on the Free plan — no card required — and upgrade to Basic or Scale when a customer goes live.
devices/{imei}/telemetry
devices/{imei}/status (retained)
devices/{imei}/commands
gateways/{gateway-id}/health (retained)Create a private ConnectMQ broker for each enterprise customer and hand over its endpoint and credentials with the SIM bundle. Devices publish over MQTT/TLS, the customer’s applications subscribe, and you don’t run the broker infrastructure. Billing, SIM lifecycle and APN configuration stay in your own BSS and connectivity platform.
The simplest isolation is one broker per tenant. On ConnectMQ each customer has a separate instance with its own credentials and per-topic ACLs, so there is no shared namespace to misconfigure. Inside a broker, ACLs limit every device and application to its own topics.
For most devices, yes: small headers, keep-alive and persistent sessions work well on LTE-M and on NB-IoT modules that hold a TCP/TLS connection. Very constrained devices that sleep for hours sometimes use UDP-based protocols such as MQTT-SN or CoAP through a gateway instead. ConnectMQ speaks standard MQTT over TCP, TLS and WebSockets.
Start on the Free plan — no card required — connect your first devices today and upgrade when you go live.
