About AxoGeo

AxoGeo is a node-based 3D editor that runs in your browser. You build geometry by wiring nodes together instead of pushing vertices, so nothing you make is a finished object — it is a recipe you can keep changing.

The part that makes it different

Plenty of tools can produce a mesh. The interesting question is what happens after you export one.

Almost everywhere, the answer is: nothing. The recipe stays in the tool and your game gets the leftovers — a frozen mesh, and a trip back to the editor every time you want it a little different.

AxoGeo exports the recipe. On Roblox that means an .rbxmx model with a generated Luau runtime, where every parameter is a live Instance Attribute you can tune in Studio while the game is playing. On Godot it means a .glb paired with a GDScript that puts those same parameters in the inspector. The asset arrives still parametric, and your game code drives it.

A standard glTF export exists too, for every engine and DCC that reads one. That one is baked, and it is free — see pricing.

Not another Blender

Blender is extraordinary and free, and if you want a desktop modelling suite you should use it. AxoGeo is not trying to be a smaller one in a browser tab. It is built around a different idea: that a procedural asset should stay procedural all the way into the thing you are shipping.

That is also why the node vocabulary leans where it does — low-poly, flat-shaded, instanced, deterministic. Every instance is a pure function of its index and the frame, which is what makes an effect scrub-able, loop exactly, and survive being translated into another engine's language without drifting out of sync.

Where the name comes from

AxoGeo — said Axe-O-Gee-O.

Axo is for axon: the fibre a neuron sends its signal down, the connection in a network of connections. Which is exactly what a node graph is — the whole tool is a web of things passing signal to each other. (It is not short for axonometric, though people guess that.)

Geo is geometry, which is what comes out the other end.

And A, X and O are all symmetrical letters — which felt right for a tool about structure.

Where it is going

Roblox and Godot both have a full runtime mirror today. That was the hard part, and it is done twice: the engine works out which parts of a graph can be baked and which have to run live, so a new target only has to translate the live half into its own language. More engines get easier from here.

If you want a live runtime for a specific engine, come and say so in the Discord — that is how the order gets decided.