Cisco Jasper vs. Microsoft Azure IoT Central

Using Cisco Jasper is suitable for managing large numbers of cellular subscribers where manual management is impossible. If you are a prototype project with dozens of subscribers, it may not be convenient for you to deal with Cisco Jasper and opt for manual management. The use of Cisco Jasper is justified in a production and project monetization environment.

Incentivized

Microsoft Azure IoT Central has native integrations with Visual Studio (like pretty much all Microsoft products) making it pretty simple to publish apps to Azure App Service, where you can host all sorts of different applications. It does a really good job of storing large amounts of data (for instance, collected from IoT devices with various sensors) and it gets stored to multiple DBs. Azure IoT Central could improve by adding more customizations, as this would make troubleshooting the products easier and make future costs smaller and easier to predict.

Incentivized

• Device integration
• Connectivity management
• Enterprise-grade solution

Incentivized

• Documentation
• Support
• Good and approachable GUI
• Many types of subscription configurations

Incentivized

• Occasionally, it takes a long time for things to load, but that is just a feature.
• There are a few minor glitches, but nothing that affects usage.
• It was assuring security as a vendor-based solution.

• central application
• smartphone app

Incentivized

In our country, the subscriber management platform is not eligible since each cell phone operator opts for a particular brand, that is, we have not had an option, although we have no complaints about the platform, we feel comfortable using it. I know of other management platforms used by other operators and they are really all very well designed, but we all know about CISCO's track record in the market, which adds additional value.

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

• We saved an average of 14% on device connectivity costs
• We have an almost 99% uptime thanks to CJ.

Incentivized

• positive: connected huge number of machines as IoT devices and passed them through entire IoT pipeline until storage in a fairly short time
• negative: we spent some time figuring out some "less-used" services because they aren't documented well

Incentivized