AXLEKEYSBETAAxle Keys is being built in public, one practical layer at a time. This page is the only place on the site that describes things that don't exist yet — everywhere else states what works today.
The modelling core, the fabrication outputs, and the agent endpoint are built and in use. What's still ahead is the knowledge that makes each System worth choosing, and the public spaces where finished models meet buyers.
The model loop works: describe or import an object, shape it, verify it, and take it out as drawings, cut lists, exports, or a configurator — in Studio or through your own AI agent. The current work is the layer that makes the output specific: Systems that carry how a thing is genuinely made, proven against real projects with the first Keyholders rather than declared finished on a marketing page.
The platform is live and the modelling engine is real. Everything after this builds on it.
This is the working core of the product today. It is why the rest of the roadmap is worth building.
One model, many artifacts. A finished model produces the files a shop actually builds from.
People work in Studio, agents work over MCP, and both drive the same model.
A System is a build methodology captured as real context — parts, rules, constraints, materials. Open Design works today. A named System is only worth releasing when it knows enough to be genuinely better than starting from scratch, and that is the work in progress.
Access is deliberately narrow while the product is proven with real work.
The embeddable configurator already ships, so the engine for this exists. What is missing is the public half — the places a buyer finds the model without ever opening Studio.
A few principles that guide what gets built and in what order.
One complete, working, well-documented System is worth more than five half-built ones. A System is only released when it knows enough to beat starting from scratch — which is why Open Design ships today and the named Systems are still listed as work in progress.
Every decision about what the platform can and cannot do is a product decision. Systems work because they have rules. A good configurator exposes the decisions that matter and protects the technical relationships underneath.
Every feature is evaluated against whether it makes the platform more callable — by people in Studio, by developers via API, and by agents via MCP. Callability is the long-term product. Agents are more useful when they work inside structure.
The roadmap will keep changing as the Systems become stronger and real users push models from idea to output. That is the point of building it in public.