Cloud workbench for KiCad

Boards, reviewed.

Design, check and release native KiCad projects with your team and your agents. Every change is a typed command, every check is evidence, and nothing ships on a stale pass.

Fulmetry layout view: a four-layer field-sensor board with three unrouted nets highlighted
Built on KiCad 9PostgreSQLModel Context ProtocolGoogle Cloud RunWebGL2

Who it's for

Built for people who ship boards.

Follow one board from jumper wires to a client's sign-off — through the worlds of the nine people we met while onboarding.

The firmware engineer building a first custom board.

“Help me inspect the board, identify unresolved decisions, run checks and produce a KiCad project I can hand off.”

The solo product builder shipping a device alone.

“Keep the board history understandable, let my coding agent propose scoped changes, and show me what still needs human review.”

The software-native hardware maker.

“Give circuit changes stable identities, inspectable evidence and deterministic outputs.”

The experienced engineer reviewing a design.

“Show me the design, proposed changes, check findings, coverage and manufacturing evidence so I can make the final call.”

The small hardware team.

“Give us one shared process for proposing, checking, reviewing, releasing and investigating a board.”

The engineer preparing a board for manufacture.

“Produce a traceable manufacturing package, and never let stale evidence or unresolved parts pass for release readiness.”

The bring-up & test engineer.

“Show me this unit's 3V3 rail during a radio burst next to a known-good capture — and which release it was built from.”

The design consultancy & its clients.

“Let my client review the exact revision, see what was checked, and approve the release package themselves.”

Your coding agent, as a user.

“Install the Fulmetry skill, read the design summary, and propose typed changes a person accepts.”

Start your first board.