01 · Lossless intake
Most tools re-serialise a board after reading it, which reorders fields, drops comments and turns a small change into a thousand-line diff. QodeX parses the .kicad_pcb into a concrete syntax tree that remembers every token, including whitespace and comments.
Only the nodes we create — tracks, arcs, vias and zone fills — are ever written. Everything else is emitted byte-for-byte from the original file, so your Git history shows exactly the copper that was added.
02 · Constraint extraction
Constraints come from three places, in this order of precedence:
- Your KiCad project — net classes, differential-pair naming, custom design rules (
.kicad_dru), rule areas and the board stackup. - Your order notes — impedance targets, length windows, currents per net, locked regions.
- The fab profile — minimum trace/space, drill sizes, annular ring, aspect ratio and via technologies of the fabricator you selected.
Where your rules are tighter than the fab's, yours win. Where they are looser, the fab's are applied so the board is manufacturable as delivered.
| Constraint | Source | Checked in dossier |
|---|---|---|
| Trace width / clearance | Net class ∩ fab profile | Every segment |
| Differential impedance | Stackup + target | Per pair, per layer |
| Intra-pair skew | Order notes / rules | Per pair |
| Length window | Group definition | Per group |
| Annular ring, drill | Fab profile | Every via and pad |
03 · Topological routing
Routing is solved on the board's topology before any coordinates are fixed: which side of each obstacle a net passes, in what order nets cross a channel, and which layer each segment uses. Geometry is committed only once the topology is known to be feasible.
Order of operations
- Escape routing for BGAs and fine-pitch parts, ring by ring, using the via technology your fab supports.
- Constrained groups — differential pairs, length-matched buses, RF feeds — routed together with their return paths.
- Power distribution sized for current, with via arrays for thermal and current capacity.
- General signals, with layer changes minimised and a stitching via next to every reference change.
Return paths are constraints, not afterthoughts
For every constrained net we check the reference plane beneath it along its whole length. Crossing a plane split, an anti-pad void or a slot is treated like a clearance violation: the route is rejected and re-solved.
04 · DFM polish
The polish pass cleans up geometry that is electrically fine but hurts yield:
- Acute angles (acid traps) removed; bends mitred to 45° or arced
- Teardrops added at pad and via entries
- Copper slivers and starved thermals removed from pours
- Annular ring and drill-to-copper checked against the fab table
- Silkscreen clipped from pads and solder-mask openings
What you receive
| File | Purpose |
|---|---|
board.kicad_pcb | Your board, routed. Opens in KiCad unchanged except for new copper. |
board.glb | 3D model for review in the portal or any glTF viewer. |
fab/*.gbr, *.drl | Gerber X2 and Excellon drill files for the selected fab. |
dossier.pdf | DRC / DFM evidence: every rule, every result, constrained-net tables. |
Order workflow
- Upload the board in the portal. It is analysed in your browser and priced instantly.
- Pay in USD by card, Apple Pay, Google Pay or PayPal.
- Your order is queued; status updates and engineer messages appear in the portal.
- Deliverables are uploaded to your order. Inspect them in 3D, download, and confirm.
When we say no
Some boards cannot be routed as placed — a connector wedged against a BGA, a four-layer stack asked to carry eight layers of signals. When that happens you get a report showing the congested regions and the smallest change that would make the board routable (for example, two extra layers, or moving three named parts), and you decide what to do. We do not silently move parts or relax your rules.