KeelenUse case · Roblox creators
Your game needs updates every week. Ship them.
Live Roblox games stay alive on a steady stream of updates. A small team cannot keep up with that pace. Keelen treats a Roblox game as a software project. It works on the GitHub repository your place is synced to with Rojo. It can use Lune where the project has a verified test command. Pull requests and merge evidence follow the project controls you pick. Asset work needs the project to opt in, and your creator details.
The Indie plan is $29/month. It gives you 200 iterations, 3 projects, and one project on the 24/7 loop. You bring your own model key. Token use then bills to your provider account at cost, with no markup.
- Your place lives in Git through Rojo. Every change then has history, review, and a way back.
- A verified Lune command can test Luau outside Studio. You still use Studio to accept the game.
- Art, audio, meshes, skyboxes, and characters need two things. They need the project to opt in. They need your creator details. No asset job can use your Roblox account before that.
- Publishing stays yours. The loop ships pull requests, and your release process decides what goes live.
Keep improving the game after its first build
Turn reported bugs and content changes into bounded Requests against the game. The game lives in version control. Review the proposed changes, the tests, and the Studio behavior before you accept a release. Use the same path for ongoing upkeep and for a first build.
Work through Rojo and Lune
Keelen does not drive Studio. It works on the files your place is synced to. That is what makes review, history, and rollback possible. With a verified Lune test command, Luau tests can check the behavior they cover outside Studio. Studio playtesting and acceptance stay with you.
Assets arrive with the change that needs them
Asset generation begins with a request. A change lists the art or audio it needs in a manifest. Asset generation and Open Cloud upload need the project to opt in. They also need your Roblox creator details. Those steps act under your account. Publishing stays part of your release process.
Honest limits
Balance, pacing, and fun are judgement calls. The loop does not make them. It supplies shipping capacity for the requests you write. Asset generation is off until you turn it on for a project. You also give your Roblox creator details, because the assets publish under your account. Publishing to your live game stays yours too. Work arrives as pull requests to your repository. Your 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?
Keelen can work on a Git repo with Luau tools. You need a supported provider connection. The pull requests you can review depend on the project setup, and so does the test evidence you get. Studio acceptance and publishing stay yours.
How are changes tested without loading the place?
A verified Lune command runs Luau tests outside Studio. Those tests run on a clean checkout. They cover the behavior those tests exercise. They do not replace Studio playtesting. They also do not replace visual acceptance or your review and merge checks.
Can it make art and sound for my game?
Yes. Art, audio, meshes, skyboxes, and animated characters can come from a written request. The change that needs them declares them in a manifest. They upload through Roblox Open Cloud. You turn this on per project and give your creator details first, because the assets publish 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.