voxelbox Start a Project
case study · CS·11

The studio site as a system.

An explorable studio world: floating architectural districts, a continuous camera journey, original games, and a live portfolio of what we build.

livewebinteractivestatic-fast
the problem

What we were handed.

A studio that sells custom systems can't credibly run on a page-builder template. The site itself has to make the argument: fast, owned end-to-end, and cheap to keep fresh.

The usual trap is the opposite trade — either a beautiful site that's a chore to update, or an easy one that looks like everyone else's.

what we built

The system.

A custom three-dimensional studio world, built from procedural architecture and connected districts. Native scrolling moves the camera through design, intelligent systems, original games, and the next project, with every destination also available as a regular link.

Real project previews are displayed inside the world, alongside a live portfolio list driven by our demo feed. New work appears automatically, while useful project links remain available if the feed cannot load. The site is served and cached on our own stack.

Static core

Hand-written HTML, CSS, and JS — nothing between you and the page.

A living world

An original architectural scene with a scroll-driven camera, a deconstruction control, motion settings, and accessible content when 3D is unavailable.

Live wall

Feed-driven portfolio — new work appears with zero HTML edits.

Self-hosted

Served, cached, and monitored on the same stack we sell.

the outcome

What changed.

You're reading it. The site loads fast, updates itself when work ships, and doubles as the honest answer to “what would you build for us?”

your project

The next study could be yours.

Bring us the problem — the messy, manual, “there has to be a better way” kind. We'll design the system, build it, and run it.