Scene kits give coding agents maintained starting points for products, materials, particles, data worlds, cities, physics, and interactive scenes.
Aura3D.
The AI-native 3D SDK for the web.
Build browser-native 3D from prompts, scene kits, typed GLB/glTF assets, and editable TypeScript. Aura3D gives agents and developers the rendering, asset, diagnostic, screenshot, and deploy checks needed to ship real 3D software.
One command. A real app begins.
npx create-aura3d@latest my-scene --template product-viewer cd my-scene npm run dev
npm install @aura3d/engine
Use the direct package when Aura3D is a dependency inside an existing app. Use the scaffold when the 3D route is the app.
Browser 3D with software shape.
GLB and glTF files become generated TypeScript refs, so agents do not invent paths, string IDs, or unrelated model URLs.
WebGL and WebGPU paths, Vite templates, React adapters, diagnostics, and static deploy checks stay close to normal web software.
Route health, screenshot workflows, visual QA guidance, and deploy checks make a 3D app inspectable before it becomes a product surface.
Aura3D builds the scene. Spatial 3D governs the work.
The open SDK for browser-native 3D scenes, product viewers, data worlds, public explainers, and agent-authored visual software. Developers keep the TypeScript and can inspect the assets, runtime, diagnostics, and deploy output.
The governed App Data workflow for capture lineage, transform history, alignment review, delivery approvals, reviewer sign-off, and tuned weights. It handles the private record behind real 3D work.
Start where browser 3D already has a job.
A product viewer for a supplied GLB with studio lighting, orbit controls, and a static build.
A data world that turns metrics into a labeled 3D scene with camera motion and screenshot evidence.
A material lab that keeps chrome, glass, rubber, emissive, and clearcoat visually distinct.
A robotics or Spatial 3D explainer scene that can support public docs without exposing private capture data.