A long road through 3D. A better home for the work.
I'm Ben Houston. After years building tools for artists, contributing to Three.js, and running enterprise 3D infrastructure, I'm building Threeify.
It started with making things work.
Early in my career, I built software for visual effects production. At Frantic Films, I co-created Deadline, a render manager that grew out of the practical need to get work through a render farm reliably. The business was later acquired by Amazon.
That kind of work teaches you to care about what happens after the demo. A render has to finish. The right files have to reach the right machine. Someone needs to understand what failed when it doesn't.
Those concerns have followed me through everything I've built since.
Clara.io brought the studio into the browser.
In 2012, we started building Clara.io at Exocortex. I wanted to bring the convenience of web applications to 3D creation: open a browser, work together, and render in the cloud. We launched at SIGGRAPH in 2013, and attracted more than 100,000 users within a year and a half.
But building something people wanted to try wasn't the same as building something professional artists could use for their everyday work. Browser limits mattered. So did the years people had invested in their existing tools.
Then Steelcase asked whether our technology could help customers visualize configurable office chairs. The rendering and scene-assembly work we'd built for artists had another use. We followed that opportunity into Threekit.
Threekit taught me what happens at catalog scale.
As founder and CTO of Threekit, I spent years building an enterprise product-visualization platform spanning real-time 3D, pre-rendered imagery, cloud rendering, and large asset workflows. We raised $65 million and served brands including Louis Vuitton, Christian Dior, Crate & Barrel, Steelcase, and Milwaukee Tools.
My work covered the architecture behind those experiences: bringing assets in, processing them, rendering them, and keeping the platform reliable as catalogs grew. Performance, visual quality, memory use, and cloud cost all had to make sense together.
The recurring challenge was keeping the content consistent. Engineering changes a dimension. An artist updates a material. A configurator and a rendering job both need the right revision. Managing those connections takes as much care as the rendering itself.
I wanted to make that foundation available to more teams, including the developers and artists who don't need an entire enterprise visualization platform.
Open source has been part of the journey all along.
Alongside those companies, I've been a volunteer contributor to Three.js since December 2012, submitting more than 200 pull requests. My contributions span physically based lighting and materials, environment-map processing, animation, and the math and tests that rendering depends on.
That work continues with MaterialX, WebGPU, and Gaussian Splatting. I also built Web3D Survey to help the community understand the graphics capabilities people actually have in their browsers, and contributed to the glTF specification at Khronos.
Working in that ecosystem has shaped how I think about long-lived 3D content. Your models and materials should remain useful as tools and renderers change. Open formats and access to your original files make that possible.
Why I'm building Threeify.
Across those projects, I kept coming back to the same need: a shared place for 3D content that works for both the people creating it and the applications consuming it.
Artists need to upload, preview, revise, and discuss their work without learning a developer's toolchain. Developers need to select versions, automate processing, and load assets without filling their code repositories with large binary files.
Threeify connects those workflows. Source files stay preserved. Versions stay identifiable. Your team can review content in the browser, and your applications can consume it through standard formats, versioned URLs, and an API.
It's the foundation I wanted to build with the benefit of that experience: useful for a small Three.js project, and able to grow with a team's library and production needs.
Tell me what you're working on.
If you're working with 3D assets and spending too much time moving files, tracking exports, or keeping applications in sync, I'd like to hear about it. That is the work Threeify is here to help with.
— Ben Houston, Founder

