Need a swift communication provider for your IoT infrastructure? Hire flespi as a middleman for your publish/subscribe operations. Our online public MQTT broker is fast, secure, and free.
Perform and scale better with MQTT 5.0
The number of sensors in the IoT and M2M systems is skyrocketing. The flespi team has been working hard to add the MQTT 5.0 specification support into the broker to enhance the productivity and scalability of your projects. Most MQTT 5.0 features already implemented! Let us know if you need something that we are missing.
Be the boss in the isolated MQTT namespace
Each flespi user operates in an isolated MQTT topics namespace. It's only you who chooses how to name messages topics and what kind of hierarchy to use.
Operate the broker via REST API
Manage sessions, publish messages, read and delete retained messages, and access logs via a flexible REST API.
Fine-tune access to topics
We take security and privacy seriously. To make sure each subscriber gets the data they need but cannot cause harm by their negligence or accidental actions, we devised a flexible access control system. It allows creating tokens with different ACLs to finely customize what different parties can access within a topic.
Use shared subscriptions for easy load-balancing
When incoming messages start heavily bombarding the handler of your business app, you might lose data. We don’t want that! flespi offers shared subscriptions to spread the load across multiple service workers in a smart manner.
Never hit the speed limit
It’ frustrating when your technological partner can’t live up to your needs. We don’t want to be a bottleneck as your business grows. flespi MQTT broker can receive one million messages per second and send three million messages per second. Impressive, huh?
Stay safe with SSL-protected MQTTS and WSS connections
We care about the security of the messages you entrust to our MQTT broker. That’s why we support MQTT over SSL and MQTT over Secure WebSocket. Also, you can create an isolated namespace with any name (except /flespi).
MQTT over TCP: 8883 (SSL) or 1883 (non-SSL)
MQTT over WebSockets: 443 (SSL) or 80 (non-SSL)
|MQTT version||3.1, 3.1.1, 5.0|
|QoS supported||QoS 0, QoS 1, QoS 2|
|REST API||Yes, it's possible to publish messages, read and delete retained messages, manage connected and offline sessions, and access broker logs via MQTT broker REST API|
|ACL||Yes, topics access is adjustable via token ACL setting|
|Shared subscriptions||Yes, implemented according to MQTT 5.0 specification. Allows load-balancing published messages between multiple subscribers in the same shared group|
|Retained messages||Yes, with limited storage according to restrictions|
|Logs||MQTT broker logs available via either REST API or MQTT|
|your flespi token||not used||any|
Login to start managing MQTT sessions for free or register via email Should you need to exceed the above numbers, switch to commercial use
|MQTT 5.0 compliance checklist|
|Shared groups||Load-balancing; delivering messages to a single subscriber from the group|
|Message expiry interval||Limiting the messages TTL (for both queued and retained)|
|Response topic||Subscriber response to received topic (executing commands and getting response)|
|Receive maximum||Client limits the number of inflight messages sent by the broker|
|Maximum packet size||Client limits the max size of messages sent by the broker|
|Topic alias||Replacing a topic name with the 2-byte index (to save traffic)|
|Will delay interval||Delaying the generation of a will message|
|Subscription identifier||Client specifies own index upon subscription; broker specifies according to which subscription the message is sent to the client|