[vkuruthers]

Looks pretty good. However, how are you going to differentiate your offering from other more established players out there? (e.g. ThingWorkx, AWS IoT etc.)?

Also usually these types of "no embedded code needed" offerings are OK for demo applications, but what happens when a lot of custom features are needed? E.g. how can one add custom biz. logic to the auto-generated code? If this is not clearly spelled out, then customers are going to be hesitant to get locked into your platform I think.

You can msg. me direct if more info needed, I've worked in the industrial monitoring space for over 15 years now.

[tmckd]

Would very much like to get your further thoughts on this. didn't see a way to reach you in your bio. I am at mac - at - apiotics.com

On the custom feature side, there are two options. We think most web developers will be most comfortable implementing custom logic in their web application, which is straightforward to do.

If you need custom functionality running on the device, then you can write a custom driver for your device (which can include substantial custom logic) and use the portal to load it into your firmware image and install it.

I think our differentiation from others is that we assume the developer starts from the web application and wants to add connected devices to their app. Most other players assume a connected device and give you ways to send data from it to the cloud.

Hopefully that makes some sense.

[vkuruthers]

OK going to msg. you privately with some more details.