Developer-first hardware test automation
RagerDuty runs your embedded tests on real hardware in cloud-managed racks — flashed, probed, and measured on every push. Plus hardware-in-the-loop simulation for everything that shouldn't need a physical board.
RagerDuty.yml in your repo · works with GitHub, GitLab & Jenkins triggers
Your firmware team ships slower than your web team — not for lack of skill, but because every test needs a desk, a board, and a person.
One engineer, one bench, one board at a time. Release candidates wait days for a smoke test a machine could run in minutes.
Bugs that only appear on rev-B hardware, at low voltage, at temperature. Without a device matrix, you find them in the field.
A timing regression introduced Monday surfaces in Friday's release test. Five days of commits to bisect — by hand, on a bench.
Define the pipeline in RagerDuty.yml. We handle the racks, the probes, and the flaky cables.
Your target boards — or our stocked device matrix — wired with programmable power, logic analyzers, and relay-driven peripherals. Flashed on every push.
Simulated sensors, buses, and fault injection — brownouts, dropouts, stuck I²C — reproducible down to the microsecond, no physical rig required.
Timing, power draw, and pass rates tracked per commit. A 3 mA creep in sleep current gets flagged the day it lands, with the offending diff linked.
Triggers from GitHub, GitLab, or Jenkins; results as PR checks and JUnit XML. Your team reviews hardware results where they review code.
A RagerDuty.yml declares targets, peripherals, and test commands. Start with our templates for STM32, ESP32, nRF52, and RP2040.
Use our stocked device matrix instantly, or mail us your custom boards — we rack them with power control and instrumentation in about a week.
Every commit builds, flashes, and tests on real silicon. Failures come back with logs, captures, and scope traces attached to the PR.
median full hardware regression, down from 2 days manual
more release candidates tested per sprint
of field-reported bug classes now caught pre-merge
“We found a brownout-recovery bug on rev-C boards that had been shipping for a month — RagerDuty caught it the first week because the rack tests every voltage corner on every push. Our firmware lead said it felt like hiring three QA engineers who never sleep.”
Two weeks of rack time on the stocked device matrix — enough to wire up a real pipeline and see your first regression caught.
Access request received — onboarding instructions are on the way.