Nova3D ships open clients for a generator that stays closed
Editable, part-aware 3D generation from text or reference images. Open-source client for nova3d.xyz.
At a glance
- What is it?
- Nova3D is a set of open clients, a Flutter web app, an MCP server and a Blender add-on, for a hosted 3D generation service whose pipeline writes Blender-native Python instead of emitting one fused mesh. The MIT license covers the clients; the generation backend behind nova3d.xyz is proprietary.
- Who is it for?
- Nova3D suits anyone who wants the client side of a part-aware pipeline: the Dart web client, the MCP server and the Blender add-on are MIT licensed, and the add-on itself was tagged v1.3.1 on 2026-08-12. It is not a local generator.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 23 days ago.
- What is it written in?
- Mainly Dart, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- RareSense/Nova3D764 ★ · +58
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| RareSense/Nova3D | 706 | 764 |
58 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The open half is the client, the generator is not
The licence paragraph splits the project in two. The clients and integrations in this repository are open-source; the hosted generation backend is proprietary. The repository structure section says the same thing from the other side, describing this repository as the home for Nova3D's open clients and integrations and calling the hosted generation backend currently closed-source. So the code you can read is the code that talks to the service, not the code that decides what a ring looks like. That distinction matters the moment you try to work out where a 26.42 mm overall height came from, because the generator that wrote that constant does not live in this repository. The README also says the same engine powers FormaNova, a jewellery CAD site, so the pipeline is shared with a product that has its own commercial surface.
The directory map lists two folders the root does not have
The README draws a six-entry directory map, and the root does not match it. Two entries in that map, claude-skills/ for Claude skills and examples/ for a gallery of generated assets plus their source programs, are both marked coming soon, and neither directory exists at the root. A third, docs/, is marked coming soon as well yet it is present. The entries that do exist are .github/, .gitignore, LICENSE, README.md, app/, blender-plugin/, docs/ and mcp/. The map is the only place the layout is described:
Nova3D/
├── app/ # Flutter/Dart web client · see app/README.md
├── mcp/ # Nova3D MCP server · see mcp/README.md
├── blender-plugin/ # Blender add-on · see blender-plugin/README.md
├── claude-skills/ # Claude skills (coming soon)
├── docs/ # architecture & the "3D as code" thesis (coming soon)
└── examples/ # gallery of generated assets + their source programs (coming soon)Six days of Blender add-on tags and nothing for the app
Every recorded release is a Blender add-on tag, and all three landed inside six days: blender-plugin-v1.1.0 on 2026-08-07, then blender-plugin-v1.2.0 at 11:52 on 2026-08-12 and blender-plugin-v1.3.1 at 14:06 the same afternoon, a little over two hours later. The numbering skips too, going from v1.2.0 straight to v1.3.1 with no v1.3.0. Two directories that are present at the root, app/ and mcp/, carry no tag of their own, so the release history documents the add-on and stays silent about which version of the web client or the MCP server you are running. The README does explain the shape of that: surfaces are being moved in one at a time, and today the client app and Blender add-on live in app/ and blender-plugin/. The last push to the default branch is dated 2026-08-12, the same day as the newest tag.
The Dart client connects out and never generates locally
The primary language of the repository is Dart, and that comes from one directory: app/ is a Flutter/Dart web client. The Getting started section routes every prerequisite, setup, feature and troubleshooting question to app/README.md rather than answering it on the root page, and it states plainly that the web client lives in app/ and connects to the hosted Nova3D service with no local backend required. There is no offline path described anywhere on the root page. If you clone this repository expecting to run generation on your own hardware, what you have installed is a front end, an MCP server and a Blender add-on, while the step that actually decides your geometry still leaves the machine. The public app at app.nova3d.xyz is where that step happens.
Model-agnostic means four providers behind a settings menu
The second point of the technical philosophy calls Nova3D model-agnostic: it is a generation harness, and providers are swapped through the settings menu, with OpenRouter, OpenAI, Anthropic and Gemini named as the options. The stated reason is that the pipeline handles validation and execution regardless of which LLM writes the code. That design keeps a provider change from turning into a code change, and it also means the geometry you receive depends on whichever model the settings happen to name when you run it. Nothing in the client pins one, and nothing in the repository records which provider produced a given asset. The artefacts described further down, a depth-7 kinematic chain or a measured 6.22 mm crown height, are therefore statements about one configuration rather than a fixed property of the pipeline.
The ring prompt is the acceptance test, stated in millimetres
The Anatomy of a generation section puts a jewellery prompt in front of the reader and then holds the result against it. The prompt asks for a gold engagement ring with an oval center stone measuring 6.82 × 8.75 × 4.40 mm, a raised prong setting and small pavé diamonds along the upper band, then pins four further numbers: a 17.00 mm inner diameter, noted as US size 6.5, a 6.22 mm crown height, a 20.96 mm overall width and a 26.42 mm overall height. The claim attached to that prompt is that prompt-stated counts and dimensions hold up when measured back from the result. A demo caption makes a separate promise, 4K PBR textures ready for games, animation and VFX. Both are prose claims, and no evaluation directory appears at the root to check either one.
Joints and UV charts are written before geometry exists
The articulation section is where the program-as-source claim does the most work. Rigging is an additive code pass: joints are added at real pivots, referencing parts the program already named, and the existing geometry never moves. The assembly hierarchy section makes the same argument from the other end, describing a robot arm that exports as a depth-7 kinematic chain where rotating any pivot moves its whole subtree, against generators that export a flat list with nothing to grab or rig. UV handling follows the same logic, with each part given its own chart, auto-packed into one clean, non-overlapping atlas grouped by sub-assembly. The Built as parts section draws the ordering explicitly: components are generated as their own named, watertight parts, so any piece can be selected, retextured, replaced or rigged on its own.
Every rival comparison is a video, not a table
The competitive claims are specific enough to look for in the source. Against the diffusion generators Meshy, Tripo and Rodin, the argument is that they extract a single merged mesh with no part boundaries, while CSG and OpenSCAD systems guarantee solids but cap out on organic shapes, hierarchy and materials, and Nova3D uses Blender's scene graph as a strict superset of both. Against PartCrafter, which returns a handful of unnamed chunks, and CubePart, which must be handed the part names and then slices a finished mesh into capped, approximate regions, the argument is about ordering rather than quality. The remaining comparisons pair Nova3D with TRELLIS, TRELLIS.2, Hunyuan3D, TripoSG, PartPacker and Meshy, and the property being argued is edit locality: assets stay inspectable, regenerable, restylable, articulable and exportable instead of collapsing back into one undifferentiated mesh.
Editorial conclusion
Nova3D suits anyone who wants the client side of a part-aware pipeline: the Dart web client, the MCP server and the Blender add-on are MIT licensed, and the add-on itself was tagged v1.3.1 on 2026-08-12. It is not a local generator. The part hierarchy, the joint pivots and every dimension in the README arrive from a hosted service whose backend is proprietary, so the parts you inspect were produced by code you cannot read or run. Before using it, read app/README.md rather than the root page, confirm which provider your settings name before you compare output against a rival, and treat the measurements in the README as claims made in demo videos until you have checked them against your own result.
Frequently asked questions
Is the Nova3D generation backend open source?
No. The README states that the clients and integrations in the repository are open-source under MIT while the hosted generation backend is proprietary, and the repository structure section calls that backend currently closed-source.
Which platforms does Nova3D ship clients for?
Three directories exist at the root: app/, a Flutter/Dart web client, mcp/, the Nova3D MCP server, and blender-plugin/, a Blender add-on. The web client connects to the hosted service and needs no local backend.
Does the Nova3D repository include example generated assets?
Not yet. The directory map lists examples/ as a gallery of generated assets plus their source programs and marks it coming soon, and the directory is absent from the root. claude-skills/ is listed the same way and is also absent.
How does Nova3D let you choose the model that writes the geometry code?
The second point of the technical philosophy calls it a generation harness: OpenRouter, OpenAI, Anthropic and Gemini are swapped through the settings menu, and the pipeline handles validation and execution regardless of which LLM writes the code.
Can Nova3D rig and UV-map the assets it produces?
Rigging is an additive code pass that adds joints at real pivots referencing parts the program already named, leaving existing geometry unmoved. Each part receives its own UV chart, auto-packed into one non-overlapping atlas grouped by sub-assembly.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/raresense-nova3d)Star history chart for your README
[](https://hysenlabs.com/projects/raresense-nova3d)Was this useful?