PCB design review that leaves a record
A desktop viewer for IPC-2581 assemblies, and a review workflow built for the way hardware teams actually sign things off — with a server that can run entirely inside your own network.
Join the beta What it doesWhat it is
Open a board, look at it properly, and record what needs to change — without exporting screenshots into a spreadsheet.
Reads IPC-2581
Layers, pads, vias, traces, component footprints and the physical stackup,
from .xml or .zip. Large boards — hundreds of
thousands of drawn features — open in seconds.
Says what it skipped
Every import reports what it mapped and what it did not. A viewer that quietly drops something it does not understand is a viewer you cannot review from.
Comments belong to a revision
Not to “the board”. When Rev C arrives, the review of Rev B stays attached to what people were actually looking at when they wrote it.
The review is the point
Most tools stop at rendering. The difference between a viewer and a review tool is what happens between four engineers and a deadline.
Everyone reviews independently
While a round is collecting, you see your own comments and not anybody else’s. Nobody anchors on the first opinion in the room, and nobody skips a section because it already has a comment on it.
The round is released deliberately
A moderator releases the round and everything becomes visible at once. Until then the server does not send you somebody else’s comment — it is not a setting in the client, it is what the server will hand over.
Answering and closing are different jobs
The designer marks a comment implemented. Somebody else decides whether it is done. Blockers clear only at the release gate, and only by the people who hold that role.
What was decided is recorded
Who raised it, who answered, who cleared it, when. An append-only log, so the answer to “why did we ship it like that” is a query rather than an argument.
Where your designs live is your decision
The same software, two deployments. Nothing about the desktop application requires a server at all.
On your own server
One container and a PostgreSQL database, inside your network. Designs never leave it. Air-gapped sites are a supported case, not an afterthought: updates are signed bundles you can carry in, and the licence file needs no call home.
Hosted by us
If you would rather not run anything. Each organisation is isolated in the data layer rather than by remembering — but your designs are then on a machine we operate, and the application tells you which of the two you are connected to.
Or no server at all
The viewer works on its own. A server adds accounts, shared reviews and the audit trail; it is not a licence check standing between you and your own files.
Join the beta
It is early. Beta testers get the software free, direct access to the people building it, and a real influence on what gets built next — in exchange for telling us what is wrong with it.
Where it stands
Being straight about this, because you would find out anyway: the viewer and the review workflow are working software. The server is new. There is no compute-heavy analysis yet — the server stores and coordinates, it does not open your board and check it. If you need a DRC engine today, this is not that, yet.