- Home
- Code review software
- Rami Code Review
Rami Code Review
What it is
Rami Code Review automatically examines GitHub pull requests for potential security vulnerabilities, bugs, and code quality issues, then posts findings as review comments. It can review again after new pushes until no findings remain open. Claude Code, Cursor, and Codex can retrieve findings through MCP, apply fixes, and request another review; Rami explains issues but does not change code, leaving merge decisions to the user. Each pull request counts as one review per month regardless of file or finding count, and reruns on that request use no extra quota. Users can rebut findings with evidence, and accepted rebuttals return some review credits. Repository settings can control review language and tone, auto-approval, CI blocking, fix prompts, comment hygiene, and instruction-file use. Merge gates are available on Pro+ and Team+. The free plan includes 2 reviews per day and 20 per month; Pro is $7.00 per month. Pull request diffs and contextual repository data are sent to third-party LLM providers for analysis.
For and against
For
- Reviews GitHub pull requests automatically
- Repeat reviews use no additional quota
- Findings can be rebutted with evidence
- Repository settings control review behavior
- Free plan includes 20 reviews per month
Against
- Works with GitHub
- Rami does not change code
- Pull request data goes to third-party LLM providers
The verdict
Rami automates pull request feedback and supports re-reviews, rebuttals, and configurable repository rules. Teams should consider its GitHub scope and third-party processing of pull request data.
Who it suits
Rami suits solo developers and small teams using GitHub whose code is increasingly written by AI agents. It reports issues for people or agents to address while leaving code changes and merge decisions under user control.
Plans and prices
Free
2/day · 20/month · 10 signup reviews · 3 evidence-based rebuttals/month
Read 11 Oct 2026 · rami.reviews
Pro
100 reviews/month · unlimited evidence-based rebuttals · accepted rebuttals return credits
Read 11 Oct 2026 · rami.reviews
Starter credits
10 credits = 1 review · purchased credits never expire
Read 11 Oct 2026 · rami.reviews
Standard credits
10 credits = 1 review · purchased credits never expire
Read 11 Oct 2026 · rami.reviews
Pro+
225 reviews/month · self-tuning · Check Run merge gates
Read 11 Oct 2026 · rami.reviews
Team
150 reviews per seat, shared across your org · unlimited evidence-based rebuttals
Read 11 Oct 2026 · rami.reviews
Value credits
10 credits = 1 review · purchased credits never expire
Read 11 Oct 2026 · rami.reviews
Team+
275 reviews per seat, shared across your org · self-tuning · Check Run merge gates
Read 11 Oct 2026 · rami.reviews
On the record
- Agent workflow
- Claude Code, Cursor, and Codex can fetch findings over MCP, apply fixes, and request re-reviews.rami.reviews · read 11 Oct 2026
- Data access
- Rami accesses only repositories where its GitHub App is installed, with pull request read/write, contents read-only, metadata read-only, and organization members read-only permissions.rami.reviews · read 11 Oct 2026
- Data retention
- Cached analysis and completed result snapshots are retained for up to 7 days, while review finding lifecycle history is retained for up to 90 days.rami.reviews · read 11 Oct 2026
- Human control
- Rami reports findings and explains them but does not change code; the user decides what gets merged.rami.reviews · read 11 Oct 2026
- Intended users
- Rami describes itself as designed for solo developers and small teams whose code is increasingly written by AI agents.rami.reviews · read 11 Oct 2026
- Merge gates
- Check Run merge gates are available on Pro+ and Team+ plans.rami.reviews · read 11 Oct 2026
- Rebuttals
- Users can rebut findings with evidence; accepted rebuttals return some review credits, and repeated accepted rebuttals can teach Rami repository conventions on eligible plans.rami.reviews · read 11 Oct 2026
- Repository configuration
- A repository config file can control review language, tone, auto-approval, CI blocking, fix prompts, comment hygiene, and repository instruction-file use.rami.reviews · read 11 Oct 2026
- Review quotas
- A pull request counts as one review per month regardless of files or findings, and re-reviews of that PR use no additional review quota.rami.reviews · read 11 Oct 2026
- Review scope
- Rami identifies potential security vulnerabilities, bugs, and code quality issues in GitHub pull request changes.rami.reviews · read 11 Oct 2026
- Security measures
- Rami says it uses encryption in transit and at rest, access controls, and audit logging.rami.reviews · read 11 Oct 2026
- Support
- The privacy policy lists [email protected] for privacy questions and data rights requests.rami.reviews · read 11 Oct 2026
- Third-party processing
- Pull request diffs and contextual repository data are sent to third-party LLM providers for analysis, including OpenAI, Anthropic, Google, OpenRouter, xAI, and AWS Bedrock.rami.reviews · read 11 Oct 2026
- What it does
- Rami automatically reviews GitHub pull requests, posts findings as review comments, and re-reviews after pushes until no findings remain open.rami.reviews · read 11 Oct 2026
