HiveMQ Cloud Starter

What do you like best about the product?

The biggest thing I like about HiveMQ is that it just works reliably for our setup. We use it for handling communication between devices and our backend, and I haven't had many issues with dropped connections or messages. The monitoring is probably one of the features I use the most because it gives a quick idea of what is happening with the broker. I also found the initial setup and integration fairly straightforward.

What do you dislike about the product?

There is a bit of learning curve if you want to go beyond the basic setup. Some of the configuration options are quite detailed, and it took me a while to understand which ones we actually needed. The documentation helps, but I still sometimes have to search around before finding the exact answer. For smaller projects, the overall cost can also feel a little high.

What problems is the product solving and how is that benefiting you?

We were mainly looking for a reliable way to handle MQTT communication as our number of devices increased. Earlier, managing connections and keeping track of message flow was becoming more difficult. HiveMQ gives us a central place to handle that communication, and it has made the whole setup easier to maintain. WHen we add new devices, we don't have rethink the messaging setup every time, which saves quite a bit of effort.

What do you like best about the product?

The navigation is very well thought out - Explore, Connect, Contextualize, Analyze make it easier to know where to go on each stage. Ask Bea bar with suggestion prompts is helpful instead of starting with a blank search. Getting started cards make onboarding simpler. The platform also has a stable performance without any lags and errors.

What do you dislike about the product?

Some advance features under Contextualize and Analyze aren't very intuitive for new users. They end up leaning on Bea or docs more then you would like. Pricing and licensing info is also not easy to find inside the platform. Aside from this, i haven't come across any other major issues.

What problems is the product solving and how is that benefiting you?

We use it for the messaging backbone between connected devices that need to talk in real time. Before, this meant stitching tools ourselves. HiveMQ gives one platform to connect, monitor and act on data without building infrastructure from scratch, saving time on deployment and catching issues early.

What do you like best about the product?

HiveMQ has worked quite well for us so far. We mainly use it for handling messages between our connected devices and backend, and it has been reliable even when the number of messages goes up. I also like that I can keep an eye on connections and activity from the monitoring side, which helps when we need to troubleshoot something. Getting it connected with our existing setup was also relatively easy.

What do you dislike about the product?

The platform has a lot of configuration options, so it can take a while to understand everything properly. I had to go through the documentation a few times when working on some of the less common settings. Nothing major, but it can slow things down when you are trying to find a specific configuration. The cost is also something smaller teams may need to think about.

What problems is the product solving and how is that benefiting you?

We needed a better way to manage communication between a growing number of IoT devices and our backend. As more devices were added, keeping the connections and message flow reliable was becoming more difficult. HiveMQ has taken care of that messaging layer for us, so the system is easier to manage and we don't have to worry as much about connection issues when the number of devices increases.

What do you like best about the product?

I mostly like HiveMQ because it has been quite stable for our day to day work. We use it for communication between devices and our backend, and it handles a good amount of traffic without creating many issues. The monitoring part is also useful because I can quickly check the connections and see if something is going wrong. Integration with our existing systems was also not too difficult.

What do you dislike about the product?

The main issue for me was getting used to some of the advanced settings. There are a lot of options and the documentation is good, but sometimes I had to spend more time finding the exact information I needed. The pricing can also be a little difficult to justify for smaller projects.

What problems is the product solving and how is that benefiting you?

We mainly use HiveMQ to keep communication between our IoP devices and backend services reliable. Earlier, handling increasing device connections and message traffic was becoming harder to manage. With HiveMQ, the communication has been more stable and it has also made scaling the setup easier as we add more devices.

What do you like best about the product?

Honestly, the best thing about HiveMQ is its performance and rock-solid stability. It scales effortlessly as you add more connected devices, and the UI is very friendly even if you aren't high-level expert. Setting up secure device communication was way faster than expected, and we rarely have to worry about lost messages. It's a huge time-saver for our team.

What do you dislike about the product?

Honestly, nothing major. The dashboard UX could use a few small UI tweaks to make managing individual connected devices slightly more intuitive, but it doesn't affect the overall performance at all.

What problems is the product solving and how is that benefiting you?

HiveMQ solves the headache of managing complex, high-volume device streams. Instead of custom-building a fragile messaging setup that breaks every time we add new devices, HiveMQ acts as rock-solid central hub that routes data smoothly between our hardware and cloud apps.
It speeds up our development process significantly. We can bring new devices online in minutes without worrying about custom integration code, allowing us to focus on building features rather than managing infrastructure.

What do you like best about the product?

