Our engine: 20,000 objects in a browser tab

An AI that builds websites can stand on a browser and a hosting platform. An AI that builds places needs an engine: one that draws the scene fast on a cheap phone, runs physics and scripts, keeps a room of players in sync and opens in AR or in a headset. We build that engine ourselves.

One scene, every device

The same scene, with its logic and data, runs everywhere, with no separate build for each platform:

• in any browser on phones and computers, in 3D, AR and VR headsets;
• on iPhone through an App Clip, straight from a link or a QR code;
• in the ARClip app on iOS and Android, and on headsets and AR glasses;
• as a Mac app, made from the latest publish with one command.

Big scenes stay fast

AI builds big: a team of agents fills a scene with thousands of objects, and people walk around it together. Our test scene of 20,000 objects runs smoothly in a browser tab, and we keep making it faster.

Why it matters

Generating a 3D model is becoming a commodity: many tools do it well, and we use the best of them. What doesn't become a commodity is what happens next: a place that loads fast on a classroom's old phones, holds a room of players, opens in AR and in a headset from one link, and that an AI agent can edit live while people are in it. That takes an engine, and an engine takes years.

See it at work: describe a scene, and the assistant builds it, or read about a multiplayer 3D game in the browser.