CodeProt logo
Code Review Testing · Security Code Scanning

CodeProt

CodeProt is an AI code review platform connected to GitHub, GitLab and self-hosted GitLab. It reviews pull requests automatically, scans entire repositories for vulnerabilities and bugs, and enforces custom quality rules across development teams of any size.

Active Free plan · Free trial Freemium API available 13+ Verified by Guidaio
Overview

What is CodeProt?

CodeProt is an AI code review platform that plugs into a team's version control system. Its terms describe it as a tool offering insightful, line-by-line feedback on code changes, suggesting improvements and corrections; its own comparison page is more ambitious, positioning it as the team's quality gatekeeper, providing not just code review but precise quality governance, explicitly set against LLM-powered IDEs (an umpire rather than a player) and against CodeRabbit, which it judges noisy and short on governance.

The product rests on four blocks. Pull request review analyzes each PR for quality, security vulnerabilities, performance and test coverage, and can also write the title, change type, summary and labels. Reviews run through a multi-agent mechanism working several dimensions in parallel with cross-validation, and read the diff together with its context rather than the changed lines alone; suggestions stay inside the modified scope and arrive as a directly submittable patch. Repository scanning adds full static analysis, scheduled daily, weekly or on a custom rhythm, running language-specific linters and SAST tools: ESLint and Stylelint, Pylint and Checkov, PMD, PHPCS, Cppcheck, Scalastyle, HTMLHint, ShellCheck. Pre-commit review happens in the IDE through an MCP server exposing four tools to MCP-compatible editors such as Cursor. Rule governance ties it together: rules and thresholds inherited across organization, repository and branch, merge blocking against a baseline, exemptions submitted for approval, and an audit trail.

It connects to GitHub (OAuth plus a GitHub App), GitLab.com (OAuth) and self-hosted GitLab (instance URL plus an administrator personal access token). Announced language coverage includes Vue, TypeScript, Python, Java, C#, C++, C, Go, Rust, Ruby, PHP and Swift. Findings land in a dashboard with summary cards, PR progress cards and recently completed reviews, filterable by repository and date range, and can be pushed to Jira, Linear or Leiga or announced on Slack and Microsoft Teams.

The headline numbers — 94% accuracy on critical issues, 87% less noise, 3.2x more actionable insights per comment, 60% less review time, and a 4.8/5 rating from 150 reviews — are published by CodeProt itself, with no method and no independent source; the homepage testimonials and case studies name no real company.

What it does

  • Review pull requests automatically for code quality, security vulnerabilities, performance, test coverage and review effort
  • Scan an entire repository with static analysis to surface vulnerabilities, bugs, duplication and architectural debt
  • Offer one-click code suggestions delivered as a patch limited to the changed diff
  • Generate pull request titles, change types, summaries and labels without human input
  • Review local changes inside an MCP-compatible IDE before the commit is even made
  • Create and track Jira, Linear or Leiga issues straight from suggestions and scan results
  • Enforce review rules written in plain language at organization, repository or branch level, with blocking thresholds and traceable exemptions
Audience

When to use CodeProt / When not to

A quick filter to help you decide if CodeProt is the right fit.

When to use CodeProt

  • Solo developers and students starting with AI-assisted code review, who can stay on the permanently free plan
  • Professional developers and small teams on early-stage or service projects, who need unlimited pull request reviews for a low monthly fee
  • Engineering managers and tech leads of growing teams looking for advanced code quality metrics and dashboard reporting
  • CTOs, VPs of Engineering and DevSecOps leads who need rule governance, blocking merge thresholds and an on-premise option
  • Teams working on a self-hosted GitLab instance, which CodeProt supports alongside GitHub and GitLab.com

When not to use CodeProt

  • Teams on Bitbucket, Azure DevOps, SVN or Mercurial: only GitHub and GitLab are supported, with more platforms merely announced as future work
  • Anyone expecting whole-repository static analysis at no cost, since repository scanning is a premium feature limited to paid subscriptions
  • High-volume open source maintainers who would exceed the free plan's ceiling of 50 pull requests per month
  • Buyers whose procurement requires documented GDPR compliance, a data processing agreement or named hosting locations, none of which the site provides
  • Users looking for a mobile app, a browser extension, a non-English interface, or review of design, documents or data rather than code
Get started

How to use CodeProt

