Rupa3D

Lets an assistant build 3D CAD, meshes and physics scenes, then measure them and embed a certificate in the GLB.

What you can do

Rupa3D builds 3D assets: exact b-rep CAD with OpenCascade (primitives, booleans, fillets, 2D sketch to solid, STEP/IGES/STL/GLB export), meshes through headless Blender, and three.js scenes with Rapier physics published as a single HTML page. It then measures what it built against closed-form references or independent measurements, and embeds the certificate in the GLB at asset.extras.rupa3d so it travels with the file. Tools include rupa_periksa for checking any GLB against a spec, rupa_topologi and rupa_tekstur for topology and texel density, rupa_proksi for convex collision hulls, and rupa_cad_* and rupa_adegan_* families. A command-line gate returns exit codes 0, 1 or 2 for CI use.

When to use it

Use it when an assistant needs to generate or inspect 3D assets and you want verifiable measurements rather than a kernel's ok flag, for example checking someone else's GLB against a spec without Blender, producing exact CAD geometry with reported approximation error, or building physics scenes. It is not a replacement for Blender or Spline. The command-line gate suits CI pipelines that must reject assets failing required rules.

Requirements

Local Node.js runtime, version 22.14 or newer, run via npx rupa3d over stdio. Blender is optional: 23 of 36 tools work without it, and the other 13 need the Blender executable found on PATH, under C:Program FilesBlender Foundation, or via the RUPA3D_BLENDER environment variable. Workspaces default to ~/.rupa3d, overridable with RUPA3D_RUANG. No authentication declared.