The right model for every review, with costs you can see
MergeHarbor runs every review on its own models, picks the right one for each step, and shows what each review cost. No model keys to supply or pay for.
How it works
Choose a review tier
Standard, Deep or Max, with rules by path or size of change in .mergeharbor.yml. MergeHarbor picks the models for each tier.
Set budgets
Set a monthly credit limit and a per-pull-request cap. When a review would go over, it steps down to a tier that fits.
Track what reviews cost
Each review run shows its cost per step, with the model, tokens and price list used. Cost per review shows the trend over time.
What you get
- Models included in your plan
- Reviews and every other AI feature run on MergeHarbor's model accounts. Your plan's credits cover them, so there is no second bill from a model provider.
- Failover between providers
- If a model provider is unavailable, work moves to another provider your routing settings allow, so reviews still finish.
- Data residency respected
- Where your plan includes data residency, restrict model processing to approved providers and regions. Failover never moves work outside them.
- The right model for each step
- A small model checks risk and verifies findings. A stronger model runs only for risky changes and findings the small model could not settle.
- Costs kept low by design
- Prompt caching, leaving generated and vendored files out of prompts, and batch processing for work that can wait.
- Alerts before you overspend
- Billing admins get alerts at 80% and 100% of the allowance, and see credits per day by tier, developer and repository.
Frequently asked questions
Do we need our own model provider accounts or API keys?
No. The hosted service runs every review on MergeHarbor's own models. Your plan's credits cover model usage, and you never share or pay for model keys. Self-hosted Enterprise installs can use their own model provider accounts instead.
Which models review our code?
MergeHarbor routes each step to the model that fits it, from the providers your routing and data residency settings allow. Each review's cost breakdown names the model every step used.
What happens when a review would go over budget?
It steps down to a tier that fits the monthly credit limit and the per-pull-request cap.
Have another question? Ask our support team
Review every pull request with the context of your whole codebase
Connect a code host in minutes. Reviews start right away, and codebase context is added as indexing completes.