A typical end-to-end flow, from setup to results.

  1. Sign in with GitHub or GitLab through OAuth; for a self-hosted GitLab instance, first create an administrator personal access token with the api, read_repository, read_user and email scopes, then supply the instance URL and the token at first login
  2. On GitHub, install the CodeProt GitHub App, choose the organization and select the repositories to add
  3. Use the Sync Repositories button at the top right of the repositories page to refresh the list from GitHub or GitLab
  4. Open the settings icon next to a repository and switch on Auto Review, Auto Describe and Code Suggestions
  5. Set languages and write your own checks in the Language Settings and Code Check Rules tabs, in plain language
  6. Connect issue tracking and notifications in the Integrations settings: Jira (base URL, email, API token), Linear (API key), Leiga (client ID and secret) and Slack via OAuth, choosing channels and trigger events
  7. Submit a first pull or merge request and receive the review comments automatically
  8. Launch a repository scan from the repository list, approve it in the authorization dialog, then filter the results and read the AI suggestions (2 to 5 minutes under 1,000 files, 15 to 30 minutes above 5,000)
  9. Create an MCP application in the user settings to obtain an AppID and secret, then configure your MCP-compatible IDE to review local changes before committing
  10. Follow quality trends in the dashboard and turn findings into Jira, Linear or Leiga issues
Quick read

Pros & Cons

Pros

  • Permanently free plan with unlimited repositories and 50 pull requests per month, plus a 14-day trial on Starter and Pro
  • Low paid entry point at 15 USD per month, or 144 USD per year
  • Source code is never stored permanently: read-only access and an isolated scan environment destroyed after analysis, with TLS 1.3 in transit and encryption at rest
  • Self-hosted GitLab is covered, which the publisher's own comparison table presents as uncommon among competitors
  • Pre-commit review inside the IDE through the MCP server, before a pull request even exists
  • Review rules can be written in natural language and governed across organization, repository and branch, with approved exemptions and traceability
  • Native issue tracking integrations (Jira, Linear, Leiga) with one-click issue creation and follow-up through to resolution

Cons

  • The GDPR is never mentioned anywhere on the site, although the product is sold to development teams that include European ones
  • No certification is displayed (no SOC 2, no ISO 27001, no HIPAA) and no data processing agreement is offered, while the Enterprise plan is sold on enterprise-grade security and compliance
  • No hosting country or region is named: the privacy policy says only "secure data centers" and describes international transfers in generic terms
  • Nothing is published about training models on customer data and no opt-out exists; the third-party AI service that generates the suggestions is never named
  • No postal address and no legal entity: the terms and privacy policy point to a "CodeProt Legal Department" and a "CodeProt Privacy Department", and a single address, support@codeprot.com, answers for support, legal, privacy, the DPO and security incidents
  • Marketing figures cannot be verified: 94%, 87%, 3.2x and a self-declared 4.8/5 from 150 reviews, alongside anonymized case studies and testimonials naming no company
  • Only GitHub and GitLab are supported, repository scanning is reserved for paid plans, and the Enterprise price is not public
Pricing

Pricing & Plans

A permanently free plan is available at no charge. The lowest paid tier is Starter at 15.00 USD per month, or 144.00 USD per year, with a 14-day free trial offered on the Starter and Pro plans. Billing is tiered according to the number of developers and processed by Stripe. Fees are non-refundable except where the law requires otherwise, and price changes are subject to 30 days' notice.

Plan 1
  • Free — 0 USD — unlimited repositories
  • basic summaries for up to 50 pull requests per month
  • community support
  • no static analysis
  • no MCP server
  • no issue tracking integrations
Plan 3
  • Pro — 30 USD per month or 288 USD per year
  • 14-day trial — everything in Starter plus AI suggestions on static scan results and priority support
Plan 4
  • Enterprise — price on request — everything in Pro plus an on-premise deployment option and a dedicated account manager
  • no free trial
Starter footnote
  • the advanced model is prioritized
  • if its quota is temporarily exhausted the system falls back to the standard model and
  • in rare cases
  • returns only a summary
  • with automatic restoration or earlier restoration on request to support@codeprot.com
Prices and plans listed above may evolve. Always check the official pricing page before subscribing.
Trust & Privacy

Data, GDPR & hosting

A consolidated view of how CodeProt handles your data.

GDPR overview

The site never mentions the GDPR. Across every page collected — terms, privacy policy, support and pricing — there is no occurrence of "GDPR" or "General Data Protection Regulation", no legal basis for processing, no Article 27 EU representative, no standard contractual clauses and no data processing agreement. What stands in its place is thinner. A Data Protection Officer is designated in the privacy policy at support@codeprot.com, the same address as the Privacy Officer and general support. The policy grants rights that overlap the European text (access, correction, deletion, portability, restriction) without ever tying them to it. Section 9 says servers sit in "secure data centers" and that data may be transferred and processed outside your country, naming no country. Governing law is the Federal Arbitration Act, US federal law and California state law.

