Firmware usually speaks MQTT over TCP or TLS; browsers need WebSockets. ConnectMQ listens on all four, so devices, services and dashboards share the same topics.
No card required
mqtt://broker.connectmq.comTCPmqtts://broker.connectmq.comTCP + TLSws://broker.connectmq.comBrowsers (HTTP pages)wss://broker.connectmq.comBrowsers (HTTPS pages)Shown: the public shared endpoint. Your private broker’s connection details are in your dashboard.
ConnectMQ implements the MQTT specification, not a proprietary dialect — so your existing client libraries, firmware and tools keep working.
Use 8883 (MQTT over TLS) for devices and services, and 8084 (secure WebSockets, path /mqtt) for browser apps. 1883 and 8083 are unencrypted and meant for quick tests only.
Yes. ConnectMQ exposes MQTT over secure WebSockets (wss), which is what browser MQTT clients such as MQTT.js use.
No. ConnectMQ speaks standard MQTT 3.1.1 and MQTT 5, so any MQTT client library works.
Create an account, get your broker credentials and connect your first device — no servers to install, patch or scale.
