The whole machine, in documents you can check.

Arkim is a master CAD system: it authors B-rep parts, weldments, sheet metal and PCBs as data, assembles them with real joints, simulates the mechanism and the circuit, lays out the drawings, and exports machinable STEP, DXF flat patterns and Gerbers. Verified by numbers — not pictures you have to trust.

Parametric, machinable CAD

Eight ways to author a part — scripts, sketches, weldments, sheet metal, imported STEP, circuit boards — all landing on one OCCT B-rep kernel. STEP in and STEP out, geometry a shop can machine.

Documents, not feature trees

A weldment is centrelines plus trim priority; sheet metal folds forward from a bend table to an exact flat pattern; a sketch never names derived topology — so editing early features can't break late ones.

Assemblies that move

Onshape-style joints with live sliders, expression-driven relations for gears and cams, closed loops, and an interference sweep that flags only what physically cannot exist — across the whole travel range.

Simulation you can trust

Chrono rigid-body physics with motors that stall under load, springs, friction, contact and terrain — mass and inertia taken from the geometry, welded groups collapsed to the bodies they really are.

Circuits, end to end

A board is a checkable netlist: schematic, autorouted PCB, DRC, Gerbers and BOM — plus SPICE testbenches for the electrical side, and a 3D board that bolts into the same assemblies and sims as the steel.

Drawings, revisions, releases

Third-angle sheets with hidden-line removal, associative dimensions and sections, exported to SVG, PDF and DXF. Every save is a revision, releases pin what a reference means, and deletion goes to a trash — never straight to gone.

One source of truth, from sketch to shop.

A design and an answer to the same question are two things that can disagree. Arkim keeps them as one: geometry is authored as data, checked by the numbers, and the same model that renders is the model that simulates, draws and exports. No screenshot settles a geometry question here.

MCP built in

Arkim speaks the Model Context Protocol, the open standard for connecting AI assistants to your apps. Because every design here is a document, a connected assistant authors one the way you do — parts, assemblies, simulations, cut lists, STEP — held to the same validators as the UI. You approve access with your own login, it reaches only the projects you are a member of, and every change it makes is a revision you can diff and restore.

How to connect