Our story
Firmware shouldn't wait on hardware
CircuitTwin started from a simple frustration: why do embedded engineers have to wait weeks for boards to arrive just to test a few lines of firmware?
The problem
Teams wait on hardware
The embedded workflow is still hardware-first. Order dev boards, wait for shipping, wire up sensors, fight a flaky debug probe, all before writing a single line of testable firmware. Every revision repeats the cycle, and iteration speed pays the price.
Hardware is also a bottleneck for collaboration. Whoever holds the board holds the build, and the rest of the team waits their turn.
The solution
A virtual twin of your board
CircuitTwin builds a virtual embedded twin from real hardware data and datasheets. We model the MCU and its peripherals at the register level, so you can boot, step, and debug firmware in simulation long before the PCB comes back from fab.
We focus on the embedded targets teams actually ship, MCUs like STM32, ESP32, and Nordic, and build accurate models from their datasheets rather than hand-written stubs. Your firmware meets reality on day one instead of on delivery day.
Real hardware, virtualizedWhat we value
The principles that guide everything we build
Accuracy
Register-level fidelity is the foundation, not a feature. We model peripherals from real datasheets so behavior in simulation matches behavior on silicon.
Developer-First Workflow
Built by embedded engineers, for embedded engineers. CircuitTwin fits the way teams already write, flash, and debug firmware, not the other way around.
Practical Engineering
We ship tools that solve real problems on real projects. Honest about what's supported today, focused on what actually moves a firmware team forward.
Open Simulation Ecosystem
We build on open simulation technology and contribute back. Better embedded tooling should lift the whole community, not lock it in.
Be first to try CircuitTwin
We're opening early access soon. Join the waitlist to get an invite, or reach out if you'd like to talk.