How it works

A compiler for copper.

QodeX treats your board the way a compiler treats source code: parse it without loss, extract the constraints, solve the problem in an abstract space, then emit geometry and a proof that it satisfies every rule.

01 · PARSE

Lossless intake

Comment-preserving S-expression tree.

02 · CLASSIFY

Constraints

Net classes, pairs, groups, fab table.

03 · ROUTE

Topology first

Escape, constrained groups, the rest.

04 · POLISH

DFM & dossier

Geometry clean-up and evidence.

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.

Invariant: footprints, their positions, locked items, 3D model paths, custom fields and design rules you did not ask us to touch are never modified.

02 · Constraint extraction

Constraints come from three places, in this order of precedence:

  1. Your KiCad project — net classes, differential-pair naming, custom design rules (.kicad_dru), rule areas and the board stackup.
  2. Your order notes — impedance targets, length windows, currents per net, locked regions.
  3. 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.

ConstraintSourceChecked in dossier
Trace width / clearanceNet class ∩ fab profileEvery segment
Differential impedanceStackup + targetPer pair, per layer
Intra-pair skewOrder notes / rulesPer pair
Length windowGroup definitionPer group
Annular ring, drillFab profileEvery 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

  1. Escape routing for BGAs and fine-pitch parts, ring by ring, using the via technology your fab supports.
  2. Constrained groups — differential pairs, length-matched buses, RF feeds — routed together with their return paths.
  3. Power distribution sized for current, with via arrays for thermal and current capacity.
  4. 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

FilePurpose
board.kicad_pcbYour board, routed. Opens in KiCad unchanged except for new copper.
board.glb3D model for review in the portal or any glTF viewer.
fab/*.gbr, *.drlGerber X2 and Excellon drill files for the selected fab.
dossier.pdfDRC / DFM evidence: every rule, every result, constrained-net tables.

Order workflow

  1. Upload the board in the portal. It is analysed in your browser and priced instantly.
  2. Pay in USD by card, Apple Pay, Google Pay or PayPal.
  3. Your order is queued; status updates and engineer messages appear in the portal.
  4. 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.

See it on your own board.

Upload a placed .kicad_pcb and get a quote in seconds.