About

We handle the unglamorous middle of AR retail: turning one beautiful source model into the many unbeautiful builds a real phone will accept.

Where this came from

Between us we spent a long time on product visualisation — furniture ranges shot in software, footwear turntables, the endless re-exports that go with them. The same thing happened on every project. A studio would deliver a gorgeous model, engineering would discover it was far too heavy for the handsets most shoppers actually carried, and the fix would be a folder of one-off scripts owned by whoever happened to be free that sprint.

Those scripts are load-bearing and nobody wants them. They decide whether the AR button works, they break when a new handset ships, and they are the first thing to rot when the person who wrote them changes teams.

What we built instead

Fennmoor is a conditioning pipeline with a viewer in front of it. You publish the source once; we derive the levels of detail, fit the textures to a memory budget, and emit the container each platform wants. Builds are addressed by content hash, so re-deriving a finish produces a new address rather than a migration, and a device that already holds a build never fetches it twice.

We are deliberately not a modelling tool and not a storefront. We don't want your prices, your stock, or your shoppers' identities — we take the model you already have and make sure the right version of it is on the handset before anyone taps.

Where we are

Early. One region, a handful of retailers at a time, and a habit of declining work that would drag us toward being a general-purpose 3D platform. If that is the stage you want a vendor at, say hello.