Founding pilot · ESP32 & ESP8266

Debug firmware with evidence, not guesswork.

Incendio Probe reads your serial logs, source and datasheets, then gives you ranked root causes, each tied to the exact line that supports it, plus fixes and a plan to verify them on the bench.

Invite-only while we work closely with our first engineers.

Example report (sample data)
Confidence: mediumEvery citation checked
1Heap exhaustion from unfreed MQTT payload buffers
main.c:58
char *buf = malloc(512);
serial_monitor.log:60
mbedtls_ssl_setup returned -0x7F00
2Beacon timeouts under max modem power-save

An investigator, not a chatbot

Designed around how embedded engineers actually debug: gather evidence, form hypotheses, test them.

Facts, not vibes

Confirmed facts, assumptions and hypotheses are kept apart. Causes are ranked by likelihood, without fake percentages.

Citations we verify

Every quoted log line or source excerpt is checked against your actual files. Anything we can't find is flagged.

Fix + verify

Each recommendation comes with a verification step. Code suggestions are clearly marked as not hardware-tested.

Your evidence, in context

Serial logs, C/C++/Arduino source, configs and datasheet PDFs, with line and page references preserved.

Private by default

Private storage, per-account access rules in the database, and automatic masking of Wi-Fi passwords and API keys.

Built for ESP32 & ESP8266

Resets, brownouts, Wi-Fi disconnect reasons, heap exhaustion, I2C/SPI/UART issues. Arduino and STM32 coming next.

01

Create a project

Board, framework (ESP-IDF, Arduino, PlatformIO), toolchain.

02

Upload evidence

Serial monitor log, relevant source, optional datasheet PDF.

03

Get a report

Ranked causes with verified citations, fixes, a verification plan, and follow-up chat.

What we will never claim

Incendio Probe never claims code was compiled, flashed or tested on hardware, never invents datasheet values or register behaviour, and tells you plainly when the evidence isn't enough.

Request pilot access