A studio, an engine and an API.

The 3DRise studio is a 3D editor that runs in the browser: models, materials, lights, environments, shaders, effects and a timeline, with nothing to install and every project saved in the cloud.

3DRise AI works inside the same project, with the same tools you use. Describe a change and it builds it — objects, lighting, camera moves, animation — and everything it makes stays editable. It removes the blank screen; the creative calls stay yours.

Everything you make goes into your library and is reusable in every future project, alongside a gallery of scenes, objects and materials you can take and change.

Under the studio is a real-time engine built on three.js and React Three Fiber. Shaders, lighting, performance, file formats, model optimization, asset storage and hosting are its job, not yours. You focus on creating

Motion is part of the engine too: clips and sequences on a timeline, actions that change many things at once, interactions on click and hover, and stories driven by the page's scroll.

A published project loads into any React app with one component, and the scene API controls it from your code: apply the project's actions, play its clips and sequences, scrub a story with your page's scroll, write values live, and listen to what the scene does.

Everything is addressed by the key you gave it in the studio, so your code keeps working when the scene changes. Designers keep editing the scene; developers keep the code.

The scene API is small and named after what it does, which makes it a natural surface for AI agents and models outside 3DRise. An agent can list a project's actions, clips and sequences by key and drive them — the same calls your own code makes.

The examples repository shows both sides: wiring a 3DRise scene into an app, and letting an AI model control it.