Who owns the data?

Neither the terms nor the privacy policy claim ownership of your code. Accounts are created by connecting a GitHub or GitLab account: you authorize read-only access on your behalf and warrant you hold the rights to grant it. The publisher states it does not store source code permanently — analysis runs in an isolated environment destroyed afterwards, and only structured results are kept (file names, line numbers, vulnerability locations, recommendations, metrics). It does not sell, trade or transfer source code or personal information; sharing is limited to Stripe, cloud infrastructure providers, Slack, GitHub/GitLab, legal obligations and a business transfer. Issue details, never source code, go to an unnamed third-party AI service.

Reuse rights

Nothing in the terms restricts what the customer does with the output. Scan results, suggestions and reports exist for your own use: opening Jira, Linear or Leiga issues, reporting to stakeholders and tracking resolution. The privacy policy adds explicit rights to access, correct, delete, export ("Export your scan results and repository settings") and restrict processing, plus control over which repositories are authorized, revocation of access at any time, an access history, and management of Slack and Microsoft Teams notifications. The counterpart is responsibility: suggestions are supplied as-is, and the terms make you responsible for testing and validating every code change. Acceptable use forbids breaking the law, hateful content, malware, fraud, privacy violations and scraping the service itself.

Data retention & training

Retention summary
Source code is not kept: temporary copies are deleted immediately after the scan, the scan environment is destroyed after each use, and access lasts only as long as the active scan. Results are another matter — scan reports, quality history and AI suggestions are retained for the life of the account, and the policy states that "All data is deleted within 180 days of account termination". Account information is kept for the duration of the account plus any applicable statutory periods, while payment records follow financial obligations. You may request deletion of your account and its associated data at any time. Anonymization and pseudonymization are never mentioned, so there is no stated middle ground between retention and deletion.
Subprocessors disclosed
Yes
GDPR contact

Hosting summary

CodeProt names no hosting country. The privacy policy states only that its servers are located in "secure data centers" and that personal information may be transferred to and processed in countries other than your own, with a general commitment that such transfers comply with applicable data protection laws. No region, no cloud provider and no data residency option is disclosed; section 6.1 refers to cloud infrastructure providers without identifying them, and no European region is offered. What is documented is the handling rather than the location: analysis runs in isolated containers destroyed after each scan, traffic is protected by TLS 1.3, data at rest is encrypted with standard encryption, and access tokens are stored encrypted. On the legal side, the terms place the contract under the law of the State of California. As an indication only, the public website resolves to 34.54.94.124, an anycast address announced by Google LLC (AS396982) and geolocated in the United States — that describes the marketing site, not necessarily where customer data is processed.

Watch-outs

Things to keep in mind

Risks and trade-offs to weigh before adopting CodeProt.

  • CodeProt receives read access to entire repositories through OAuth; the exposure depends on the scope you grant, repository by repository, and it is easy to authorize more than is needed
  • A self-hosted GitLab instance requires an administrator personal access token carrying the api scope — a broad privilege handed to a third party
  • Issue details, and therefore fragments of code context, are sent to an unnamed third-party AI service, so its jurisdiction and its policies cannot be assessed
  • Accepting one-click patches without reading them quietly replaces human review and erodes the very skill growth the publisher claims the tool delivers
  • Suggestions are provided as-is: the terms state they must be reviewed by qualified developers and that testing and validating every change remains your responsibility
  • No hosting country, no GDPR mention, no data processing agreement, no postal address and no identified legal entity: recourse in a dispute would be difficult, and a single contact address also handles security incidents
  • The advertised performance figures (94%, 87%, 3.2x) and the 4.8/5 rating are self-declared with no published method, and the free plan's ceiling of 50 pull requests per month can create a false sense of continuous coverage
Setup

Setup & Integrations

Technical difficulty

Low for most users. On GitHub, an OAuth sign-in followed by installing the GitHub App and picking repositories takes a few minutes with no technical configuration; GitLab.com needs OAuth alone, and the site promises setup "in minutes". Enabling reviews is a matter of checkboxes per repository, and review rules are written in plain language rather than code. Two paths ask more: a self-hosted GitLab instance requires an administrator personal access token with four scopes, and the MCP server requires creating an application, then editing the IDE configuration file. Nothing is installed locally.

Deployment

Web appAPISlack app

Integrations

GitHub GitLab Self Hosted GitLab Jira Linear Leiga Slack Microsoft Teams Cursor ESLint Stylelint Pylint Checkov PMD PHPCS Cppcheck Scalastyle HTMLHint ShellCheck

