AuraOne Open includes Aura3D 2.0.3, the current release published on August 16, 2026. It is a TypeScript SDK for browser-native 3D scenes, prompt-to-code workflows, typed GLB/glTF assets, diagnostics, screenshot evidence, and static deploy checks under the MIT license. The coordinated release is live across 29 public packages, with the public documentation and package registry carrying the same version.
The short version: Aura3D lets a developer or coding agent describe a 3D surface and keep the result as editable TypeScript.
That matters because browser 3D is moving into ordinary software. Product pages need real GLB viewers. Data apps need spatial views. Robotics and Spatial 3D teams need public explainers that do not expose private captures. Agent-generated interfaces need an SDK that gives them maintained scene systems instead of a blank renderer and improvised glue.
Aura3D is built for that workflow.
What Aura3D Gives Developers
Aura3D starts from the way AI coding agents actually work. A prompt should not produce a fragile pile of geometry and hand-written asset paths. It should start from maintained scene kits, use typed assets, and leave behind source code a developer can inspect.
The core install path is simple:
npx [email protected] my-scene --template product-viewer
cd my-scene
npx @aura3d/[email protected] assets add ./assets/product.glb --name product
npm run dev
Teams can also install the engine directly:
npm install --save-exact @aura3d/[email protected]
The current 2.0.3 documentation covers 36 live public experiences and a production-oriented stack of typed assets, scene kits, Vite templates, diagnostics, screenshots, and static deployment checks. The 2.0.3 release notes describe the evidence and compatibility boundaries instead of implying that one package replaces every 3D engine or workflow.
What changed in 2.0.3
Aura3D 2.0.3 is a coordinated showcase and test-harness patch across the public package set. It restores Vite 7-ready browser evidence, adds the promised draw-range interaction, tightens small-screen route chrome, and removes local-development favicon noise. The current @aura3d/engine package carries the same release line.
The release includes:
- Browser-evidence recovery for the gallery and wow screenshot suites, including the Vite 7 port-output fix and the restored 11 gallery tests.
- An interactive Geometry Draw Range example with keyboard and click controls; selected ranges remain partial rather than silently becoming full-range renders.
- Responsive and local-development hygiene for the examples catalog and draw-range route at 390px, plus favicon links on 15 route entry points.
- The 2.0.2 corrections for the Turbo Drift Circuit tarmac, Skyline Runner collectibles and ember volleys, catalog posters, Tokyo-only Smart City composition, Draco decoding, and exposure behavior.
- 2.0.3 pinned across all 19 public scaffolds so a generated app installs the packed release dependency graph.
- A bounded compatibility claim: the release keeps the repository-locked
[email protected]comparison and does not claim to be a universal Three.js replacement.
Typed Assets, Not Invented Paths
3D workflows break when a model invents an asset ID or points at a model that was never supplied. Aura3D's safe asset workflow makes the supplied GLB or glTF explicit before the app code uses it.
import { createAuraApp, sceneKits } from "@aura3d/engine";
import { assets } from "./aura-assets";
const kit = sceneKits.productViewer(assets.product);
createAuraApp("#app", kit.toAppOptions());
That pattern is small, but it is important. The generated source owns the scene. The asset reference is inspectable. The deployed app remains normal browser software.
How It Fits AuraOne Open
AuraOne Open is the public tooling layer adjacent to Human Data and Enterprise Intelligence. Rubric Studio Open handles rubric authoring. Agent Studio Open handles agent traces and regressions. Robotics Studio Open handles local robotics dataset review. Trust Toolkit packages review and reliability checks. AuraGlass provides the UI layer.
Aura3D adds the browser-native 3D layer.
It belongs in the Open catalog because 3D product surfaces, data worlds, robotics explainers, and spatial-data previews need the same local-first contract as the rest of AuraOne Open: inspect the source repository and MIT license, install the verified 2.0.3 package graph, keep the artifact, and bring AuraOne in only when shared state, review, or governance is the real problem.
Aura3D and private spatial workflows
The boundary is simple.
Aura3D is the open SDK for building the scene: a product viewer, data world, interactive explainer, or browser-native 3D app.
Private spatial workflows may also need capture lineage, transform history, alignment notes, delivery state, handoff files, and scoped export terms. AuraOne does not currently market a standalone Spatial 3D application.
The open SDK helps developers ship browser 3D. A customer-specific data program would address private captures and delivery files only when a real workflow, rights boundary, and accepted output have been scoped.
Start Here
Launch the site at aura3d.auraone.ai, review the Aura3D 2.0.3 release notes, inspect the create-aura3d scaffolder on npm, install @aura3d/engine 2.0.3 from npm, open the AuraOne-owned overview at /open/aura3d, or inspect the source at github.com/auraoneai/aura3d.
If you are using an AI coding assistant, start with the agent context:
https://aura3d.auraone.ai/llms.txt
The goal is not to hide 3D inside a black box. The goal is to make browser 3D feel like software again: prompted, shaped, inspected, tested, and shipped as source.