KeelenUse case — Agencies
Thirty client repos, one console, one flat bill.
If you run a development agency or dev shop, you're juggling many repositories with different owners, stacks, and merge conventions. Keelen runs them from one console: up to fifteen concurrent machines across thirty projects, each with its own merge policy, its own roadmap, and its own history — all on your own AI credentials, all through the same verification gates.
The Agency plan is $299/month: 5,000 iterations, 30 projects, 15 concurrent runs, unlimited scheduled projects, 5 team seats, and 1-year log retention. Per-project merge policy means you can run branch-only for the client who wants to review everything and gated auto-merge for the one who wants velocity.
- 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 the project is configured to create; branch-only work can remain a branch.
- Each project has its own roadmap. Credential separation depends on the connections and access policy configured for that client.
Many repos, one operator console
The overhead of running an agency is context-switching: every client repo has its own stack, its own conventions, its own definition of done. Keelen holds all of that per project — the roadmap, the steering rules, the merge policy — and surfaces one console across the fleet. Available concurrent capacity helps with eligible work, while client review capacity and decisions still set the pace.
A merge policy per client
Clients disagree about autonomy, and they should get to. Set each project independently: 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 remains a branch; pull-request and merge records depend on the policy selected for that client repository.
A review rhythm for each client project
Agree which requests can progress while the team is offline and which changes need manual review. Use project specific approval and merge settings. An external scheduler using MCP can trigger repeat Security, Legal and Controls reviews, with findings triaged before code remediation enters the backlog. Keep non-code decisions with the people responsible for 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 transparent and per-client if you scope keys that way. Keelen's own charge is one flat $299 tier for the whole fleet — not per-seat-per-client math. 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 concurrent machines across 30 projects with unlimited scheduled projects, each with its own roadmap, merge policy, and history in one console.
Can each client have a different merge policy?
Yes — merge policy is per project. Choose branch-only (Keelen pushes branches, opens no PRs), manual merge (it opens the PR, you merge), or gated auto-merge (it merges after the verification gates and review window) independently for every client repo.
What does the Agency plan include?
$299/month: 5,000 iterations, 30 projects, 15 concurrent runs, unlimited scheduled projects, 5 team seats, a dedicated support channel, and 1-year log retention. You bring your own model keys; token usage bills to your provider at cost.