Build your app. Build the tools your team needs.

Connect Claude Code, OpenAI Codex, GLM, Kimi, or Grok using your own supported subscription or API key. Grok accepts a SuperGrok sign in or an xAI API key. Pick an engine per project; AI usage stays on your provider account, and switching engines preserves your roadmap and history. Engine availability can differ by role. OpenRouter is currently limited to Keelen's own test and benchmark projects. It is not enabled for customer repositories.

No. Keelen runs on whatever credentials you connect at setup — a Claude subscription login or API key, a Codex login or OpenAI API key, a GLM key, a Kimi key, or a SuperGrok sign in or xAI API key. We don't resell tokens; usage bills to your own provider at cost. If you do own a Claude Pro or Max plan, Keelen is the highest-leverage thing you can point it at: the loop runs on the subscription you already pay for.

Five gates stand between the AI and your main branch. Where a verified project test command supports it, new tests are applied without the implementation first and must fail — tests born green are rejected. An independent adversarial reviewer that shares no context with the dev run reviews the diff. When a verified project test command is available, your test suite runs on a clean checkout. Configured required CI checks protect a merge from a red result. And gated auto-merge waits out a review window — or you can replace it entirely with plan-review sign-off before any code is written, manual merge, or branch-only mode. The loop is also forbidden from weakening your checks: it may not skip a failing test or mark a check non-required to get to green.

Every failed run is classified into one of 30 failure kinds. Infrastructure blips and provider limits retry on a budget and never count against your work; real dead ends become one plain-English card in your Needs-you queue with a recommended action, and the project pauses instead of burning your quota. Iterations are wall-clock capped (about an hour for a dev run), so nothing spins forever. You resolve the card, hit resume, and the loop continues.

TypeScript and JavaScript (including Next.js and Vite web apps, which get preview-server QA with a headless browser), Python, Go, Rust, C/C++, Godot, and Roblox (Rojo/Luau with the Lune test runner). Monorepos are supported with per-package test targets. Repos with no tests at all can still onboard — Keelen runs with an honest no-test posture until its own PRs add a test suite.

Your repo is cloned into an isolated single-use VM that is destroyed when the run ends — no persistent volume, so code and credentials on disk die with the machine. What persists on our side: iteration logs (with secrets automatically scrubbed), PR metadata, and timeline metrics. Your credentials are encrypted at rest under independently rotated keys and are deleted the moment you revoke them.

Copilots autocomplete while your hands are on the keyboard. Chat coding agents do one task per prompt and wait for the next one. Keelen runs a standing process: it holds your roadmap, picks its own next task, works around the clock, verifies every change through test and review gates, recovers from flaky CI and merge conflicts on its own, and accumulates lessons and steering rules that persist across runs — on your own AI subscription, at cost.

Both — the loop is the product, the graph is the machinery. Keelen is not one model in a while-loop: it runs parallel lanes (intake, planning, dev, review, recovery) routed by scheduler policy over durable Postgres state, with circuit breakers on every retry cycle and human checkpoints where you configure them. That is everything graph-based agent frameworks promise — branching, parallelism, checkpointed shared state, human-in-the-loop — running as a crash-safe control plane instead of an in-memory graph.

Yes, per project. Require plan review — a product sign-off and/or a developer sign-off on every plan before any code is written. Set merge to manual and Keelen opens the PR but leaves the merge button to you. Or choose branch-only and it pushes branches without opening PRs at all. You can also pause one project or your whole fleet at any time, and revoke GitHub or model access in one click.

Yes. Keelen ships a public MCP server at https://keelen.ai/mcp over streamable HTTP. Add it to Claude Code, Claude Desktop, Cursor, Windsurf, the Codex CLI, or any MCP client, and 41 tools let you sign up, create projects, submit requests, reorder the roadmap, check project status and resolve escalations from chat. Signup and email verification are themselves tools, so you connect before you have a key. A request submitted over MCP enters the same intake pipeline as one typed into the dashboard.

One iteration = one machine run — a PM planning pass or a dev run. Manual runs and scheduler-triggered runs count the same. If you hit your monthly cap, new runs pause until your cycle renews — or top up instantly with an add-on pack from the billing dashboard.

Yes — the Security scan is a deep whole-repository audit that runs in an isolated VM with a read-only single-repo token. It works a fixed checklist across code, secrets (including git history), dependencies, and infrastructure, and reports ranked findings plus a coverage map with no silent gaps. Any finding can be sent to the loop, which fixes it and ships a tested pull request. Included on every paid plan.

The Controls scan reviews your repository for per-control evidence against Cyber Essentials v3.3, CMMC Level 1, and CMMC Level 2 (NIST SP 800-171 Rev. 2), and the Legal scan maps code observations to commonly cited obligations under GDPR, CCPA/CPRA, COPPA, and TCPA. Both are honestly bounded engineering reviews — not certifications and not legal advice — and both can route code-fixable gaps into the loop as tested pull requests.