Supported languages

English
Company

Behind CodeProt

Company name
CodeProt
Founded
10/07/2025
Country of origin
🇺🇸 United States
UBO
INFORMATION_NOT_FOUND
UBO country
INFORMATION_NOT_FOUND
Domain registrar country
🇨🇳 China
Legal contact
Support contact
Official links

Resources

All the official URLs gathered for verification and reference.

Compare

Alternatives

Tools that compete with or complement CodeProt.

C CodeRabbitC Cursor
FAQ

Frequently asked questions

What is CodeProt?
CodeProt is an AI-driven code review tool that connects to your version control system. It runs automated reviews of pull requests, writes pull request descriptions and suggests improvements, with line-by-line feedback on code changes.
Which version control systems does it support?
GitHub and GitLab, including self-hosted GitLab instances. The publisher's FAQ states that support for additional version control systems is planned for the future, so Bitbucket, Azure DevOps, SVN and Mercurial are not covered today.
Which programming languages are covered?
The site announces Vue, TypeScript, Python, Java, C#, C++, C, Go, Rust, Ruby, PHP and Swift, plus "many more". Static scanning runs language-specific tools such as ESLint and Stylelint, Pylint and Checkov, PMD, PHPCS, Cppcheck, Scalastyle, HTMLHint and ShellCheck.
Is my source code stored?
The privacy policy states that source code is never stored permanently. Access is read-only, analysis happens in an isolated environment destroyed after each scan, and only structured results are retained: file names, line numbers, vulnerability locations, recommendations and metrics.
How long is my data kept?
Scan reports, quality history and AI suggestions are retained for as long as the account is active. The privacy policy states that all data is deleted within 180 days of account termination, and deletion can be requested at any time.
Is there a free plan and a free trial?
Yes to both. The free plan is permanent and offers unlimited repositories, basic summaries for up to 50 pull requests per month and community support. A 14-day free trial is available on the Starter and Pro plans, but not on Enterprise.
How does billing work and what does it cost?
Pricing is tiered based on the number of developers: Free at 0 USD, Starter at 15 USD per month or 144 USD per year, Pro at 30 USD per month or 288 USD per year, and Enterprise on request. Payments are processed by Stripe and fees are non-refundable except where the law requires otherwise.
Can I use CodeProt inside my IDE?
Yes. Creating an MCP application in the user settings provides an AppID and a secret, which configure an MCP-compatible IDE such as Cursor. The MCP server exposes four tools, including review of local diff changes before committing.
Does the site address the GDPR?
No. Neither "GDPR" nor "General Data Protection Regulation" appears anywhere on the site, and no data processing agreement or EU representative is mentioned. A Data Protection Officer is nonetheless designated in the privacy policy, at support@codeprot.com.
How long does a repository scan take?
The support centre gives 2 to 5 minutes for projects under 1,000 files, 5 to 15 minutes between 1,000 and 5,000 files, and 15 to 30 minutes above 5,000 files. Repository scanning is a paid feature.
Conclusion

Should you pick CodeProt?

CodeProt is unusually complete for a product this young: pull request review, whole-repository scanning, pre-commit review in the IDE through an MCP server, plain-language rule governance and native Jira, Linear and Leiga integrations, all reachable from a readable, low price ladder — free, 15 USD, 30 USD, then Enterprise on request, with a 14-day trial on the paid tiers. Its claimed differentiator is not maximum coverage but noise reduction: fewer and better comments, and merge gates a team can actually govern.

The weak spot is compliance documentation. The GDPR is never mentioned, no certification is displayed, no data processing agreement is offered, no hosting country or region is named, no postal address or legal entity is published, and one email address, support@codeprot.com, answers for support, legal, privacy, the Data Protection Officer and security incidents. For a European team or any enterprise buyer running a vendor review, that list is likely to be a blocker before the product itself is judged.

Youth explains part of it. The domain was registered on 21 May 2025 and first archived on 10 July 2025, and residual inconsistencies remain visible: structured data still advertises a Professional plan at 19 USD while the live pricing configuration shows 15 and 30 USD, a 2023 publication date sits beside a 2025 founding date, and robots.txt points at a localhost sitemap. The headline figures — 94% accuracy, 87% less noise, 3.2x, 60% less review time and 4.8/5 — are self-declared, backed by anonymized case studies.

The wider picture is a Chinese registrar (Alibaba Cloud / HiChina), United States hosting on Google Cloud, California governing law and displayed partnerships with Leiga and Docuopia. Worth trying on the free plan; worth questioning before signing.