Why not a feature comparison table?

Because every tool lists the same features and the differences are structural. Two tools that both say "AI writes your game" can be entirely different products.

Which axis matters most?

Where the game runs. It sets the ceiling on everything else and is the hardest thing for a tool to change.

Are browser tools worse?

No, they are different. For speed, sharing and low friction they are better and it is not close. For 3D scope they are constrained by the tab.

Can I move a project between tools?

Rarely, unless the output is a standard engine format. That is what axis two is measuring.

What does Stage Engine not do?

No browser version, no phone or Chromebook, no offline building, and no AI laying out your world.

AI game maker comparison: the five axes that matter

Feature tables are useless for comparing AI game makers, because every tool lists the same features. Five structural properties actually distinguish them, and once you know a tool's position on those five you can predict almost everything else about using it.

Axis one: where the game runs

In a browser tab, or natively on your machine. This is the most predictive single fact about any tool in the category.

A tab constrains object counts, world size, texture budget and framerate, and no amount of cleverness in the tool changes that. Tools in this position steer you toward small, flat scenes whether or not their marketing says so.

Native means the limit is your hardware, which is at least a limit you can see and upgrade. The cost is that it is a download, on specific operating systems, with a machine requirement.

Axis two: what you hold at the end

A project in a standard engine format that other software can open, or a document that exists only inside the service that made it.

The second is a completely legitimate product and it is what makes instant sharing possible. It becomes a problem exactly once: when you want to do something the tool does not do, and there is nowhere to take the work.

The test is one question. If this company shut down, or if you wanted to hand the project to a developer, what would you send them?

Axis three: how the code is produced

Assembled from a fixed list of behaviours, wired together as a graph, or written as real script by a model.

The list is fastest to start and has a ceiling shaped exactly like the list. The graph composes further but is programming with a different notation. Written script has the engine's ceiling rather than the tool's, and costs a round or two of iteration to get right.

The useful question to ask any tool: what happens when I need a behaviour nobody anticipated? The answer separates the three cleanly.

Axis four: who builds the world

The model, or you. Tools that generate levels are faster to a first result and produce something generic, because a landscape has no correctness test and a description only ever gets close.

Tools that make you build it are slower to a first result and produce the place you meant. Which one is right depends entirely on whether the world is part of what you care about.

This axis is the one most buried in marketing, because "generates your entire world" sounds better than "you build the world", and the second one is what people who finish games end up wanting.

Axis five: what the paid tier buys

More usage of the same product, or a different product with capabilities the free tier does not have. Both models exist and only one of them lets you evaluate the tool honestly before paying.

Watch for the version where the free tier is a demo of a smaller engine. You cannot learn anything about the real product from it, and by the time you find that out you have spent a fortnight.

Where Stage Engine sits on all five

Runs natively, on Mac and Windows, on a bundled copy of Godot. You hold a normal Godot project in a folder. Code is written by Director 1 as real GDScript, with no behaviour list anywhere in the product. The world is built by you, by hand, deliberately.

Paid plans buy more usage and not a different engine — Free at $0, Indie at $10 a month, Pro at $50, and no team or enterprise tier. External MCP access, for driving the app with your own agent, is on the paid plans.

The honest costs of that position: it is a download rather than a tab, building needs an internet connection, there is no phone or Chromebook version, and reaching something playable takes an evening rather than ninety seconds.

Questions

Why not a feature comparison table?: Because every tool lists the same features and the differences are structural. Two tools that both say "AI writes your game" can be entirely different products.
Which axis matters most?: Where the game runs. It sets the ceiling on everything else and is the hardest thing for a tool to change.
Are browser tools worse?: No, they are different. For speed, sharing and low friction they are better and it is not close. For 3D scope they are constrained by the tab.
Can I move a project between tools?: Rarely, unless the output is a standard engine format. That is what axis two is measuring.
What does Stage Engine not do?: No browser version, no phone or Chromebook, no offline building, and no AI laying out your world.