Authoring

Built as data,
not as code

The usual way a configurator gets rich is that somebody writes JavaScript per product and then maintains it forever. Ours is authored: layers, groups, rules and steps you set, and the same machinery underneath every product you sell.

01

The outliner

Your model arrives as a list of its real parts. You work through them one at a time, and everything else binds to a part by name: a colour grid, a print area, a rule. Reordering something never breaks anything.

02

The libraries

Colours, palettes and materials live above any one product. Edit a palette and every product that uses it follows. A brand can hold its own alongside its parent's, and a product can hold one of its own when it needs to.

03

Layers and designs

A surface is built up in layers. A base, a pattern with its own mask, another over it. Group them, give the group a name, and the shopper meets one decision called camo instead of three switches that only make sense together.

04

The texture editor

Surface detail is edited in the browser against the real product, not in a separate tool and re-uploaded. Heavy work runs on a smaller proxy and the full-resolution result is what gets committed.

05

Elements and steps

An element is one thing a shopper may change; a step is where they meet it. Arrange the steps, drop the elements into them, and preview the journey exactly as it will be seen before anyone outside sees it.

06

Launch

Pick the camera angles worth showing and the lighting to show them in, then publish a link. Nothing goes live because you saved it. It goes live because you launched it.

Why it matters

The second
product is
the test

Any platform can get one product looking good. Someone will write whatever it takes. The question is what the fifth one costs, and whether the person who builds it has to be a developer.

Here the fifth product is the same five decisions as the first, made against libraries that already exist. Nothing is addressed by position, so nobody breaks a launched product by reordering a list.

One product, in decisionsTeam cap
Parts in the outlinerCrown · brim · button · eyelets
From the libraryTeam palette · twill · mesh
DesignsSolid · two-tone · camo
What the shopper changes6 elements
Journey4 steps
No scripts. Nothing here is a file somebody has to maintain.
How a journey is authored
  1. 01Importthe GLB, welded and mapped
  2. 02Materialslayers over channels, palettes on top
  3. 03Elementsbound to the parts they drive
  4. 04Ruleswhat a choice hides, shows or forces
  5. 05Stepsthe order a shopper meets them in
  6. 06Previewthe real journey, before publishing

Book a demo

Put your product on the stage

Bring a model, or bring the product and some photographs. We'll walk you through what a customizer for it looks like, and tell you honestly what it takes to get there.

There is no self-serve sign-up yet: we set the account up with you, and go through your product before you commit to anything.