Early access

Upload your board.
Test it before it exists.

Send us your PCB files and we build a simulated copy of the board, with every part modeled from its datasheet. You, your team, or your AI agents can power it on and test it before you pay for a fab run.

Upload a designWe handle the modeling
Input
.kicad_pcb · .PcbDoc · Gerber + BOM
Output
A simulated board you can test
Setup
Upload and wait

Keep scrolling

01Physical board
Your layout, the way it would come back from the fab.
fx-01_revA.kicad_pcbMode: physical
C1U2C2U3C3J1U1J2SW1R1Y1D1U4C5C6VBUS 5.02V3V3USB_D± 90ΩSPI 24MHzSWDUART 115k2I²C 400kNRSTU2.VOUT3.301 V ±0.4%I(U1)23.4 mAY1 · XOUT16.000 MHz76.00 mm
Nets parsed
0 / 47
Datasheets
0 / 23
SPICE models
0 / 23
Simulation
○ Idle

02  Why we built this

Boards get designed in days now. Testing still takes weeks.

A lot of hardware teams now use AI to draft schematics, write firmware and even route boards. The design gets done fast, and then it waits on fab, assembly, and someone with time at the bench.

We want testing to keep up with that. Each revision gets its own twin as soon as you push it, so you can run tests as often as you change the design, without needing more people in the lab.

Hardware bring-up2–3 weeks
FixtrMinutes

03  How it works

How it works

01
Upload your design
KiCad, Altium, Eagle, or Gerbers and a BOM. Nothing else to set up on your end.
02
We read the datasheets
We find the datasheet for every part on the BOM and pull out pinouts, operating limits, timing and abs-max ratings.
03
We build the SPICE models
If the vendor ships a model we use it. If not, we build a behavioral one from the datasheet.
04
You test the twin
Power it up, probe nets, flash your firmware and inject faults, from the browser or through the API.

04  Interface

Use it yourself, or let an agent drive

Agent · MCP / API“Bring up the IMU”
›power_on(vbus=5.0)
✓3V3 rail settled in 1.8 ms
›flash("fw_v0.4.bin")
✓boot ok · UART @ 115200
›i2c_scan(bus=1, hz=400_000)
!0x68 responds intermittently
›probe("SDA", window="2ms")
✗rise time 1.9 µs · spec 300 ns
→suggest: R7, R8 10k → 2.2k
✓re-run with patch: 0x68 ACK 100/100

05  What it catches

Problems you’d usually find at the bench

Power failure3 findings
01
Brownout on USB hot-plug
Inrush sags VBUS below the LDO’s dropout. MCU resets on plug-in.
02
Regulator runs past thermal limit
Datasheet θJA says 74 °C rise at full load. No copper to sink it.
03
Back-feed through an I/O pin
Debug header powers the MCU through its ESD diode when the board is off.
Signal failure3 findings
04
I²C rise time out of spec
10k pull-ups plus bus capacitance give 1.9 µs. Spec is 300 ns at 400 kHz.
05
Crystal load caps mismatched
22 pF caps on a 9 pF crystal. Oscillator starts slow or not at all.
06
Reset pin left floating
No pull-up on NRST. Random resets when a hand gets near the board.

06  Get started

Try it on your own board

Send your design files and we’ll set up a demo using your actual hardware.