AXLEKEYSBETAA model does not have to stay trapped inside one workspace. It can begin as a private project, become structured through Systems, turn into a configurable object, move into public discovery, and eventually become a customer-facing product line.
Not every model goes through every stage. Some stay private. Some are only examples. Some move all the way to fabrication outputs. The value is that the path exists.
A model may begin from a prompt, sketch, reference image, client request, existing CAD file, product idea, shop standard, or agent workflow. The first step is understanding what kind of object is being created and why.
Before the model becomes useful, it needs context. That context comes from a System — a structured way to create a family of physical objects. The System tells Axle Keys what kind of object the model is becoming.
View Systems →Studio is where the model begins as a working project: selected System, model code, 3D geometry, project files, references, parameters, parts, materials, validation reports, and version history. Private by default. This is where the messy work happens.
Read Studio docs →A model becomes more valuable when its structure is visible — named parts, dimensions, editable parameters, material assumptions, relationships between parts, System rules, and output logic. A 3D object can be viewed. A structured model can be configured, reviewed, reused, and prepared for output.
A configurable object exposes useful controls — width, height, depth, material, finish, shelf count, layout choices, hardware options. The goal is not to expose everything. The goal is to expose the decisions that matter while protecting the technical relationships underneath.
Before a model moves forward: did it build? Are there geometry errors? Are parameters valid? Are parts named clearly? Are materials assigned? Is the model public-ready, customer-ready, or fabrication-ready — or only conceptual? Validation is a structured review step, not a guarantee.
When the model is useful enough to show publicly, it moves to Exhibition — where configurable objects can be browsed, studied, shared, and eventually remixed. Exhibition is about discovery and public visibility, not customer transactions.
Read Exhibition docs →A model becomes a Showroom product when it represents something a user, shop, or business wants to present publicly — with a live configurator, customer-friendly parameters, an inquiry form, and owner admin controls. The model becomes part of an offering.
Read Showroom docs →Some models move toward fabrication or production outputs — CAD exports, part lists, material lists, cut lists, assembly views, drawings, configuration records, job outputs. Output depends on the System and model maturity. Export does not mean automatic fabrication approval. Physical objects still need review.
The end of one model can become the beginning of another. A model may be duplicated, forked, remixed, used as an example, turned into a template, improved by agents, refined into a stronger System, or used as project knowledge for future work. This is where Axle Keys becomes more than a modeling tool — the work becomes reusable.
Choose a System, create or import a model, edit geometry, expose parameters, organize parts, attach files, review materials, validate changes, prepare outputs, publish or export.
Studio is where the object is made understandable.
Open Studio →Browse public models, study configurable objects, open models in Studio, share public work, feature strong examples, build future remix and community workflows.
Exhibition is where the object becomes visible.
View Exhibition →Present configurable products, create a public page for a user or business, let customers adjust options, collect inquiries, manage owner/admin controls, build toward embedded configurators.
Showroom is where the object becomes an offering.
View Showroom →A model may move forward, loop back, branch, or stop at any stage. Axle Keys is designed for this kind of movement — physical design work is rarely one straight line.
It is where models move — from private work to structured object to public artifact to customer-facing product to reusable knowledge. That path is the difference between a modeling tool and a platform.