percepta

AI tools can write firmware and flash it to your board. but they can't see if it actually worked. percepta closes that loop.

the problem

you ask claude to write a boot sequence that blinks an LED at 1Hz. it generates the code, compiles it, flashes it. "done," it says.

you stare at the board. it's blinking at 2Hz.

the AI has no idea. you're the only sensor in the loop. every verification, every regression check, every "did that actually work?" — that's you, staring at hardware.

what percepta does

point a camera at your board. ask questions in plain english. percepta watches your hardware and tells you what's actually happening. 

$ percepta

> is the status LED blinking at 1Hz?

✓ STATUS_LED: blinking at 0.98 Hz
✓ POWER_LED: on
  boot time: 2.3s

it remembers what it sees. you can query behavior by firmware version, detect regressions across commits, replay failure states.

what you can do

validate firmware changes
flash code, verify physical behavior. no more staring at LEDs.
catch regressions
behavior indexed by commit. know exactly when boot time got slower.
run hardware tests in CI
automated assertions on physical state. LED should blink at 1Hz? test it.
debug remotely
record sessions. share with teammates. replay exact failure states.
close the AI loop
let claude write firmware, flash it, and verify it worked. fully autonomous.

how it works

camera pointed at your board. you talk to percepta. it observes, remembers, and answers.

works with any webcam. runs locally. integrates with the tools you already use — claude code, cursor, any MCP-compatible environment.

status

in active development. early access available for teams building embedded systems.

want early access? building something with hardware?

email ↗ twitter ↗