KeelenUse case — Roblox creators
Your game needs updates every week. Ship them.
Live Roblox games are kept alive by a steady stream of updates, and that cadence is what a small team cannot sustain. Keelen treats a Roblox game as a software project: it works on the GitHub repository your place is synced to with Rojo, writes Luau, runs the Lune test runner, and ships each change as a pull request that has passed its gates. It can also generate the art, audio, meshes, skyboxes, and animated characters a change needs, declared in a manifest by the change that needs them.
The Indie plan is $29/month: 200 iterations, 3 projects, and one project on the 24/7 loop. You bring your own model key, so token usage bills to your provider account at cost with no markup.
- Your place lives in Git through Rojo, so every change has history, review, and a way back.
- Luau changes are verified with Lune before they reach your branch, not by loading the place and hoping.
- Art, audio, meshes, skyboxes, and characters are generated from written requests, not left as placeholders.
- Publishing stays yours: the loop ships pull requests, and your release process decides what goes live.
One-shot generation is not the hard part
Producing a first playable build from a description is largely solved, and Studio's own assistant and several prompt-to-game tools do it well. The hard part is month two: a live game with players, a bug list, and a need for new content on a schedule. That is ordinary software maintenance wearing a different hat, and it responds to the same remedies, which are version control, tests, and steady shipping.
Rojo and Lune, not Studio automation
Keelen does not drive Studio. It works on the files your place is synced to, which is what makes review, history, and rollback possible at all. Luau tests run under Lune outside Studio, so a change can be verified automatically rather than by hand. You keep using Studio for the things Studio is for.
Assets arrive with the change that needs them
Asset generation is request-driven. A change declares the art or audio it needs in a manifest, and the pipeline generates and uploads it through Roblox Open Cloud rather than leaving a grey box behind. For a small team this is usually the slowest part of the week, and it is the part that blocks everything downstream.
Honest limits
Balance, pacing, and whether something is actually fun are judgement calls, and the loop does not make them. It supplies shipping capacity against requests you write. Asset generation is off until you turn it on for a project and supply your Roblox creator details, because generated assets are published under your account. Publishing to your live experience stays under your control too: work arrives as pull requests to your repository, and your own release process decides what reaches players.
Recommended plan
Indie — $29 / month
FAQ
Does it work inside Roblox Studio?
No. It works on the GitHub repository your place is synced to with Rojo. You keep using Studio; the loop works on the files, which is what makes review and rollback possible.
Can AI write Luau well?
Yes. Luau is well supported by current coding models, and Keelen runs Claude, Codex, GLM, or Kimi on your own credentials. The difference from a chat window is that the change arrives as a tested pull request rather than a snippet to paste.
How are changes tested without loading the place?
Luau tests run under the Lune runner outside Studio, on a clean checkout, before anything can merge. That is what makes unattended changes to a live game safe enough to consider.
Can it make art and sound for my game?
Yes. Art, audio, meshes, skyboxes, and animated characters can be generated from written requests, declared in a manifest by the change that needs them, and uploaded through Roblox Open Cloud. You turn this on per project and supply your creator details first, because the assets are published under your account.
Will it publish updates to my live game automatically?
No. Publishing stays under your control. The loop ships changes as reviewed pull requests to your repository, and your release process decides what reaches players.