// the take
SagooIOT is a full-stack, Go-based IoT platform (GoFrame backend, Vue3 frontend) covering device management, multi-protocol ingestion, rule-based alerting, and a plugin system for custom protocol handlers. It's aimed at teams building an internal device-management console for industrial, building, or agricultural IoT rather than hobbyists wiring up a single sensor.
Protocol breadth is real, not just a marketing list: TCP, MQTT, UDP, CoAP, HTTP, Modbus, OPC UA, IEC104, JT808 are all wired in, and the plugin system runs on hashicorp/go-plugin so new protocols can be added as separate C/C++/Python/Go processes without touching the core binary. TDengine integration for time-series storage is the right call for device telemetry at scale instead of forcing everything through a relational table. The feature set (thing model, JS-based rule engine, Casbin RBAC, alarm dedup/suppression, code generation) covers a lot of the boilerplate that normally eats weeks on an internal IoT tool, and there are actual *_test.go files next to the business logic, not just a demo scaffold.
It's GPL-3.0, and the README is explicit that shipping a closed-source derivative requires a separate commercial license from the maintainer - a hard blocker for a lot of companies before they even read the code. Getting it running means standing up MySQL/PostgreSQL, Redis, TDengine or InfluxDB, an MQTT broker, and MinIO simultaneously, which undercuts the 'lightweight' framing. Support and the real documentation live in a QQ group and a Chinese-first doc site; the English README is a translation layer over a project whose primary community you can't easily participate in. The architecture also assumes you take the whole stack (GoFrame + Vue3 + Casbin + gToken) as-is - swapping any one piece isn't a designed-in option, and it ships with a default admin/admin123456 credential you have to remember to change.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →