Microsoft Azure IoT Central vs. OpenRemote

If there is a need for a system to be developed in a short time then Azure IoT Central is the perfect option, offering a fast solution for a simple system that can be used and built upon. This is a great advantage as it skips on some details, also this is a bit of a disadvantage as most times developers want to know what they are working with.

Incentivized

• Creation and management of user roles, who can access your IoT resources and configure the level of access, very granular and self-explanatory
• Configuration of apps and devices, integrations, and administrations are done in an intuitive way and it's easy to navigate your way through the available settings.
• The documentation is really excellent, everything is explained succinctly and there are enough practical examples to get you started.
• Existing templates can save you a lot of time in getting your desired setup complete with less effort and time invested.

Incentivized

• Lack of info on error messages
• GUI misses important configuration options
• Not well documented options inside IoT Hub for example (consumer groups)

Incentivized

Before deciding to go with Microsoft Azure IoT Central, we considered Google, Datadog, and AWS alternatives. The reason we went with Azure was that the client was heavily invested in Microsoft technologies and Azure plays really well with other Microsoft products. The competitive products might be a little bit easier to set up, with more flexible pricing, but, the integrations with other Microsoft services were the deciding factor for our use case.

Incentivized

• Continuous and significant progress
• Integration of the product in the ongoing work and improvement of our system capacity
• Convenient interface

Incentivized