CLOUD ROUND-TRIPS
Inference happens on-device. Your prompts and your geometry stay on your hardware — private by default, and fast because there's nothing to wait for over the wire.
Describe what you want in plain language; Archie turns it into structured, validated tool-calls and hands back real, editable geometry. It runs on a local, open-weights model fleet — your words and your geometry never leave the machine.
Open source · free forever · local fleet · public release soon — nothing leaves your machine.
Archie is not one model behind an API — it's a fleet of small, per-discipline models, DeepSeek-R1-distilled and fine-tuned for the operation in front of you. They're served on your own hardware. There is no cloud round-trip to wait on, no API key to manage, and no per-token meter running while you iterate.
Open weights — download the fleet and run it yourself.
CLOUD ROUND-TRIPS
Inference happens on-device. Your prompts and your geometry stay on your hardware — private by default, and fast because there's nothing to wait for over the wire.
DISTILLED, PER-DISCIPLINE
A DeepSeek-R1-distilled base with discipline-specific fine-tunes, so the model that plans a sketch isn't the one that lights a scene. The right specialist answers each call.
PER-TOKEN BILL
No metered API. Run it as much as you want on hardware you already own. Iterate at the speed of thought, not the speed of your quota.
Most text-to-CAD tools hand you a wall of generated code and wish you luck. Archie emits structured, schema-validated tool-calls into the real kernel — named operations with named parameters, in the order the engine runs them. Every call conforms to a tool-call schema the kernel actually exposes, so it can't ask for an operation that doesn't exist.
Every value is a parameter you can read and change, not a magic number baked into a mesh.
Calls are checked against the kernel's tool-call contract before they run; malformed intent is caught, not crashed.
You see the plan before anything is drawn, and the plan is the part's construction history.
A plausible-looking model can still be a broken solid — non-manifold edges, self-intersections, a shell that didn't close. Archie doesn't hand you the first thing it generates. Every result passes a coherence gate that runs checkValidity() against the kernel, and when something is off, the gate repairs it and re-checks — before the geometry ever reaches your viewport.
Other tools verify nothing and ship you the failure. Archie ships you a solid the kernel already agreed is valid.
feature tree · live
re-solved locally · 0 cloud calls
Because every call is a real parametric operation, what Archie hands back is the part's living construction history. Open the tree, change the wall from 4 mm to 3 mm, and the kernel re-solves locally — no second prompt, no regenerate-and-pray. Archie built it the same way you would have, so you can keep building from where it stopped.
Drive it by hand any time — every Archie call lands in the same feature tree and toolbars you’d use yourself.
Archie isn't bolted onto two apps — it is the spine that drives both. Ask it to sculpt, light, and frame a scene in Studio; ask it to sketch, constrain, assemble, and simulate a part in Forge. Same copilot, same readable tool-calls, same coherence gate — it just changes which engine it's speaking to.
archie · one kernel, two engines
No. Archie emits structured tool-calls into a real B-rep kernel and returns an editable feature tree, then verifies the solid before handing it back. You get geometry you can edit, simulate, and export — not disposable code.
A local, open-source AI copilot, a real CAD kernel, and a full 3D studio — Studio, Forge, and Archie in one app, on your machine.
Open source · free to start · public release soon