How is MicroReview different from CodeRabbit?

MicroReview adds a 0-100 risk score per PR, merge blocking on critical findings, a dedicated GitHub Checks API integration with inline annotations, and hardcoded secret detection across 13 patterns. It also starts free and scales to $19/mo per repo vs CodeRabbit's higher per-seat pricing.

Does MicroReview work with private repositories?

Yes. MicroReview works with both public and private repositories on GitHub and GitLab. The GitHub App requests only the minimum permissions needed: read access to code for PR diffs and write access to post review comments and check runs.

What programming languages does MicroReview support?

AI bug detection and secret scanning work on any language. Deep static analysis rules including naming conventions, Spring Boot patterns, and validation checks are available for Java, TypeScript, and Python today with more language-specific rule sets coming soon.

Is my source code sent to AI?

Only the changed lines (diff hunks) from your pull request are sent to the AI, not your entire codebase. Code is sent over HTTPS, is not used to train models, and is retained by the AI provider for at most 30 days for abuse monitoring before deletion.

How much does MicroReview cost?

MicroReview starts free with 2 repos and 50 reviews per month. The Pro plan is $19/mo per repo with unlimited reviews and AI bug detection. The Team plan is $15/mo per repo for 5+ repos with analytics, SSO, and config inheritance.

Blog

Comparisons, engineering insights, and updates from the MicroReview team.

Featured6 min read

Automating PR Reviews: GitHub Actions vs a Dedicated Review Bot

Should you script code review in GitHub Actions or use a dedicated bot? A practical breakdown of cost, maintenance, and what each approach actually catches.

May 28, 2026·MicroReview Team

Featured6 min read

CodeRabbit vs MicroReview: Which AI Code Review Tool Should You Use in 2026?

An honest comparison of CodeRabbit and MicroReview — pricing, features, risk scoring, and which one fits your team better.

May 23, 2026·MicroReview Team

Featured4 min read

Why We Charge Per Repo, Not Per Seat

Per-seat pricing punishes growing teams. Here's why MicroReview uses per-repo pricing and how it saves teams 80% compared to alternatives.

May 23, 2026·MicroReview Team

All Articles

How to Stop Secrets From Leaking Into Your Git History

Hardcoded API keys and tokens are one of the most common — and most expensive — security mistakes. Here's how to catch them before they ever reach your main branch.

May 27, 2026
5 min read

5 Bugs AI Code Review Catches That Humans Miss

Real examples of bugs, secrets, and risky patterns that slip through human code review but get flagged by AI — from hardcoded credentials to null pointer risks.

May 23, 2026
5 min read