I think EMQX can be improved, but to be honest, I don't have anything I'd like to see added or changed. In terms of needed improvements, I don't have anything else to add, even small ones or nice-to-haves. There are no improvements needed for EMQX that I haven't mentioned yet, even small ones.
Senior Software Engineer at a tech vendor with 51-200 employees
Real User
Top 10
Apr 30, 2026
I think EMQX can be improved by providing a uniform UI and login feature that we can use in the dashboard. Additionally, it seems to be a single tenant setup. If we are using a multi-tenant structure, we cannot use it without deploying EMQX dashboard for each instance, which is hard to track. A centralized dashboard where we can add multiple clusters in a single place would be easier to monitor. We also do not find any OAuth integration such as Google login, which would be quite helpful.
EMQX is a good MQTT broker but the historian is simple. The historian side of EMQX and MQTT is simple and could be better. It could be more reliable in new versions.
I do not have any suggestions for improvement in EMQX. As I have worked with EMQX, I do not feel much improvement is needed. Whatever is available till now is working great and is very efficient for us. Perhaps I need to explore more to add new features or other functionalities, but as of now, it is great for us.
EMQX is a scalable open-source MQTT broker designed to connect millions of IoT devices reliably. It is known for its high availability and robust performance, making it a go-to choice for enterprises seeking efficient data transmission across IoT ecosystems.EMQX offers advanced features supporting complex IoT use cases and ensures seamless data flow with low latency. It supports a wide range of protocols and is suitable for industrial IoT, smart homes, and automotive sectors. Developers favor...
I think EMQX can be improved, but to be honest, I don't have anything I'd like to see added or changed. In terms of needed improvements, I don't have anything else to add, even small ones or nice-to-haves. There are no improvements needed for EMQX that I haven't mentioned yet, even small ones.
I think EMQX can be improved by providing a uniform UI and login feature that we can use in the dashboard. Additionally, it seems to be a single tenant setup. If we are using a multi-tenant structure, we cannot use it without deploying EMQX dashboard for each instance, which is hard to track. A centralized dashboard where we can add multiple clusters in a single place would be easier to monitor. We also do not find any OAuth integration such as Google login, which would be quite helpful.
EMQX is a good MQTT broker but the historian is simple. The historian side of EMQX and MQTT is simple and could be better. It could be more reliable in new versions.
I do not have any suggestions for improvement in EMQX. As I have worked with EMQX, I do not feel much improvement is needed. Whatever is available till now is working great and is very efficient for us. Perhaps I need to explore more to add new features or other functionalities, but as of now, it is great for us.