WebGL / Three.js

Three.js and WebGL development for product configurators, digital twins and 3D data

Start a project

3D in the browser stopped being a novelty: configurators sell furniture and cars, digital twins show a plant’s live state, and engineering data is easier to understand as a model than as a table. What separates a demo from a product is the asset pipeline and the performance budget.

We build 3D web applications with Three.js, React Three Fiber and WebGPU where it is available — from the Blender-to-glTF pipeline through interaction design to the loading strategy that makes it usable on a mid-range phone.

What we build

  • —Product configurators with pricing rules, variants and export to quote or cart
  • —Digital twins connected to live IoT, ERP or MES data
  • —3D data visualization for engineering, GIS, energy and logistics
  • —Interactive training, simulation and virtual tours
  • —Asset pipeline: glTF/GLB, Draco/Meshopt compression, KTX2 textures, LODs
  • —Performance work on existing WebGL projects (draw calls, memory, mobile)

How a project runs

  1. 01

    Scope and asset audit

    What must be interactive, what the models look like today, which devices matter. Output: performance budget and asset plan.

  2. 02

    Pipeline and prototype

    Convert and optimize one representative asset; build the interaction on it; measure on target devices.

  3. 03

    Build

    Full feature set, integration with product data and commerce, accessibility fallbacks.

  4. 04

    Ship and measure

    Loading strategy, analytics on interaction, CDN delivery, hand-over of the pipeline so your team can add products.

Frequently asked questions

What does a 3D web project cost?
The model count and how interactive they must be drive cost more than the code. A single configurable product is weeks; a catalogue with live data integration is months. Asset preparation is often a third of the effort.
Will it work on phones?
Yes, if it is designed for it from the start: texture budgets, compressed geometry, level-of-detail and a loading strategy. Retrofitting mobile support onto a desktop-first scene is expensive.
Three.js, Babylon.js or Unity WebGL?
Three.js for most product and data work, especially with React; Babylon.js when you want a more complete engine out of the box; Unity only when the project is really a game and load size is acceptable.
Can you use our CAD or BIM files?
Usually, after conversion and simplification. CAD models carry far more detail than a browser needs; part of the pipeline is deciding what to keep.

Have a system in mind?

Send us a short description of the problem, the current tooling and the deadline. We reply within two business days with next steps or a frank “this is not for us”.

Start a project