Our mission

Heapwatch exists so you can see what an ESP32 is doing without sitting next to it with a USB cable: heap, CPU, task stacks, logs, and a decoded crash when the board panics.

A reboot alone does not tell you what happened. Watch history plus a core dump matched to that firmware build gives you the file and line, not a story you invent from serial prints.

Who we build for

People writing ESP-IDF firmware for ESP32-family devices, and small teams doing the same. This is a lab workbench (live boards, soak boards, crash decode), not a production fleet-ops product.

What Heapwatch is not

Heapwatch is not a general-purpose IoT device manager and not Heapwatch Fleet (production device ops). It does not replace AWS IoT, Golioth, or whatever you already use to run a fleet.

Convenient OTA, remote config, and remote files exist on the workbench for development and lab boards. That is not a claim that OTA cannot brick a device, and it is not a factory provisioning system.

How it works

Add the snippet - drop a connector into your ESP-IDF firmware. The device streams memory, CPU, thread, log, and event data over MQTTS using the native ESP-IDF stack.
Watch it run, and catch crashes - live metrics while it is installed. On a panic the device saves a core dump to flash and uploads it on the next boot when the network is up.
Get a decoded stack trace - file, line, and call stack for that build, which you can read yourself or hand to a coding agent.

Get in touch

Questions about Heapwatch or already integrating it? info@heapwatch.com or the contact page.