KeelenUse case · Agencies
Thirty client repos, one console, one flat bill.
If you run an agency or a dev shop, you juggle many repos with different owners, stacks, and merge rules. Keelen runs them from one console. It can run up to fifteen machines at once across thirty projects. Each project has its own merge policy, roadmap, and history. It all runs on your own AI credentials. Every run goes through the same verification gates.
The Agency plan costs $299 a month. You get 5,000 iterations, 30 projects, 15 concurrent runs, unlimited scheduled projects, 5 team seats, and 1-year log retention. The merge policy per project lets you pick the right mode per client. Use branch-only for the client who reviews everything. Use gated auto-merge for the one who wants speed.
- Fifteen concurrent machines across thirty client repos from one console.
- Per project merge policy: branch-only, manual, or gated auto-merge per client.
- Five seats and a 1-year audit trail for the work and pull requests a project is set to create. Branch-only work can stay a branch.
- Each project has its own roadmap. How you keep credentials apart depends on the connections and access rules you set for that client.
Many repos, one operator console
The hard part of running an agency is context switching. Every client repo has its own stack, its own rules, and its own bar for done. Keelen holds all of that per project: the roadmap, the steering rules, the merge policy. It shows one console across the fleet. Extra capacity helps with eligible work. Client review time and decisions still set the pace.
A merge policy per client
Clients disagree about autonomy, and they should get to. Set each project on its own: branch-only for the client who reviews every line, manual merge for the one who wants to press the button, gated auto-merge for the one who trusts the gates. Branch-only work stays a branch. Pull request and merge records depend on the policy you pick for that client repo.
A review rhythm for each client project
Agree on which requests can move while the team is offline. Agree on which changes need a human review. Use approval and merge settings per project. An outside scheduler using MCP can run repeat Security, Legal, and Controls reviews. Findings get triaged first. Then code remediation enters the backlog. Keep decisions that are not code with the people who own the client project.
Billing that doesn't multiply with clients
Token usage bills to whichever model credentials you connect, at cost. So your AI spend is clear, and per client if you scope keys that way. Keelen's own charge is one flat $299 tier for the whole fleet. You do not pay per seat or per client. Five team seats share the console, and the 1-year log retention gives you the paper trail client work needs.
Recommended plan
Agency: $299 / month
FAQ
Can Keelen run many client repositories at once?
Yes. The Agency plan runs up to 15 machines at once across 30 projects. It has unlimited scheduled projects. Each one has its own roadmap, merge policy, and history in one console.
Can each client have a different merge policy?
Yes. Merge policy is per project. For each client repo you can pick one of three. Branch-only means Keelen pushes branches and opens no PRs. Manual merge means it opens the PR and you merge. Gated auto-merge means it merges after the verification gates and the review window.
What does the Agency plan include?
$299 a month. You get 5,000 iterations and 30 projects. You also get 15 concurrent runs and unlimited scheduled projects. Plus 5 team seats, a dedicated support channel, and 1-year log retention. Bring your own model keys. Tokens bill to your provider at cost.