Comparisons

Best AI code review tool in 2026
Finding the right automated code review platform for your team
Log in
Last updated October 2026
Code review has always been one of the most important, and most time-consuming, parts of software development. A thorough review catches bugs before they ship, enforces coding standards across a growing team, and transfers knowledge between engineers who might otherwise work in silos. But manual code review is slow. Reviewers context-switch away from their own work, leave comments that sit unaddressed for hours, and sometimes rubber-stamp pull requests just to keep the queue moving. AI code review tools promise to change that equation by providing instant, consistent feedback on every pull request, freeing human reviewers to focus on architecture, logic, and design rather than style nitpicks and common bug patterns.
The market for AI-powered code review has matured considerably over the past two years. What started as simple linting overlays has grown into a category of sophisticated tools that understand context, learn from your codebase, and provide actionable suggestions that go well beyond what static analysis alone can catch. Some of these tools focus exclusively on the review process, while others bundle review capabilities into broader developer platforms. The right choice depends on your team's size, your language stack, your existing toolchain, and how much you want AI to own versus assist.
This guide covers the five strongest options available today. We evaluated each tool on review quality, language support, integration depth, pricing transparency, and how well it fits into real development workflows. Whether you are a solo developer looking for a free tier or an enterprise team standardizing on a single platform, one of these tools should fit.
For a broader look at how these tools fit into a larger developer workflow, see our roundup of best tools for developer productivity.
CodeRabbit
CodeRabbit has emerged as the dedicated AI code review platform, purpose-built for pull request analysis rather than bolted onto an existing product. While other tools treat code review as one feature among many, CodeRabbit treats it as the entire product, and that singular focus shows in the depth and quality of its reviews.
How CodeRabbit works
CodeRabbit connects to your repository and automatically reviews every pull request as soon as it is opened. The review process goes beyond line-by-line analysis. CodeRabbit builds an understanding of the full change set, summarizing what the PR accomplishes, flagging potential issues, and providing specific suggestions with code snippets you can apply directly. The auto-generated PR summaries alone save reviewers significant time by giving them a clear picture of what changed and why before they dive into the diff.
Security scanning and vulnerability detection. CodeRabbit scans for security issues as part of every review, identifying common vulnerabilities like SQL injection, cross-site scripting, hardcoded secrets, and insecure dependencies. This is not a separate step or a different tool. Security feedback appears alongside functional review comments, which means developers see and address security concerns in the same workflow where they handle all other review feedback.
Learnable style guides. One of CodeRabbit's most distinctive features is its ability to learn your team's coding conventions over time. Rather than relying solely on generic rules, CodeRabbit adapts to how your team writes code. When reviewers consistently accept or reject certain patterns, CodeRabbit incorporates those preferences into future reviews. This means the tool becomes more useful the longer you use it, eventually catching the same issues your senior engineers would flag, but doing so instantly on every PR.
Incremental review updates. When a developer pushes new commits to address review feedback, CodeRabbit re-reviews only the changed portions and updates its comments accordingly. This avoids the noise of redundant feedback and keeps the conversation focused on what still needs attention.
CodeRabbit pricing
CodeRabbit offers a free tier for public repositories, making it accessible to open source maintainers and individual developers working on public projects. For private repositories, the Essentials plan starts at $24 per user per month, covering the core review features most small teams need. The Team plan at $48 per user per month adds deeper configuration, priority support, and more granular controls over review behavior. The Advanced plan at $72 per user per month unlocks the full feature set, including advanced security scanning, compliance reporting, and custom integrations. Enterprise pricing is available on request for organizations with specific requirements around deployment, data residency, or scale.
Who CodeRabbit is best for
CodeRabbit is the strongest choice for teams that want a dedicated, continuously improving AI reviewer rather than a feature embedded in a larger platform. It works particularly well for teams that have established coding standards they want enforced consistently, for organizations where security review is mandatory on every change, and for engineering leaders who want every pull request reviewed thoroughly regardless of reviewer availability. The learning capability makes it especially valuable for growing teams where new engineers need consistent guidance on codebase conventions.
For a deeper look at how CodeRabbit performs across different use cases, see our full CodeRabbit review.
GitHub Copilot
GitHub Copilot started as an AI pair programmer focused on code generation, but it has steadily expanded into code review territory. For teams already embedded in the GitHub ecosystem, Copilot's review capabilities offer a natural extension of a tool many developers already use daily.
How GitHub Copilot approaches code review
Copilot's code review features live directly inside GitHub pull requests. When enabled, Copilot can analyze PR diffs and leave review comments that identify bugs, suggest improvements, and flag potential issues. The experience feels native to GitHub because it is native to GitHub. Comments appear in the same interface where human reviewers leave their feedback, and suggestions can be committed directly from the review thread.
Copilot Chat for code understanding. Beyond automated PR comments, Copilot Chat allows developers and reviewers to ask questions about code changes in natural language. A reviewer who is unfamiliar with a particular module can ask Copilot to explain what a function does, why a particular pattern was chosen, or what the implications of a change might be. This conversational layer is useful for onboarding new team members and for reviewing changes in unfamiliar parts of the codebase.
Integration with the broader Copilot ecosystem. The review features work alongside Copilot's code completion, chat, and CLI tools. A developer who used Copilot to write code can then have Copilot review the resulting PR, creating a feedback loop where the AI assists at every stage of the development cycle. Whether this tight coupling is an advantage or a concern depends on your team's philosophy about AI in the development process.
GitHub Copilot pricing
GitHub Copilot offers a free tier with limited functionality that lets individual developers try the core features. The Pro plan at $10 per user per month provides full access to code completion and chat for individual developers. Pro+ at $39 per month adds higher usage limits and priority access to the latest models. For organizations, the Business plan at $19 per user per month adds administrative controls, policy management, and organization-wide settings. The Enterprise plan at $39 per user per month includes everything in Business plus fine-tuned models trained on your organization's codebase, knowledge bases, and advanced security features.
GitHub Copilot's review limitations
Copilot's review capabilities, while improving rapidly, are still one feature within a much larger product. The review suggestions tend to be most useful for catching common patterns and style issues rather than deep architectural concerns. Teams that need highly customizable review rules, learnable style enforcement, or standalone review infrastructure may find Copilot's review features too lightweight compared to dedicated alternatives. The tool also requires you to be on GitHub, which is not a limitation for most teams but does exclude those using GitLab, Bitbucket, or other platforms.
Who GitHub Copilot is best for
GitHub Copilot is the path of least resistance for teams that already use GitHub and want AI assistance across the entire development workflow, not just code review. If your team values having a single AI tool that helps with writing, understanding, and reviewing code, and if you are comfortable with GitHub's platform, Copilot is a strong default choice. It is less ideal for teams that want a best-in-class, standalone review tool or for those who need deep customization of the review process.
For more on how Copilot fits into a broader development setup, see our GitHub Copilot review.
Sourcery
Sourcery carved out its initial reputation in the Python ecosystem, where it became known for producing clean, idiomatic refactoring suggestions that developers would often accept without modification. The tool has since expanded its language support, but its core strength remains in understanding code quality at a structural level rather than just scanning for bugs.
How Sourcery reviews code
Sourcery integrates into the pull request workflow and provides automated reviews that focus on code quality, readability, and maintainability. Where some tools emphasize catching bugs and security issues, Sourcery emphasizes making code better. Its suggestions often involve restructuring conditionals, simplifying nested logic, replacing verbose patterns with more idiomatic alternatives, and improving naming conventions.
Refactoring-first philosophy. Sourcery's refactoring engine is its distinguishing feature. Rather than simply flagging problems and leaving the fix to the developer, Sourcery provides concrete refactored code that you can review and apply. The suggestions are typically conservative and correct, which builds trust over time. Developers learn to expect that a Sourcery suggestion will compile, pass tests, and be stylistically appropriate for the language.
Quality metrics and scoring. Sourcery assigns quality scores to code changes, giving teams a quantitative view of how their codebase health is trending. These metrics cover complexity, readability, and adherence to language-specific best practices. While no single number can capture code quality, the trends over time can be valuable for engineering managers who want to understand whether standards are being maintained as the team and codebase grow.
IDE integration. In addition to PR reviews, Sourcery provides real-time feedback in popular IDEs. This means developers see suggestions as they write code, not just when they open a pull request. Catching issues earlier in the cycle reduces the volume of review comments and shortens the feedback loop.
Sourcery pricing
Sourcery's free tier covers public repositories and provides basic functionality for individual developers. The Pro plan at $12 per seat per month unlocks the full set of refactoring suggestions, quality metrics, and IDE features for individual use. The Team plan at $24 per seat per month adds team-wide configuration, shared rule sets, and administrative controls. These prices make Sourcery one of the more affordable options in the category, particularly for small teams.
Sourcery's current limitations
Sourcery's Python support remains its strongest offering, and teams working primarily in other languages may find the suggestions less comprehensive. The tool has been expanding its language coverage steadily, but the depth of analysis for JavaScript, TypeScript, and other languages has not yet reached parity with Python. Teams that need equally thorough reviews across a polyglot codebase should evaluate whether Sourcery's coverage meets their needs for each language they use.
Who Sourcery is best for
Sourcery is an excellent choice for Python-heavy teams that prioritize code quality and readability over raw bug detection. It is also well-suited for teams that want AI review feedback to appear in the IDE during development, not just at PR time. The affordable pricing makes it accessible to small teams and startups, and the refactoring-first approach appeals to developers who value clean, maintainable code. Teams working across many languages or those who need heavy security scanning as part of review should consider pairing Sourcery with a complementary tool.
SonarQube and SonarCloud
SonarQube (self-hosted) and SonarCloud (cloud-hosted) represent the established guard of code quality analysis. Sonar has been in the static analysis space for well over a decade, and its tools are deeply embedded in enterprise CI/CD pipelines around the world. The addition of AI-powered capabilities in recent years has brought Sonar into the modern code review conversation, though its approach differs from the newer, AI-native tools.
How SonarQube and SonarCloud work
Sonar's tools analyze code against a comprehensive rule set that covers bugs, vulnerabilities, code smells, and security hotspots. The analysis runs as part of your CI/CD pipeline, scanning every commit or pull request and reporting results through a dashboard or directly in the PR interface. The breadth of Sonar's rule library is one of its key strengths. With support for over 30 programming languages and thousands of individual rules, Sonar can enforce standards across virtually any technology stack.
Quality gates. Sonar's quality gate concept allows teams to define pass/fail criteria for code changes. A quality gate might require that new code has no critical bugs, maintains a minimum test coverage percentage, and introduces no new security vulnerabilities. If a PR fails the quality gate, it can be blocked from merging. This enforcement mechanism is particularly valuable for regulated industries and large organizations where code standards must be maintained consistently across hundreds of developers.
Security hotspot analysis. Sonar identifies code patterns that may represent security vulnerabilities and presents them as "hotspots" for human review. Rather than declaring a finding definitively vulnerable, Sonar highlights areas that need security-focused attention and provides context about the potential risk. This approach reduces false positives while ensuring that security-sensitive code gets reviewed by someone qualified to assess the risk.
Technical debt tracking. Sonar quantifies technical debt by estimating the time required to fix all identified issues. This metric, while imperfect, gives engineering leaders a common language for discussing code quality with stakeholders. The trend over time shows whether the team is accruing or paying down debt, which can inform decisions about dedicating time to refactoring versus shipping new features.
SonarQube and SonarCloud pricing
SonarCloud is free for open source projects, making it a popular choice for public repositories. The Developer edition starts at $30 per month and scales based on the number of lines of code analyzed. Enterprise pricing is available on request and includes advanced features like portfolio management, regulatory reporting, and dedicated support. SonarQube (self-hosted) has its own pricing structure based on the edition and the number of lines of code, with a free Community Edition available for teams that want to host their own instance.
Where Sonar differs from AI-native tools
Sonar's strength is comprehensive, deterministic static analysis. Its rules are well-documented, predictable, and produce consistent results. The AI-powered features that Sonar has added in recent years enhance its capabilities, but the core product remains rooted in traditional static analysis rather than large language model-driven review. This is both a strength and a limitation. Teams that value predictability and exhaustive rule coverage will appreciate Sonar's approach. Teams that want the kind of contextual, natural-language feedback that AI-native tools provide may find Sonar's suggestions more mechanical.
Who SonarQube and SonarCloud are best for
Sonar is the natural choice for enterprises that need proven, battle-tested code quality infrastructure. It excels in regulated industries where audit trails, compliance reporting, and deterministic rule enforcement are requirements rather than nice-to-haves. Teams that have already invested in Sonar's ecosystem and configured their quality gates will find significant value in continuing with the platform, particularly as AI features continue to mature. For teams starting fresh and prioritizing AI-driven review over traditional static analysis, one of the newer tools may be a better fit.
DeepSource
DeepSource positions itself as a modern alternative to traditional static analysis tools, combining automated code review with an autofix capability that can apply corrections without developer intervention. The platform supports a broad range of languages and has built a reputation for a clean, developer-friendly experience.
How DeepSource reviews code
DeepSource analyzes pull requests and reports issues across several categories: bug risk, anti-patterns, performance, security, and style. The analysis is fast, typically completing within seconds of a PR being opened, and results appear directly in the PR interface. DeepSource emphasizes actionable findings over exhaustive reporting, which means fewer false positives and less noise for developers to sort through.
Autofix capabilities. DeepSource's autofix feature can automatically apply corrections for certain categories of issues, creating fix commits that developers can review and merge. The scope of autofix has expanded steadily and now covers formatting issues, simple bug patterns, deprecated API usage, and some security fixes. This capability saves time on routine corrections and ensures that straightforward issues do not linger in the codebase simply because no one prioritized fixing them.
Multi-language support. DeepSource supports Python, JavaScript, TypeScript, Go, Ruby, Java, Kotlin, Rust, C, C++, and several other languages. The quality of analysis varies somewhat by language, with Python, Go, and JavaScript receiving the deepest coverage, but the breadth of support makes DeepSource viable for polyglot teams that need a single tool across their entire stack.
Security scanning. DeepSource includes security analysis as part of its standard review process, identifying vulnerabilities like injection flaws, insecure cryptographic usage, and hardcoded credentials. The security findings are integrated into the same workflow as other review comments, which encourages developers to treat security fixes with the same urgency as functional bugs.
DeepSource pricing
DeepSource is free for public repositories, with generous limits that make it practical for open source projects of any size. The Business plan at $12 per user per month covers private repositories and adds features like priority analysis, custom rules, and team management. Enterprise pricing is available on request and includes SSO, audit logs, dedicated support, and on-premise deployment options.
DeepSource's competitive position
DeepSource occupies an interesting middle ground between traditional static analysis tools like Sonar and AI-native review platforms like CodeRabbit. Its analysis is more modern and developer-friendly than legacy static analysis, but it does not yet offer the same depth of AI-driven contextual review that dedicated AI review tools provide. The autofix capability is a genuine differentiator, though, and the clean interface and fast analysis make it easy to adopt.
Who DeepSource is best for
DeepSource is a strong choice for teams that want modern code quality analysis with minimal setup friction. The free tier for public repositories makes it particularly attractive for open source maintainers, and the affordable Business plan keeps it accessible for small to mid-sized teams. Teams that value automated fixes for routine issues and want a single tool that covers a broad language spectrum will find DeepSource compelling. For teams that need the deepest possible AI-driven review, pairing DeepSource with a tool like CodeRabbit can provide both breadth and depth.
How to choose the right AI code review tool
Selecting the right tool depends on several factors that vary by team. Rather than declaring a single winner, it is more useful to match your priorities to the tool that best addresses them.
Review depth versus breadth
If your primary concern is getting the most thorough, contextual AI review on every pull request, CodeRabbit is the standout choice. Its singular focus on the review process and its ability to learn your team's conventions over time make it the deepest option in the category. If you need broad coverage across code review, code generation, and code understanding, GitHub Copilot provides a wider, if shallower, set of capabilities.
Language stack considerations
Python-heavy teams should strongly consider Sourcery, whose Python analysis remains the best in class. Polyglot teams will find the broadest language support in SonarQube/SonarCloud and DeepSource. CodeRabbit and GitHub Copilot both support a wide range of languages through their underlying AI models, though the quality of suggestions can vary by language.
Budget and team size
For individual developers and small teams, several free tiers are available. DeepSource and Sourcery offer the most generous free options for public repositories. For teams on a tight budget working with private repositories, DeepSource at $12 per user per month and Sourcery at $12 per seat per month are the most affordable paid options. GitHub Copilot Pro at $10 per user per month is also competitive, though it bundles code review with code generation features.
Enterprise requirements
Large organizations with compliance, audit, and governance needs should evaluate SonarQube Enterprise, which has the most mature enterprise feature set in the category. CodeRabbit's Enterprise tier and GitHub Copilot Enterprise also offer enterprise-grade features, though they approach governance from different angles. SonarQube's decade-plus track record in enterprise environments gives it a credibility advantage that newer tools are still building.
Integration and workflow fit
Consider how each tool fits into your existing workflow. If you are on GitHub, Copilot and CodeRabbit both integrate seamlessly. If you use multiple source control platforms, SonarQube, DeepSource, and Sourcery offer broader integration options. The best tool is one your team will use consistently, so integration friction matters more than feature lists.
Frequently asked questions
What is an AI code review tool?
An AI code review tool uses artificial intelligence, typically large language models and static analysis, to automatically analyze code changes in pull requests. These tools identify bugs, security vulnerabilities, style inconsistencies, and performance issues, then provide feedback directly in the PR interface. Unlike traditional linters that check against fixed rules, AI-powered tools can understand context, suggest refactored code, and learn from your team's preferences over time.
Can AI code review tools replace human reviewers?
AI code review tools are best understood as a complement to human reviewers, not a replacement. They excel at catching the kinds of issues that humans often miss due to fatigue or time pressure: security vulnerabilities, subtle bugs, style inconsistencies, and common anti-patterns. Human reviewers remain essential for evaluating architecture decisions, assessing whether the code solves the right problem, and providing mentorship to junior developers. The most effective teams use AI tools to handle the mechanical aspects of review so that human reviewers can focus on higher-level concerns.
How do AI code review tools handle false positives?
False positive rates vary by tool and by the type of issue being detected. Most modern tools have invested heavily in reducing false positives because developers quickly lose trust in tools that cry wolf. CodeRabbit addresses this through its learning capability, adapting to your team's patterns over time. SonarQube allows fine-grained rule configuration to suppress categories of findings that are not relevant to your project. DeepSource emphasizes precision over recall, preferring to surface fewer but more actionable findings. When evaluating a tool, running it against your actual codebase during a trial period is the most reliable way to assess false positive rates for your specific situation.
Do AI code review tools work with private repositories?
Yes, all five tools covered in this guide support private repositories, though pricing differs. CodeRabbit, Sourcery, and DeepSource offer free tiers limited to public repositories, with paid plans required for private repo support. GitHub Copilot's paid plans cover private repositories. SonarCloud requires a paid plan for private repos, while the self-hosted SonarQube can analyze any repository within your infrastructure. For teams with strict data privacy requirements, SonarQube's self-hosted option and CodeRabbit's enterprise deployment options provide the most control over where code is processed.
Which AI code review tool is best for open source projects?
For open source projects, the free tiers from CodeRabbit, DeepSource, and SonarCloud are all strong options. CodeRabbit provides the most comprehensive AI-powered review at no cost for public repos. DeepSource offers broad language coverage and autofix capabilities. SonarCloud provides deep static analysis and quality gate enforcement. Many open source projects use more than one of these tools simultaneously, since the free tiers make it practical to layer multiple forms of analysis.
How long does it take to set up an AI code review tool?
Most modern AI code review tools can be set up in under 30 minutes. The typical process involves connecting your GitHub, GitLab, or Bitbucket account, selecting which repositories to analyze, and configuring basic preferences. CodeRabbit, DeepSource, and Sourcery are particularly quick to set up because they are cloud-hosted and require minimal configuration. SonarQube (self-hosted) takes more effort because you need to provision infrastructure, install the server, and configure your CI/CD pipeline to run the scanner. SonarCloud, the hosted alternative, is much faster to set up.
Can I use multiple AI code review tools on the same repository?
Yes, and many teams do. The tools generally operate independently, each leaving their own comments on pull requests. A common combination is pairing a deep AI reviewer like CodeRabbit with a comprehensive static analysis tool like SonarQube, getting both contextual AI feedback and deterministic rule enforcement. The main concern with running multiple tools is comment noise. If three tools each flag the same issue, the PR can become cluttered. Most tools provide configuration options to adjust their scope, which helps reduce overlap.
Do these tools support languages beyond JavaScript and Python?
All five tools support multiple programming languages, though the depth of support varies. SonarQube and SonarCloud lead in raw language count, with support for over 30 languages. DeepSource covers more than a dozen languages with varying depth. CodeRabbit and GitHub Copilot leverage large language models that can analyze code in virtually any language, though suggestions may be more reliable for widely-used languages with more training data. Sourcery started with Python and is expanding, but Python remains its strongest offering. Check each tool's documentation for the specific languages your team uses.
How do AI code review tools handle security scanning?
Security scanning approaches vary across the category. CodeRabbit includes security analysis as an integrated part of every review, identifying vulnerabilities in the context of the broader code change. SonarQube and SonarCloud provide dedicated security hotspot detection backed by years of rule development, including rules mapped to OWASP and CWE standards. DeepSource scans for common vulnerability patterns and can autofix certain security issues. GitHub Copilot can identify security concerns through its AI model, though its security coverage is less systematic than tools with dedicated security rule sets. For teams with strict security requirements, combining an AI reviewer with a purpose-built security scanner (like Snyk or Semgrep) is common practice.
What is the difference between AI code review and traditional static analysis?
Traditional static analysis tools like early versions of SonarQube apply fixed rules to code. They check for known patterns, enforce formatting standards, and flag violations against a predetermined rule set. The results are deterministic: the same code always produces the same findings. AI-powered code review, as provided by tools like CodeRabbit and GitHub Copilot, uses machine learning models that understand code semantics and context. These tools can identify issues that no fixed rule anticipates, suggest refactored code, explain their reasoning in natural language, and adapt to your team's preferences. The tradeoff is that AI-powered suggestions can occasionally be incorrect or inconsistent, while traditional static analysis findings are reliably reproducible. Many teams benefit from using both approaches.
How much do AI code review tools cost for a team of 20 developers?
At a team size of 20 developers, monthly costs vary significantly. GitHub Copilot Business would cost $380 per month. DeepSource Business would cost $240 per month. Sourcery Team would cost $480 per month. CodeRabbit Essentials would cost $480 per month, with Team at $960 and Advanced at $1,440. SonarCloud pricing depends on lines of code rather than user count, so costs vary by codebase size. Most tools offer annual billing discounts, and some offer special pricing for startups or nonprofits. The right comparison is not just price per seat but the value of developer time saved. Even a modest reduction in review cycle time across 20 developers can justify a significant tool investment.
Are AI code review tools safe for proprietary code?
Reputable AI code review tools take code privacy seriously. CodeRabbit, GitHub Copilot, SonarCloud, DeepSource, and Sourcery all provide documentation on their data handling practices, including whether code is stored, how it is processed, and whether it is used to train models. GitHub Copilot for Business and Enterprise explicitly excludes your code from model training. For organizations with the strictest requirements, SonarQube's self-hosted option processes all code on your own infrastructure, eliminating third-party data exposure entirely. CodeRabbit and DeepSource also offer self-hosted or private cloud deployment options at their enterprise tiers. Review each vendor's security documentation and compliance certifications before connecting proprietary repositories.
What happens to the knowledge in pull requests after they are merged?
Pull requests contain some of the most valuable engineering context: the PR description explains why a change was made, the review discussion captures trade-offs and agreements, and the diff shows exactly what changed. But PRs are ephemeral. They scroll off the page within a week, and the knowledge they contain is effectively lost. Fabric addresses this with self-writing docs that connect to your GitHub repositories and read every merged pull request. Architecture decisions, API changes, migration notes, and system behavior modifications are extracted and filed as structured documentation automatically. Your engineers keep merging PRs the way they always have, and the documentation assembles itself. It pairs well with code review tools because the same PRs that CodeRabbit or Copilot review for quality become the source material for your engineering knowledge base. Learn more about Fabric's self-writing docs.
Which tool provides the fastest review feedback?
DeepSource is typically the fastest, often returning results within seconds of a PR being opened. Sourcery and CodeRabbit also provide near-instant feedback for most pull requests. GitHub Copilot's review suggestions appear quickly because they are generated within the GitHub platform itself. SonarQube and SonarCloud speed depends on your CI/CD configuration and the size of the codebase being analyzed, but well-configured pipelines typically complete analysis within a few minutes. For teams where review speed is critical, the cloud-hosted tools (CodeRabbit, DeepSource, Sourcery, SonarCloud) generally outperform self-hosted alternatives because they maintain always-warm analysis infrastructure.
Compare similar apps and tools:
Evaluating other options? See more comparisons:
Explore more comparions:
Evaluating other options? See more comparisons: