Pipeline & formats
Asset pipeline playground
Step a 412 MB CAD assembly down to a 610 kB web asset, one stage at a time.
- 1
Capture & ingest
13 sWhatever the geometry already lives in — CAD release, drone flight, scanner, or a modeller's FBX — lands in a content-addressed store.
STEP AP242 assembly hashed and stored, 4,120 parts indexed
- Size
- 412.0 MB
- 2
Reconstruct & tessellate
B-rep becomes triangles; photo sets become meshes or splats; raw scans get registered, denoised and classified.
- 3
Optimise to budget
Decimation, LOD chains, UV atlasing, Draco and KTX2 — until the manifest fits the budget you set.
What this is
Run the six pipeline stages against a synthetic source file and watch size, triangle count and build time change at each step — including the gate that fails the build.
Pick a source format and a target surface, then step through. The stage list, the reductions and the failure gates are the ones our build system actually applies. Change the target from 'web configurator' to 'print catalogue' and most of the optimisation stages switch off — different surface, different budget.
Things worth trying
- Start from a 412 MB STEP assembly targeting a mobile configurator
- Set the triangle budget below what the model can reach and watch the gate fail
- Switch target to AR Quick Look — the pipeline reroutes through USDZ
Bring us the product you were told could not be configured.
Tell us the option count, the CAD you already have and the frame budget you need to hit. An engineer reads it and replies with a straight answer — including when the answer is that good photography would serve you better.
We reply to every enquiry within one business day, in your timezone — with a frame budget, not a brochure.