Open Hardware · Embedded Systems
Heisenboard builds open hardware tools for engineers who need to understand exactly what's running inside their systems — and change it.
About Heisenboard
Werner Heisenberg showed us that the act of observing a system changes it — and that truly knowing what's happening inside is harder than it looks.
We named our company after that problem. And we build tools that solve it.
Engineers deserve to know the state of their systems: what's running, what's protected, what's in memory, and why. Too often that visibility is an afterthought — bolted on, unreliable, or absent entirely. We think it should be foundational.
Everything we build starts from that principle. We care about memory safety, hardware reliability, and tools that tell the truth.
We're a small team. We ship hardware. We double down on what works.
Know your state.
"The act of observing a system changes it — knowing what's really happening inside is harder than it looks."
Product
Automotive controllers have always been closed: closed hardware, closed software, closed ecosystems. You buy what's available, work within what's supported, and hope the vendor's roadmap aligns with yours.
Chameleon is different by design.
It's an open source hardware controller built around proven, automotive-grade components and designed to run TockOS — the embedded Rust operating system that brings hardware-enforced memory isolation to the automotive domain.
Rust doesn't dominate automotive yet. That's what the name is about. Chameleon fits naturally into an environment where it isn't expected, and changes what's possible there.
The enclosure is sourced from standard automotive tooling — no custom molding, no minimum order surprises. The schematic is open. The design files will be open. Build it, modify it, learn from it.
Chameleon is for the engineers who've always wanted to see what's inside — and change it.
32-Pin Connector — Functional Layout
Molex 643340100 · Hover pins for signal detail · Faded pins = CAN splice
System Architecture
Dashed lines = wake paths · solid lines = data/power · Input Conditioning and IGN shown left of MCU as inputs · see pinout above for connector mapping