
Tago was the 2nd system I tried. The first system was very weak on testing/rigo around having a working platform. Tago seems pretty solid in terms of uptime and availability. Very good. I love the idea of Tago's openness and the fact that you can integrate anything that can chirp out a JSON is pretty incredible... then provide a united display, linked by time has unlimited possibilities. I love the fact that they have pre-loaded many decoders on the LoraWAN side of things (can't speak to the rest). Right now my primary focus is IOT for agriculture in central Texas. Primarily water management for grazing operations - which shows LoraWANs best attributes off quite well. I do like the fact that they have IOS/Android apps as all customers want this. I like their tiered pricing and while I'm still very much in startup phase, I've been able to win a couple of customers while still refining my business and pay as I go which has been huge. The fact that they don't tie me into specific LoraWAN networks is great too as I run my own servers. Excellent platform. Their documenation is immense and as part of that they have added AI which has sped up use of the service quite a bit. Review collected by and hosted on G2.com.
I'd like to see Tago go back and make their documentation more indepth and current as the docs aren't keeping up w the developments. As well, their AI depends on their docs so you get a less than good circular loop. However, I think they could use AI to improve the docs and if users could disagree w the AI answer and suggest improvements it could self repair. Related to this, if users could put user comments on current docs which are to superficial that would be great. I'd like to see a real consolidation of docs as there are too many sources and they aren't always clear which one is the best. I also think as part of the onboarding, an overall visual map of how things fit together and the places integrators could customize would be helpful. Some of the options seem to conflict with other options and if that could be better highlighted so programmers/integrators don't have to self-discover would be great. It seems some of the widgets could be more custom fit to the applications - for example, there isn't a battery widget ready made with coloring and transmogrification options from voltage ranges to pre-colored items. There are some alerts that should be prepackaged or bound with devices and device data a little tighter for convenience. The alert triggers themselves I think would be super useful with a little more logic on the front end - for example if this signal goes HIGH and this signal is HIGH would be great. Also, if alerts had the ability to always do a quick query on the last value you could observe state changes and that would be really helpful. This is a good tool though and the team continues to work hard, so I tried to provide this list to be helpful and not just a negative criticism, which it is not. Review collected by and hosted on G2.com.



