An AI game studio in the sense of a workshop, not a company

People search this meaning two different things. If you want the software that acts as your studio, that is what this is. If you want a plan for a company of twelve, there is not one.

Two meanings, sorted out

The first meaning is software — a studio the way a paint program is a studio. One place with everything you need to make the thing, so you are not stitching four tools together to get one game.

The second meaning is organisational: a small company wanting AI in its pipeline, with seats, shared projects and admin. That version does not exist here. Stage Engine is a desktop app licensed per person, with Free, Indie at $10 a month and Pro at $50, and no team or enterprise tier.

Everything below is about the first meaning.

The disciplines one person normally cannot cover

A studio is a set of roles. Someone programs, someone designs the levels, someone makes the art, someone decides whether the whole thing is any good. Alone, you are all of them in sequence, and the sequence stalls at whichever one you are worst at.

Programming is the usual stall. Stage Engine takes it: you describe what should happen and Director 1 writes the GDScript inside your project. The other roles stay with you, which is correct, because they are the ones where your taste is the product.

Level building happens in the builder, by hand — terrain, water, weather, structures, characters. Asset and world generation feed into it rather than being a fixed catalogue you pick from.

One app, one project format

Everything happens in the same desktop application for Mac and Windows, and it carries its own copy of Godot. There is no separate engine to install, no export bridge between tools, no plugin chain to keep in sync.

The project is a real Godot project on your disk. That is the format the whole studio works in, from prototype to the thing you ship, and it stays readable whatever happens to us.

The game runs locally on that bundled Godot when you press play. Nothing streams and nothing renders on a server.

The role that stays yours no matter what

The creative director. Someone has to play the build and say the pacing is wrong, the world feels empty, the enemy is annoying rather than frightening. No amount of automation produces that judgement and none of it should.

Which means the working loop is you playing, deciding, and sending it back. That is the tool functioning normally, not a failure. Not writing the code does not remove your opinion about the game — it is the only thing you are actually being asked for.

What it needs

A Mac or a Windows PC, and an internet connection to build, because Director 1, asset generation and world data all come over the network. Playing what you built does not need one.

The download is free and there is a free plan. Paid plans buy more usage rather than more software.

Working alongside other tools

Nothing here stops you using what you already have. If you make music, make it elsewhere and bring it in. If you have a modelling tool you like, use it. The project is a normal Godot project, so bringing your own material in is the ordinary Godot process.

The same is true in the other direction. Version control, external editors, your own build scripts — all standard, because nothing is held in a format only this app understands.

What the app covers is the middle: the world, the code, and running the thing. Those are the parts that usually require three tools and a bridge between them.

Questions

Is there a studio or team plan?
No. It is a desktop app licensed per person. Free, Indie at $10 a month, Pro at $50, with no seats or enterprise tier.
Do I need other software alongside it?
No. Godot ships inside the app and the builder handles the world. You may still want your own art tools if you have them.
Does it replace a programmer?
For game code it does most of the job. For engine-level work, custom rendering or hard optimisation, no.
Where do assets come from?
Generation, the web, or you. There is no fixed catalogue to pick from, which is the point.
Can several people work on one project?
It is a Godot project on disk, so normal version control applies, but there is nothing built in for collaboration and no shared accounts.