The best part about HiveMQ is its exceptional reliability and scalability for handling MQTT messages. Integrating it with java based systems was incredibly straightforward for my messaging projects. the control centre dashboard is very intuitive, making it easy to monitor active client connections and message traffic in real time. It effortlessly handles high throughput without dropping connections, which is a huge plus.

What do you dislike about the product?

While the platform is highly robust, the initial setup and configuration can be a bit overwhelming for someone just starting out. the documentation is very detailed but could definitely use more simplified, quick start examples for complex cluster setups. Also, the enterprise pricing can feel a bit steep for smaller scale applications.

What problems is the product solving and how is that benefiting you?

I am using it to ensure seamless and low latency communication between connected devices. It completely solves the problem of the message loss during unreliable network conditions thanks to its QoS features. The biggest benefit for me is the stability it provides, knowing that the broker can scale up automatically if the number of connected clients suddenly spikes

What do you like best about the product?

One of the things I like most about HiveMQ is how dependable it has been in our daily operations. It handles large volumes of MQTT messages without affecting performance, and onboarding new customer sites has been smooth. The integration with Apache Kafka fits well into our existing workflow, and the pricing is reasonable compared to similar enterprise solutions. The support team has also been helpful whenever we had questions, and the AI features have reduced the time we spend on routine monitoring tasks.

What do you dislike about the product?

Overall, our experience has been very positive. We haven't faced any major issues, and the platform has been easy for both experienced and new team members to use. If I had to mention one improvement, I would like to see more flexibility in dashboards and built-in analytics, but this hasn't affected our day-to-day work

What problems is the product solving and how is that benefiting you?

We use HiveMQ as the messaging platform for our IoT devices to ensure reliable communication between connected devices and our backend systems. It has improved scalability, simplified device management, and helped us process real-time data more efficiently.

What do you like best about the product?

One of the things I like most about HiveMQ is how dependable it has been in our daily operations. It handles large volumes of MQTT messages without affecting performance, and onboarding new customer sites has been smooth. The integration with Apache Kafka fits well into our existing workflow, and the pricing is reasonable compared to similar enterprise solutions. The support team has also been helpful whenever we had questions, and the AI features have reduced the time we spend on routine monitoring tasks.

What do you dislike about the product?

One of the things I like most about HiveMQ is how dependable it has been in our daily operations. It handles large volumes of MQTT messages without affecting performance, and onboarding new customer sites has been smooth. The integration with Apache Kafka fits well into our existing workflow, and the pricing is reasonable compared to similar enterprise solutions. The support team has also been helpful whenever we had questions, and the AI features have reduced the time we spend on routine monitoring tasks.

What problems is the product solving and how is that benefiting you?

We use HiveMQ as the messaging platform for our IoT devices to ensure reliable communication between connected devices and our backend systems. It has improved scalability, simplified device management, and helped us process real-time data more efficiently.

What do you like best about the product?

Most of my work involves connecting field devices with cloud applications so having a dependable messaging platform is essential. I've been using HiveMQ as the communication layer between IoT devices and cloud services. It has handled a growing number of client connections without affecting performance, and the MQTT implementation has been reliable for both telemetry and command messages. The platform also integrates well with cloud environments, which simplified our overall architecture.

What do you dislike about the product?

The documentation is comprehensive, but it can take time to find information for more advanced deployment scenarios. I would also like more built-in operational dashboards instead of relying on external monitoring tools for some metrics.

What problems is the product solving and how is that benefiting you?

As our IoT environment expanded, managing reliable communication between devices and cloud services became more challenging. HiveMQ gave us a stable messaging backbone that could support increasing traffic without requiring major architectural changes. Since deployment, we've spent less time troubleshooting communication issues and more time building new integrations for connected devices.

What do you like best about the product?

It's really all about scalability for us. We were running load test for new over the air update feature and i was honestly waiting for whole thing to crash. But HiveMQ just kept chugging along without breaking sweat. Clustering is phenomenal and we just spun up another node and it joined the party seamlessly. It handled backpressure from our downstream service gracefully too.

What do you dislike about the product?

Complexity of security setup is what i keep tripping over. We wanted to implement pretty strict X.509 client certificate authentication but getting mapping and validation rule right was pain. Documentation covers it, but it's bit scattered.

What problems is the product solving and how is that benefiting you?

Biggest benefit for us is being able to guarantee message delivery in highly volatile network environment. QoS level in HiveMQ ensures we don't lose critical error code or software version data. We used to have to reconcile log from different gateway, which was very difficult. Now it's just clean ordered stream of data we can actually build real time dashboard that our manufacturing lead rely on.