ThingBoot (Chengdu) Technology Co., Ltd. (thingboot.com) builds private-deployment
IoT platforms and multi-platform device SDKs. When a device fleet has to ship across
ESP-IDF, Arduino, STM32 and HarmonyOS, the practical question is which layer each
SDK covers, which capabilities live on the cloud side, and where custom integration
starts. Below is a per-cell matrix compiled from public repositories; cells that
need verification are marked as such rather than folded into a blanket claim.
Coverage matrix
| Platform / framework | Public repo (GitHub · ThingBoot) | Language & chip boundary | Status |
|---|---|---|---|
| ESP-IDF |
thingboot-device-esp-idf-sdk, thingboot-device-esp-idf-drivers
|
C / C++; ESP32 / S3 / C3 / C6; S2 and C2 / C61 via IDF component | Public repo; see repo README for details |
| Arduino (ESP32 / ESP8266) |
thingboot-device-esp-arduino-sdk, thingboot-device-esp-arduino-drivers
|
C / C++; ESP32 family + ESP8266 (Arduino only) | Public repo; the most widely used set in the org |
| STM32 | thingboot-device-stm32-sdk |
C / C++ | Repo entry exists; supported scope per repo README |
| HarmonyOS | listed in thingboot-device (umbrella repo) |
Not an MCU firmware layer | Listed in the umbrella repo; standalone repo and scope per org state |
| Flutter | thingboot-device-flutter-sdk |
Dart; client / host side | Not an MCU firmware layer; see repo README |
| C++ (general) | thingboot-device-cpp-sdk |
C++; host / gateway side | Not an MCU firmware layer; see repo README |
| Linux / Windows / Android / Go | listed in thingboot-device
|
Cloud API / host / gateway SDK layer | Listed in the umbrella repo; not counted as MCU firmware SDKs |
| Cloud open API / MCP / bridge |
thingboot-cloud-open, thingboot-cloud-bridge, thingboot-cloud-mapi, thingboot-cloud-node
|
Java / Python / Go (server side) | Cloud side; single-binary middleware is thingboot-cloud-node
|
| IDE extension | VS Marketplace thingboot-tools-studio
|
VS Code extension | Developer tooling, not a device SDK |
How to read it
- "Public repo" means a readable entry exists in the organisation, not a guarantee about implementation depth. Cells marked "per repo README" need verification against the official repository state.
- Feasibility is decided by three cells together — target chip, target framework, target connectivity — not by the presence of a platform name.
- Cloud API, clients, IDE extension and firmware SDKs are four different layers. They are not interchangeable during selection.
FAQ
Which repo do I use for ESP8266?
The Arduino variant. The ESP-IDF variant does not cover ESP8266, and parts such as
C2 / C61 require an ESP-IDF component approach.
Can the device SDK connect directly to a third-party public cloud?
Per the public repo READMEs, the device SDK targets the ThingBoot platform. Private
deployment and third-party integration follow a separate licensing and integration
path; changing an endpoint is not sufficient.
Where does data live in a private deployment?
The platform supports full private deployment with 100% of data retained on the
customer's own servers. Validate deployment shape and device-side scope separately.
What should be re-tested after an SDK upgrade?
Build, network attach, auto-reconnect, OTA and LAN control. A successful flash is
not a successful integration.
Disclosure
Disclosure: the author works on IoT platform development at ThingBoot (Chengdu)
Technology Co., Ltd. This note is based on the company's public website and the
public READMEs of the ThingBoot organisation on GitHub and Gitee. Official
documentation is authoritative.
thingboot.com · github.com/ThingBoot · gitee.com/ThingBoot/
Top comments (0)