What runs in the cloud, and what runs on your machine
By Eduardo Orellana · Updated
Flockbay is free on your own Claude or ChatGPT plan. Claude Pro or Max, or ChatGPT Plus or higher, builds a real Godot project in the Godot editor. Claude Free and ChatGPT Free do not run here. More models are optional, a credit reload at API prices. Windows today. The engine is the official Godot release. The line is simple and worth stating exactly. Building needs the network. Playing does not. Nothing about your game is rendered, streamed or executed on somebody else's hardware.
Your game runs on your computer
Flockbay is a desktop application for Windows, and it ships with Godot inside it. When you press play, the game starts on your machine, using your processor, your graphics card and your memory. There is no streaming, no remote rendering and no video feed coming back from a server.
This is the part people most often assume works the other way, because a lot of tools in this space do run the game elsewhere and send you a picture. That approach has real advantages, chiefly that it works on any machine. It also has a hard cost: your framerate is a shared resource, your input latency includes a round trip, and the size of world you can build is decided by whatever the provider is willing to pay for.
Running locally inverts all of that. A world with terrain, weather and a few hundred simulated characters is bounded by your hardware rather than by our infrastructure bill.
More on this: Looking for a game maker with no download
What does come over the network
Flockbay, which writes the GDScript for your game, runs over the network. So does asset generation, and so does world data such as terrain sources. These are the parts that genuinely need to be somewhere else, because they are large models and large datasets rather than something that fits on a laptop.
The consequence is direct and you should plan around it: you need an internet connection while you are building. There is no offline mode, no degraded mode and no cached fallback that lets you keep working on a train. If that is a blocker for you, it is better to know before you install anything.
The connection is not needed to play. Once the game exists, it runs on the bundled Godot with nothing phoning anywhere.
Where your project lives
On your disk. What you build is a real Godot project in ordinary files, sitting in a directory on your own machine, not a record in a database you access through a browser.
This is the practical difference between a tool you use and a service you rent. Back it up how you like, copy it to another machine, keep it after you stop using the app. Godot is open source and free, so a project in Godot format does not stop being openable.
There is no cloud game building, no remote build queue and no server-side editor. The app on your machine is the whole editing surface.
More on this: Can I edit the code myself?
What this costs and what it buys
The cost is that it is a download and it needs a real computer. It will not run on a phone, a tablet, or a managed machine you cannot install software on. Browser tools win on that point and there is no way around it.
What it buys is headroom and ownership. The game can be as heavy as your machine allows, the framerate is real, and the project is a thing you hold rather than a thing you access.
Pricing follows the same logic. Flockbay is free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key. Flockbay builds from a library of ready-made objects, or with Godot's own shapes. There is no better engine to buy, because the engine is on your machine and it is the same one for everybody.
More on this: Best free AI game maker: count the cost that is not money
Working across two machines
A common question, since the project is local: what happens if you build on a desktop and want to continue on a laptop.
The answer is that the project is a directory of ordinary files and moving it is your call. Copy it, sync it with whatever you already use, or keep it in version control. Install the app on both machines and sign in with the same account.
Since September 2026 there is also a copy that follows you. Flockbay keeps each game in your account, with 1 GB of room, and a game that is not on this machine yet shows up on your Projects screen to bring down. The folder on your disk is still the game; the copy is kept alongside it, and you can switch it off per game.
It is a convenience, not a backup guarantee. Whatever you already use for the files you would hate to lose should cover this too, and it is worth setting up before you have four months in it rather than after. Two machines, two installs, one account, and the files wherever you decide to keep them: that is the whole arrangement, and it has the advantage of being something you can reason about.
More on this: Do I need Godot installed to use Flockbay?
Questions
- Is my game rendered on a server?
- No. It runs locally on the copy of Godot bundled with the Windows app, using your own hardware.
- Do I need an internet connection?
- To build, yes. The chat, asset generation and world data all come over the network. To play what you built, no.
- Is there an offline mode?
- No, and there will not be one. Building depends on services that do not fit on a laptop.
- Where is my project stored?
- In a directory on your own disk, as a real Godot project. A copy is also kept in your Flockbay account unless you switch that off for the game.
- Can I edit my game from a browser or another machine?
- No. There is no browser editor. You install the app on the machines you want to work on and the project files are yours to move.