Reviews every eligible PR
Severity-ranked inline findings with evidence quotes — not drive-by nitpicks. Suggestions render as committable patches.
Two-pass AI review · validator-gated findings · learns from your team
Every pull request reviewed.
Every finding defensible.
CodeBeaver reads the diff, gathers real repository context, runs deterministic checks and a two-pass AI review, then posts inline findings it can actually defend — and learns from the way your team replies.
Hosted runs on our Worker with your own model keys (BYOK). Self-hosting is free for your whole organisation.
2 passesindependent validator gates every published finding
6 gatesdeterministic checks before the model ever runs
1 commandto self-host the entire stack in your cloud
0 keysthat leave your control — BYOK everywhere
What the beaver does
Not another diff summariser. A reviewer that shows its evidence, respects your merge gate, and gets less wrong over time.
Blocks what actually matters
Secret-leak blocking, custom pre-merge checks, and critical-severity check runs gate the merge before a human ever looks.
Learns your taste
Accepted and disputed findings become learned rules the reviewer applies on your next pull request — per repository.
Fixes with receipts
@codebeaver autofix prepares verified follow-up PRs that only merge after your configured checks pass.
Writes the boring parts
PR descriptions, changelogs, walkthroughs by concern and file, and unit-test generation from the diff.
Knows your codebase
Vectorize-backed semantic search scoped per repository, plus import graphs, likely tests, and linked-issue scope checks.
How it works
From install to merge in three steps. No pipeline changes, no new CI runners.
-
01
Connect your repositories
Install the app with its webhook pointed at the hosted Worker — or run
pnpm selfhost:initto stand up the identical stack in your own Cloudflare account. -
02
Open a pull request
Deterministic gates run first, bounded repository context is gathered, then the primary pass and the independent validator review the change. Findings post inline with evidence.
-
03
Merge with confidence
Reply to findings to teach the reviewer, ask
@codebeaveranything, accept an autofix PR, and merge when the check turns green.
Pricing
Honest today, not aspirational. The hosted tier is in early access; self-hosting is not a trial.
Early access
Hosted
Your model keyswe run everything else
- Zero ops — install and open PRs
- Full pipeline: validator, learning, autofix, dashboard
- Review data in our Cloudflare account
- Per-seat tiers arrive with billing (roadmap)
Forever free
Self-host
Freeyour whole organisation
- One command into your own Cloudflare account
- Identical code the hosted tier runs — auditable
- Your keys in your secret manager, data in your account
- Commercial license only if you resell it
No install
BYOK Action
Freeyour provider key
- Single-pass GitHub Action, SARIF output
- No webhook, no app, no Worker
- Two-minute trial of the workflow
- Upgrade path to the full pipeline
☁️ Hosted or 🏡 self-host?
Same code, same reviewer — the difference is who holds the keys and the ops pager.
| ☁️ Hosted (we run it) | 🏡 Self-host (you run it) | |
|---|---|---|
| Setup | Install and go | pnpm selfhost:init |
| Review data lives in | Our Cloudflare account | Your Cloudflare account |
| LLM keys | Yours — BYOK is the hosted model | Yours, in your own secret manager |
| Dashboard | Hosted dashboard | Your own URL |
| Price | Per-seat BYOK tiers (roadmap) | Free |
| Best for | Teams that want zero ops | Teams with strong feelings about their keys |
Questions, answered
Where does my code go?
The Worker fetches your diff and bounded repository context, sends them to the model provider you configure, and stores findings and review state in the KV namespace of whichever account runs it — ours on hosted, yours when self-hosted. Nothing is retained by model providers beyond their own API policies, and the self-hosted build keeps every byte in your account.
Why two AI passes?
The primary pass reviews with full context; an independent validator then re-examines each candidate finding and drops the ones it can't confirm before anything reaches your PR. That second pass is why CodeBeaver findings arrive with evidence instead of apologies — and each published finding is marked validator-confirmed.
What does "learns your taste" actually mean?
When you accept a finding, dispute it, or resolve a thread, the reviewer records a bounded correction for that repository. Future reviews apply those rules — so the bot that annoys your team about tabs stops, and the one that missed your house pattern for error handling learns it.
Is self-hosting really free?
Yes — BUSL-1.1 with a permanent grant: run it on your own repositories, with your own keys, for as long as you like. The only thing that needs a commercial license is running CodeBeaver for other organisations as a service or product.
Do I need a Cloudflare account?
Not for the hosted tier — GitHub plus a model key is enough. A Cloudflare account (Workers Paid recommended at production volume) is only for self-hosting.
Which models does it support?
Any OpenRouter-compatible endpoint, with a registry-driven provider chain, per-purpose model overrides (review, validator, autofix, chat, describe, changelog), and fallback routes when a provider is down.
Put a very earnest beaver on every pull request.
Install the hosted app today, or audit every line it runs by self-hosting it tomorrow.
🔴 Critical: auth token cached without expiry check · ✅ validator-confirmed
Evidence: refresh path writes
cache.set(user.id, token); the read path on line 61 never validates expiry.Suggested fix: gate the cache read on
expiresAt > Date.now()and fall through to refresh otherwise.Human review effort: 🟡 Medium (~20 min) · Next action: address the findings before merging · 6 candidates generated → 2 survived validation and policy filters