AI Director
The Director converts intent into bounded, structured scene-tool calls and streams progress over a strict SSE decoder.
Built for accountable production
Yugma Studio turns natural-language direction into structured Three.js scenes with real assets, editable hierarchy, materials, lighting, collaboration, and OpenUSD-aware workflows.
Repository-backed product facts · reviewed 26 August 2026
Compose a scene as named objects and revisions rather than receiving one opaque mesh, then keep directing it in the browser.
The Director converts intent into bounded, structured scene-tool calls and streams progress over a strict SSE decoder.
A revisioned scene graph stores objects, transforms, materials, groups, lights, cameras, and provenance.
Three.js renders and edits the durable graph while virtualized lists and recovery boundaries contain large-scene failure.
Expand the matrix. Choose by boundary and workflow, not slogans.
| This system | Alternative · Spline | |
|---|---|---|
| Primary job | Prompt-to-scene composition plus continued structured direction | Collaborative browser 3D design and interactive experiences |
| Deployment boundary | Browser studio with Firebase persistence and provider-backed Director | Managed browser design platform |
| Evidence model | Revisioned owner-scoped scene graph and explicit tool mutations | Collaborative design history; verify current version/export details |
| Operator control | Named objects, hierarchy, materials, lights, groups, and exports | Visual editor, interactions, collaboration, and publishing |
| Integration surface | Browser editor, scene API, MCP, exports | Browser editor, collaboration, embeds, exports |
Free
Start with core scene composition and clean exports.
Premium
Higher AI, project, and storage limits for serious creators.
Ultimate
Maximum limits and priority compute under the published plan.
Current status. The browser studio, Director, scene persistence, exports, and published plans are product surfaces; individual model and asset availability remains provider-dependent.
Start with the architecture, reproduce the documented workflow, and verify the boundary against your own threat model.
No. Mutable vendor pricing is deliberately excluded. Verify current vendor terms before a purchase decision.
The status note, architecture page, and engineering articles state the current boundary and failure behaviour.