Code stays on your machine
- CodeRabbit
- Sent to cloud
- Greptile
- Sent to cloud
- GitGecko
- Stays local
Other review tools make you choose: ship your code to their cloud, then wade through findings with no proof behind them. GitGecko runs where your code already lives. Deterministic rule checks fire first so you see provable facts before a single AI opinion, and it never bills you per review.
npx gitgecko@latestFree and unlimited · no cloud account · first review in under a minute
The noise, the missing proof, the surprise bill. Each one is structural, not a setting.
Reviews run on your machine through the agent you already have (Codex, Claude Code, or OpenCode). Nothing is uploaded. No account. SaaS-only reviewers cannot do this at any price.
Local-first execution
Rule checks run first and tag every finding with its source, so you can tell what is provable from what the model suggested. The rule layer cannot hallucinate: same input, same result, every time.
Source-tagged findings
Findings pulled from a single changed line are how real bugs slip through. GitGecko reads the surrounding code: the function in the next file, the type across the module. Ask the whole repo a question, no diff required.
Repository-grounded review
The fastest way to lose trust in a reviewer is the same nitpick every week. Scan once and GitGecko learns your conventions. A rule fires on something intentional? Dismiss it once and it never fires again.
Proactive learning + rule suppression
No seat fees, no per-PR credits, no surprise bill at the end of the month. Point it at any OpenAI-compatible endpoint (LM Studio, Ollama, vLLM) or self-host with Docker. Your model, your bill.
Zero-cost local reviews
Every finding keeps its evidence chain: the rule, the source, the model pathway, the prompt, the retrieved context. The engine is Apache-2.0. Read it, verify it, run it yourself.
Open source + full trace
Example review output
A review should not be a paragraph buried in a comment. It should point to the issue, show why it matters, and leave a trail you can follow back to the evidence.
A rule check caught the replay vulnerability before the agent even read the diff. It is tagged, so you know it is a provable fact, not an AI opinion.
deliveries.has(id) → execute() without prior reserve()@@ handler.ts:42
- execute(delivery)
+ reserve(delivery.id)
+ execute(delivery)Every review opens with a one-line triage summary. Findings tagged 'rule check' are provable; findings from the agent are labeled so you verify them before acting.
CodeRabbit and Greptile are strong hosted reviewers. The differences below are structural: where your code goes, what it costs, and whether a finding can be checked.
| Feature | CodeRabbit | Greptile | GitGecko |
|---|---|---|---|
| Code stays on your machine | Sent to cloud | Sent to cloud | Stays local |
| Free reviews, unlimited | Summaries only | No free tier | Full reviews, unlimited |
| Runs without a cloud account | Required | Required | Not needed |
| Cost per review | $24+/seat/mo | $30/seat + $1/review | Free locally |
| Provable checks before the model | Configured tools | AI review only | Structural + text rules |
| Findings labeled by source | — | — | Provable vs AI-generated |
| Sees beyond the diff | Diff + codebase | Indexed codebase | Local retrieval + repo-wide Q&A |
| Learns your conventions | Plain-English rules | Reads PR comments | Config scan + agent extraction |
| Silence a noisy rule for good | Limited | — | Permanent dismiss |
| Custom rules you write | Plain-English instructions | Plain-English instructions | Text + structural patterns |
| Bring your own model | Enterprise only | — | LM Studio, Ollama, any endpoint |
| A trace behind every finding | Review details | Review details | Per-finding trace |
| Self-host | GHES / Enterprise | Enterprise | Docker |
| Source available | Closed | Closed | Apache core · AGPL UI |
No account to create and no service to onboard. GitGecko works through the coding agent already on your machine.
Run npx gitgecko@latest review in any repository. `npx` always pulls the latest published version, so there is no global install to manage and nothing to set up first.
GitGecko detects claude, codex, or opencode on your PATH. Each agent keeps its own account, credentials, and model settings. You never hand your code to a new service.
Provable rule checks run first, then the agent handles the judgment calls. Every finding carries severity, location, evidence, and its source, so you can check the work, not take it on faith.
Local review is free and unlimited today, no account required. Hosted plans are still private preview.
Full local review, free forever. No card, no account.
Hosted review for active teams. Private preview.
High-volume hosted review. Private preview.
Governed deployment with a custom contract.
Free is the plan you can use today, no account required. No surprise seat charges. No per-review overages. No bill for retries. Local-first means there is no bill to send. Hosted plans are private preview: the quota ladder above is the current product contract, not an active checkout promise. Read the enterprise path
HIPAA, SOC 2, FedRAMP, GDPR. For regulated teams, local-first is not a preference. It is a compliance boundary. CodeRabbit asks $15,000 a month and 500 seats for self-hosted review. Greptile offers no local option at any tier. GitGecko runs where your code already lives, for free.
Reviews run on your machine through your agent. Nothing is uploaded. There is no shared cloud key to exfiltrate, no third-party server to exploit. The August 2025 RCE on CodeRabbit's cloud (Kudelski Security, write access to one million repositories) is structurally impossible here.
Clone the repository, run docker compose up, and review code on your own hardware. No 500-seat minimum. No procurement cycle. No contract negotiation. The same engine the free CLI uses, on your infrastructure.
Point GitGecko at any OpenAI-compatible endpoint (LM Studio, Ollama, vLLM) or your own provider. Your model, your bill, your data residency. No inference routed through a vendor you did not choose.
Run your first review in the next minute. See a provable finding on your own code, then decide if you need a shared hosted workspace.
npx gitgecko@latest