Live demo
Configure it yourself. No form, no sales call.
Five products, driven entirely from one JSON file. Swap materials, toggle options, change variants — and watch the rules engine block the combinations the factory cannot actually build.
What to try
Four things that show what a rules engine is for
The rendering is the part everyone looks at. The constraints are the part that stops an unbuildable order reaching your factory.
Turn on the headrest with active lumbar disabled — the rule engine offers the fix
Switch to the drone and enable LiDAR plus thermal: physically impossible, blocked
Change the CNC spindle to 24,000 rpm and watch coolant become mandatory
Copy the share link — the whole configuration lives in the URL
Under the hood
Everything above is data
Geometry from primitives
Every product on this page is described as a list of primitives inconfigurator.json — no model downloads, so the demo boots instantly. Production scenes swap that for tessellated CAD through the same interface.
Rules as a graph
Constraints carry a level, a message and an optional one-click fix. Errors block the quote; warnings cost lead time; info notes exist because someone senior wanted them said out loud.
State in the URL
The whole configuration encodes into the address bar. Share it, bookmark it, paste it into an email — it resolves to the identical scene, price and BOM with no session behind it.
Want this against your own catalogue?
The Feasibility Sprint takes one real product — your worst CAD assembly, not the easy one — through the whole pipeline in two weeks, and ends in a go or a no-go.
We reply to every enquiry within one business day, in your timezone — with a frame budget, not a brochure.