Real-time 3D for the web, built for production

We build interactive 3D that runs in a browser tab — product viewers, configurators, immersive scenes — and prepare the 3D assets behind them. The work is led by Alex Shylo, who has been in 3D graphics for 15 years and has led a 3D production team since 2016.

quote after briefwritten scope before work starts · timeline set in the quoteDescribe your 3D project →

What we build

Product viewers and configurators — rotate, zoom and switch materials or options on a model inside your page.
Interactive scenes — immersive 3D with Three.js, Babylon.js and WebGL; React Three Fiber components when the page is a React app.
Custom shaders — GLSL effects when the stock materials do not give the look you need.
WebXR — AR and VR views for browsers and headsets that support them.
3D asset preparation — production-ready models, PBR materials, glTF / GLB export and Draco compression sized for the web.

Built to run on a phone

A 3D page that stutters on a mid-range phone loses the customer it was built for. Every scene is optimised for desktop and mobile browsers: compressed glTF / GLB assets, fewer draw calls, sensible texture sizes and a loading state that does not block the rest of the page.

Where the 3D comes from

Modelling and web delivery are one workflow, not two vendors. Alex has worked in 3D since 2011 — from production-ready jewelry models prepared for CNC cutting to a 3D production pipeline with intake, task routing, QC and delivery, backed by custom tooling such as a Maya-to-SketchUp exporter. The team has worked in a production partnership with Ymage (Netherlands) for more than five years.

Tools: Three.js, Babylon.js, WebGL / WebGL2, React Three Fiber, GLSL, WebXR, glTF / GLB, Draco, Autodesk Maya, SketchUp.

Connected to the rest of your business

A viewer that cannot hand a lead to your CRM is a demo. When the 3D page needs to capture an enquiry, notify a sales channel or write to a spreadsheet, the same studio builds that side — see CRM integration, Make.com automation and AI automation.

How a project runs

Brief. You describe the object or scene, the page it lives on, the devices that matter and what exists already (models, references, brand rules).
Written scope and quote. What is built, in which tools, what "done" looks like, the timeline and the price. Nothing starts before you approve it.
Build and preview. You see the scene running in a browser preview, not a screenshot.
Review. Fixes to anything off-scope are included.
Handoff. Code, assets and a short guide on how to update the scene.

About the work shown here

The case studies on this site cover our automation and AI projects. Client 3D work is not published here yet — it will be added with each client's permission, and we do not show a mock-up as if it were a client project.

Questions

How much does a 3D project cost?

There is no starting price, because the range is wide: a single product viewer and a branded interactive scene are different projects. After a short brief Alex prepares the written scope with a price and a timeline himself, before any work starts.

Will it run on phones?

Yes, that is part of the build. Assets are compressed (glTF / GLB with Draco), draw calls are reduced and the scene is tested on desktop and mobile browsers.

We already have 3D models. Can you use them?

Usually yes. Send the files with the brief; they are checked for web use (polygon count, materials, texture sizes) and prepared or re-exported where needed.

Do we need Three.js, Babylon.js or React Three Fiber?

It depends on the page. React Three Fiber fits a React app, Three.js is the general-purpose default, and Babylon.js suits some scene-heavy or tooling-heavy projects. The quote names the choice and the reason.

Describe your 3D project

What the object or scene is, where it will be shown (your site, a shop page, an app), which devices matter, and whether you already have models. We reply within 24 hours with a fit/no-fit answer and, if it fits, a quote.