FAQ
Comparison
How is LiveReview different from CodeRabbit?
LiveReview stands out from CodeRabbit in four key ways: pricing, usage, transparency, and team standardization.Predictable Pricing
LiveReview starts free with 30k LOC per month. Paid usage then scales through fixed monthly bands: 100k LOC for $32, 200k for $64, 400k for $128, 800k for $256, 1.6M for $512, and 3.2M for $1024. Paid plans keep users unlimited, so the bill tracks reviewed workload instead of headcount. CodeRabbit charges per seat, so cost rises as the team grows even when workload does not.
Usage Limits
LiveReview's main limit is monthly reviewed LOC. Within that envelope, teams can review across unlimited users and unlimited repositories. CodeRabbit applies hourly rate limits per developer per repository, which makes throughput harder to predict.
Transparency
LiveReview is source-available, meaning you can browse the entire codebase from GitHub, check the security scanning reports, and see exactly what is running under the hood. CodeRabbit does not offer anything like this.
Team Standardization
Regardless of what editor or operating system your team members use, LiveReview enforces code quality at the git level. Every line of code pushed to production goes through LiveReview's analysis, ensuring that code standards and quality are maintained across the entire organization - something none of the other code review tools currently provide.
How is LiveReview different from GitHub Copilot review?
Predictable PricingLiveReview starts free with 30k LOC per month. Paid plans then move through fixed monthly reviewed-LOC bands: 100k for $32, 200k for $64, 400k for $128, 800k for $256, 1.6M for $512, and 3.2M for $1024. Paid plans keep users unlimited, so cost stays tied to review workload. GitHub Copilot charges per user, so the bill rises with headcount rather than the amount of code reviewed.
Usage Limits
Copilot caps premium requests at 300 in the Pro plan, whereas LiveReview's main limit is monthly reviewed LOC and paid plans keep review capacity available across unlimited users and projects inside that envelope.
Team Standardization
Copilot is limited only to GitHub - if your team uses GitLab, Gitea or Bitbucket, you would need separate products. LiveReview works across GitHub, GitLab, Gitea, Bitbucket and Azure DevOps through unified Git-level integration with no additional setup.
How is LiveReview different from SonarQube?
LiveReview stands out from SonarQube in two key ways: transparency and setup.Transparency
SonarQube's Community Edition is source-available but comes with limited features, while the Developer and Enterprise editions are closed. LiveReview's entire codebase is source-available - you can check out all the core functions directly from GitHub.
Setup
For teams using SonarQube server, setting up and maintaining the server can be a burden due to its resource intensity and dependency management overhead. With LiveReview, you can self-host on your own infrastructure with a single command in under 5 minutes.
How is LiveReview different from Claude Code?
Pricing & UsageLiveReview starts free with 30k LOC per month. Premium starts at $32 for 100k LOC and scales through fixed monthly bands to 3.2M LOC while keeping users unlimited. That makes spend predictable and directly tied to reviewed code. Claude Code is token-metered, so a few complex reviews can create costs that are much harder to forecast.
Transparency & Privacy
LiveReview is source-available and can be self-hosted in enterprise plan, so you can inspect the code and keep your data within your own network. Claude Code is a closed product that sends your source code to Anthropic's cloud for processing.
Team Standardization
LiveReview enforces code quality at the git level, keeping standards consistent across GitHub, GitLab, Gitea, Bitbucket and Azure DevOps, regardless of which IDE your team uses. Claude Code is a CLI tool built for individual developers to tackle specific tasks, not for enforcing code standards across an entire organization.
Cursor and Antigravity provide in-editor code reviews for AI-generated code. Why do I still need LiveReview?
Organization-wide VisibilityCode review analysis from in-editor tools is only visible to the individual using them. In a team where members use different IDEs, it becomes difficult to enforce common code quality standards across the organization.
Git-level Enforcement
Since LiveReview operates at the Git level, it works regardless of which IDE your team members use, allowing the entire team to follow common practices and maintain consistent code quality - reducing issues that make it to production.
Automated Prevention
Once LiveReview is set up on a team member's machine, it automatically triggers code analysis during commits, catching buggy or non-production-ready code before it gets pushed.
Pricing
Why is LiveReview’s pricing fair compared to other review tools?
Most code review tools charge more as your team grows or as token consumption fluctuates. LiveReview makes the main limit explicit: monthly reviewed Lines of Code (LOC).You can start free with 30k LOC per month. When you need more, the paid ladder is fixed and public: 100k LOC for $32, 200k for $64, 400k for $128, 800k for $256, 1.6M for $512, and 3.2M for $1024.
Paid plans keep users unlimited, so if your team grows but your review workload stays the same, your bill does not suddenly double. That makes LiveReview predictable, workload-anchored, and easier to budget than seat-based or opaque token-based alternatives.
If I have a 1 million line project, will I be charged for all the lines?
No. You are only charged for the code that appears in the reviewed diff, not for the entire repository. A 1 million line project does not mean 1 million lines are billed. Only the code in the actual review diff counts.git-lrc
What data is sent?
Only the staged diff is analyzed. No full repository context is uploaded, and diffs are not stored after review.Can I disable it for a specific repo?
git lrc hooks disable # disable for current repo
git lrc hooks enable # re-enable later
Can I review an older commit?
git lrc review --commit HEAD # review the last commit
git lrc review --commit HEAD~3..HEAD # review a range
How would this be different from existing tools like SonarQube?
Tools like SonarQube are primarily static analyzers and linters. They check code against predefined rules and usually run in the IDE or CI pipeline. Many enterprises use them to enforce quality and security standards across large codebases.
git-lrc focuses on a different layer: Git itself. Instead of analyzing the whole codebase through rule catalogs, git-lrc reviews the actual diffs at commit time. The goal is to help developers understand what changed, catch issues earlier, and attach review signals directly to the commit.
Another key difference is that git-lrc treats review as repository state. The review outcome (reviewed, skipped, vouched) becomes part of the git log, so review decisions are versioned alongside the code.
The main idea is to bring verification directly into Git, so review happens earlier and becomes part of the repository's engineering history rather than something external in CI or dashboards.
If you're interested in the broader idea behind this:
- Conjecture, Criticize, Commit: Bringing Adversarial Refutation into AI-Assisted Software Engineering
- Should Code Review Live Inside Git?
They explain the thinking behind making review a Git-native artifact rather than something that lives only in CI or dashboards.
Security
What data is collected, stored, and used in LiveReview?
When you run a review, LiveReview only sends the diff to the AI model — nothing else. We do not store your code, and we never train any AI models on your code.On the security side, we regularly run scans on our own codebase to catch vulnerabilities before they become a problem. This includes Gitleaks, OSV Scanner, Govulncheck, and Semgrep, all running through GitHub Actions. A Bill of Materials (BOM) is also generated and published with every release so you can see exactly what is inside.
LiveReview is fully transparent — the entire source code is available for you to browse on GitHub. You can review the full security details in the security documentation.
What security scans are running for LiveReview?
We regularly run security scans on our codebase to catch vulnerabilities early. This includes Gitleaks, OSV Scanner, Govulncheck, and Semgrep. You can check the full scan history and logs directly from our GitHub Actions page.How does the self-hosted deployment differ from the cloud deployment in terms of security?
Self-Hosted ModeIn self-hosted mode, your team runs the entire application stack and database, and your infrastructure team controls all data storage, backups, retention, and network access.
Cloud/Provider Integrated
In cloud/provider-integrated mode, LiveReview sends data to configured external provider endpoints for AI inference and Git provider operations.
Check out more information in our deployment models documentation.
How does LiveReview handle security when using a local Ollama model vs a cloud LLM?
Local Ollama ModelWith a local Ollama model, all inference traffic stays within your own infrastructure — nothing is sent externally.
Cloud LLM
With a cloud LLM like OpenAI, Anthropic, or AWS Bedrock, the review payload is sent to that provider's API endpoint.
The choice of model is explicitly configured by the operator, ensuring complete visibility and no surprises.
Can a malicious code comment manipulate or hijack the AI’s review output?
LiveReview has robust guardrails to prevent this. Before sending any data to the AI model, it runs prompt injection detection, neutralizes instruction override phrases (like "ignore previous instructions"), strips hidden characters, and replaces known control tokens. These checks run automatically on every review request.Detailed information is available in our AI risks and mitigations documentation.
Does LiveReview have any guardrails against insecure code suggestions?
AI suggestions are strictly advisory and require human review before any action is taken. Teams can additionally enforce branch protection, CI checks, and mandatory reviewer approvals before merging.LiveReview also sanitizes model output before returning it, redacting sensitive patterns and handling unsafe links or HTML in the response. You can verify this in our guardrail verification documentation.
Does LiveReview provide a Software Bill of Materials (SBOM) for auditing dependencies?
Yes. An SBOM is automatically generated on every release using Syft and published to the GitHub release assets. You can review it at the latest release page.Is LiveReview SOC 2 Type II certified?
LiveReview is not SOC 2 Type II certified at this time. However, the full security documentation, scan history, SBOM, and source code are publicly available for review, giving enterprise buyers direct visibility into the security posture of the product.Integrations
Does LiveReview support Gitea?
Yes. You can connect your Gitea repositories in minutes and start receiving code reviews across all your projects right away.Does LiveReview provide a VSCode extension?
Yes. LiveReview provides a VSCode extension. If you are using Cursor, Antigravity, or any other VSCode-based editor, you can install the LiveReview extension from OpenVSX. Find out more here.Does git-lrc work if I commit through VSCode’s Git UI?
Yes. When you try to commit through VSCode's built-in Git UI, the commit will initially fail — this is expected. git-lrc does not allow a commit to go through until the review is either completed or intentionally skipped.To get it working, stage your files and either run
git lrc review manually in the terminal, or click the eye icon in VSCode's Git tab. Once done, you can either commit directly from the LiveReview UI, or fix the flagged issues, stage the files again, run the review once more, and then commit through VSCode's Git UI as usual.
Does Livereview support PRs created from the GitHub, GitLab, Bitbucket, Gitea, or Azure DevOps UI?
Yes, you can mention the Livereview bot on your GitHub, GitLab, Bitbucket, Gitea, and Azure DevOps PR requests; it will automatically review all the changes and provide feedback. You can also ask further questions or debate with the AI.Technical
How are LiveReview and git-lrc different?
LiveReviewLiveReview is the complete platform — it includes the dashboard, organization-level code review tracking, PR integration across GitHub, GitLab, Bitbucket, Gitea, and Azure DevOps, and the full suite of features for managing code quality across your entire team.
git-lrc
git-lrc is a lightweight git subcommand (
git lrc review) that brings LiveReview's AI analysis directly into your local git workflow. It runs on your uncommitted code before you push, so you catch issues at the earliest possible point. It installs with a single command and requires no Git provider connection to get started. Learn more about git-lrc here.In short, git-lrc is the fastest way to get started with LiveReview and is focused on the individual developer's local workflow, while LiveReview as a platform is built for the entire organization — tracking reviews, enforcing standards, and giving managers visibility across all projects and teams.
Does LiveReview provide a dashboard for auditing code reviews across an organization?
Yes. The LiveReview dashboard gives you a full view of all triggered code reviews across multiple projects — whether they came from GitHub, GitLab, or were triggered locally through git-lrc. This brings team standardization across your entire organization, giving managers an organization-level view of code quality, while helping developers push better code to production consistently across all projects.Is it possible to customize or give organization-level code review instructions to LiveReview?
Yes. If your team or organization follows specific code review practices, you can add them as instructions directly from the LiveReview dashboard. LiveReview will then check and verify that those standards are met on every code review.What is LOC in LiveReview?
LOC stands for Lines of Code. In LiveReview pricing, it refers to the code shown in the reviewed diff, not the total size of your repository.How much LOC is available on the premium plan?
Premium starts at 100,000 LOC per month for $32. Higher paid bands are 200,000 LOC for $64, 400,000 LOC for $128, 800,000 LOC for $256, 1.6M LOC for $512, and 3.2M LOC for $1024. All paid bands keep users unlimited and refresh every month. If 100,000 LOC is not enough, you move to the next fixed workload band instead of buying more seats.Does LiveReview support Python, Java, or other major programming languages?
Yes. LiveReview is powered by large language models rather than a per-language static analyzer, so it isn't limited to a fixed list of languages. It works well with Python, Java, JavaScript/TypeScript, Go, C/C++, C#, Ruby, PHP, Rust, Kotlin, Swift, and most other mainstream languages and frameworks you'll find in a typical codebase. If your team's stack includes multiple languages in the same repository, LiveReview reviews them all in the same PR without extra configuration.Enterprise
What does the enterprise plan offer?
The enterprise plan is built for organizations that need more control, privacy, and flexibility. Here is what it includes:Multiple Organization Support
Manage distinct engineering teams or entities under a single subscription.
SSO & Directory Sync
Connect your internal user directory through SAML or OIDC, so your team can log in without managing separate credentials.
Self-Hosted Deployment
Run LiveReview entirely within your own infrastructure, keeping all your code and review data inside your network.
Custom Domain
Host LiveReview on your own company-branded subdomain.
Full Data Privacy
Complete control over where your code and review data is stored and who can access it.