Your device crashed in the field. VolatileSys already found the root cause — and wrote the fix.
It ingests your fleet's telemetry, autonomously diagnoses failures against the chip's datasheet, and drafts the firmware fix — for a human to approve.
- ingest
- decode
- diagnose
- approve
- ›gatherpulled 300 s telemetry window before the fault
- ›localizeISR starvation — TIM2 handler blocks the scheduler
- ›researchmatched RM0090 reset behaviour, p.412
- ›resolvedrafted patch · validated (clang -fsyntax-only)
Frame processing runs inside the TIM2 interrupt, starving the RTOS scheduler until the watchdog resets the MCU.
void TIM2_IRQHandler(void) {- process_frame(); // blocks inside the ISR+ xQueueSendFromISR(rx_q, &frame, NULL);TIM2->SR &= ~TIM_SR_UIF;}
- 174backend tests on every commit
- 100%agent output behind a human approval gate
- org-scopedtenant isolation on every query
- SOC 2on the roadmap — ask us where we are
Diagnosing a field failure is fragmented — and it's your senior engineers who pay for it.
A device fails in the field and the clock starts. Three disconnected gaps stand between the alert and the fix.
Generic dashboards weren't built for edge devices.
Heap and stack pressure, ISR frequencies, brown-outs — the signals that precede a field failure are invisible in tools designed for web services. You find out the device died, not why it was dying.
Your tickets aren't connected to your telemetry.
A crash report arrives as a screenshot and a hunch. The data that actually explains it lives in another system, at a timestamp no one has correlated yet. Every investigation starts from zero.
Every root-cause analysis is manual, senior work.
An engineer pulls logs by hand, scrolls a 500-page datasheet for one register, reasons about the failure, and hand-writes the patch — the same slow loop, incident after incident.
Mean time to resolution stretches into days while your most expensive people burn hours per incident — reproducing the crash, reading datasheets, and writing patches by hand. It doesn't scale with your fleet, and it doesn't scale with your team.
From alert to approved fix, on one connected path.
The agent runs the investigation a senior engineer would — in order, showing its work at every step.
A crash alert or ticket fires.
A threshold breach in the telemetry — or an incoming support ticket — triggers an investigation automatically. No one has to notice first.
The agent pulls the telemetry leading up to the failure.
full reasoning traceIt gathers the exact window before the crash — heap, stack, ISR rates, the events that fired — already correlated to the device and the moment.
It localizes the fault — down to the firmware loop or pin.
Instead of a vague "device reset," you get a specific location: the interrupt handler that starved the scheduler, the pin that browned out.
It researches the MCU's datasheet.
cited datasheet pagesThe agent retrieves the relevant register behavior and reset conditions from the chip reference manual — the 500-page search, done in seconds.
It drafts an RCA and a firmware patch.
A root-cause report grounded in the telemetry window and the cited pages, plus a syntax-validated patch — every claim pointing back to its evidence.
A human approves before anything ships.
approval gateThe patch lands in front of an engineer for review. Nothing is posted to a ticket or a repo until a person signs off.
Scrub the trace. Every step is on the record.
This is the persisted trace of one investigation — the same audit trail every customer run leaves behind. Drag through it.
Waiting on a human — nothing ships without approval
status=needs_review assigned: on-call firmware engineer auto-post: DISABLED (always)
A dashboard worth having on its own — and the ground truth the agent reasons over.
Before an agent can diagnose anything, it needs telemetry it can trust. VolatileSys decodes your fleet down to the register — which is exactly why its conclusions hold up.
- heap_freeu16@0
- 11234 B
- stack_freeu16@16
- 6100 B
- cpu_pctu8@32
- 82 %
- batt_mvu16@40
- 3714 mV
- isr_tim2u16@56
- 14600 Hz
- temp_ci8@72
- 23.5 °C
- watchdogu1@80
- 1
- crash_countu7@81
- 2
Bit-packed frames, over MQTT or REST
High-frequency payloads stream from fleets of microcontrollers, buffered and decoded off the request path — no dropped frames when a device floods.
A payload decoder you can see
User-defined bit-field rules turn raw hex into named, readable metrics. Change a rule and re-decode the stored history — the raw frames are kept for exactly that.
Health built for silicon, not servers
Heap-vs-stack leak detection, CPU load, battery degradation, ISR frequencies, and watchdog and crash logging — the MCU signals generic dashboards never modeled.
Autonomous, not unaccountable.
Handing diagnosis to an agent is a real leap. It earns the trust by making every conclusion checkable and keeping a human in control of anything that ships.
Every claim links to its evidence.
A root cause points to a specific telemetry window or a cited datasheet page — never an assertion the agent can’t back. If it can’t ground a claim, it doesn’t make it.
The full reasoning trace is open.
Every step, tool call, and retrieved passage is persisted and replayable. You audit exactly how the agent reached its conclusion — it is never a black box.
Nothing ships without your approval.
The agent drafts; a person decides. No RCA or patch reaches an engineer, a ticket, or a repo until someone explicitly approves it — the gate is mandatory, not optional.
Your datasheets stay yours.
Proprietary reference manuals and schematics are scoped to your organization. No other tenant’s agent can retrieve, embed, or cite them — isolation is enforced on every read.
Start with the dashboard. Add the agent when you're ready.
The telemetry dashboard — everything you need to see your fleet.
- ›High-frequency, bit-packed ingestion — MQTT + REST
- ›The visual payload decoder — raw hex into readable metrics
- ›Real-time visualization, MCU health, and alerting
Everything in Pro, plus the autonomous agent that diagnoses failures and drafts the fix.
- ›Everything in Pro
- ›The autonomous diagnostics agent — RCA + firmware patches
- ›Private datasheet uploads, scoped to your org
- ›Ticketing integrations
Put the agent on your next field failure.
Early access is opening for firmware teams shipping fleets today — or talk to us about the Enterprise / Agent tier.