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.
The system.
A hand-authored static site — no framework tax, no builder — with a WebGL voxel-assembly hero that builds the brand mark in front of you.
The “Floating in production” work wall is driven by the same JSON feed as our demo pipeline: publish a demo anywhere on our infrastructure and the homepage features it automatically. The site is served and aggressively cached on our own stack.
Hand-written HTML, CSS, and JS — nothing between you and the page.
A voxel-assembly scene, not a stock hero image.
Feed-driven portfolio — new work appears with zero HTML edits.
Served, cached, and monitored on the same stack we sell.
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?”
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.