Subscription plans
On this page
The SonarQube Cloud’s pricing model is subscription-based: each organization is assigned a subscription plan. Three different plans are available:
- Free plan, for small teams. Only basic analysis features are available.
- Team Plan, if you want to benefit from advanced analysis features.
- Enterprise Plan, for larger organizations and teams, and if you want to benefit from the enterprise-level hierarchy and from even more features.
The legacy free and paid plans will soon no longer be supported. We recommend that you migrate your legacy plan organization to the plan that meets your current and future needs. See changing your subscription plan.
For information about the billing model, see the Billing model page.
Comparison table
The table below shows a comparison between the different SonarQube Cloud plans.
- For supported languages, see Languages overview. Note that ABAP, APEX, COBOL, JCL, PL/I, and RPG languages are only supported with the Enterprise plan.
- A SonarQube Cloud plan dedicated to open-source projects will be introduced in 2025. This plan will allow unlimited access to branch analysis and pull request analysis (in the Free plan, this access is limited to the main branch, also for public projects).
| Feature | Free | Team | Enterprise | Note |
|---|---|---|---|---|
| General | ||||
| Analysis of public projects: unlimited number of projects |  | | | See Project concept. |
| Analysis of private projects | Up to 50k LOC | Up to 1.9M LOC | Unlimited (ideal from 5M LOC for the whole enterprise) | The maximum number of lines of code (LOC) in a plan restricts the analysis of private projects in your organization or enterprise. See LOC-based pricing below. |
| Organization onboarding from multiple DevOps platforms (except Bitbucket) | | As an enterprise member, you can import a DevOps organization using any of your DevOps accounts or SSO account (except for a Bitbucket workspace which can only be imported using a Bitbucket account). | ||
| Maximum number of organization members | 5 | Unlimited | Unlimited | |
| Enterprise-level hierarchy | | You can group several organizations into an enterprise. | ||
| Analysis | ||||
| Branch analysis | Only main branch analysis | Unlimited | Unlimited | See Branch analysis. |
| Pull request analysis | Only if the target branch is the main branch | Unlimited | Unlimited | See Pull request analysis. |
| Webhooks | | | SonarQube Cloud supports the configuration of webhooks, allowing you to send automatic notifications to external services of analysis activity. See Webhooks. | |
| Report of security alerts in GitHub | | SonarQube Cloud automatically provides feedback about security vulnerabilities inside the GitHub interface itself. See GitHub code scanning alerts. | ||
| Quality standards | ||||
| Custom quality profiles | | | See Quality profiles. | |
| Custom quality gates | | | See Quality gates. | |
| Code quality assurance for AI generated code (AI Code Assurance) | | | | See AI Code Assurance. |
| Issue resolution | ||||
| AI CodeFix | | | See AI CodeFix. | |
| Management reporting | ||||
| Portfolios | | See Viewing portfolios. | ||
| Security reports | | See Viewing security reports. | ||
| Project PDF reports | | See Viewing project PDF reports. | ||
| User authentication and provisioning | ||||
| GitHub member synchronization | | | SonarQube Cloud synchronizes automatically organization members with GitHub. See GitHub member synchronization in DOP user accounts. | |
| DevOps platform authentication | | | | See DevOps platform user accounts. |
| SSO authentication | | See SSO authentication | ||
| Administration | ||||
| Groups | | | As an organization admin, you can manage custom groups and change the permissions of any group. See User group concept. | |
| Permission templates | | | As an organization admin, you can use permissions templates to manage the default permissions applying to new projects. See Managing the project-related permissions through templates. | |
| Organization-wide project configurations | | As an organization admin, you can define the long-lived branch name pattern, the analysis scope adjustment, and the automatic analysis disabling for new projects at the organization level. See Performing global analysis setup. | ||
| Projects Management page | | As an organization admin, you can manage the projects of your organization on a centralized page: the Projects Management page. See Using the Projects Management page. | ||
| Delegation of the quality profile management permission | | With the Administer Quality Profiles permission, you can authorize users or groups to manage a specific custom quality profile. See Authorizing other users to manage a custom quality profile. |
LOC-based pricing
Your subscription plan determines the maximum number of private Lines of Code (LOC) you are permitted to analyze, in your organization (for a Free or Team plan) or in your enterprise (for an Enterprise plan):
- Free: You can analyze up to 50k LOC in your organization.
- Team: You can choose a LOC between 100k and 1.9M for your organization.
- Enterprise: You can choose any LOC you want for your entire enterprise (ideal from 5M LOC).
You need to ensure that your choice of plan covers all of the LOCs you want to analyze; otherwise, you may not be able to onboard all of your organization's projects.
For enterprises created before 15 July 2025, the LOC limit isn't assigned at the enterprise level but independently for each organization in the enterprise.
LOC limit management
You cannot exceed your LOC limit in SonarQube Cloud. Once you are near your LOC limit, you will receive a notification informing you of this and advising you to upgrade your current subscription plan to a higher LOC limit or to reduce the number of LOC in your projects. This notification is currently not supported for the enterprise-level LOC limit.
You can analyze the same code as often as you like. However, if you try to analyze more LOC than is allowed under your current subscription, SonarQube Cloud will not perform the analysis, and you will also receive an error message clearly explaining the reason for this.
Example
Your organization has a 20,000 LOC license.
When you analyze a project that contains 10,000 lines of code (LOC) once, you have used 10,000 LOC from your organization's license. If you analyze the same project 20 more times, you will still have only used 10,000 LOC from the license.
However, if you then try to analyze a different project that has 15,000 LOC, you will exceed the 20,000 LOC limit of your organization's license and receive an error message.
Used LOC calculation
The LOC used by an organization is calculated by adding up the LOC of each private project analyzed for your organization. The calculation is a measure of the sum of the LOC of the largest long-lived branches for all your projects. It is not a measure of the new code analyzed in a given billing cycle. During calculation, the following are excluded from your LOC count:
- Test code.
- Files excluded from analysis.
- Code in unsupported languages.
- Comments or blank lines.
Example
Your organization has two private projects:
- Project-1 has 500 lines of code on its main branch and 400 on a secondary long-lived branch: its LOC is 500.
- Project-2 has 0 lines of code on its main branch (provisioned but never analyzed) and 200 on a secondary long-lived branch: its LOC is 200.
- The total LOC for your organization is 500 + 200 = 700.
For an enterprise, the total LOC used is determined by summing the LOC used by all its constituent organizations.
Related pages
Was this page helpful?
© 2008-2025 SonarSource SA. All rights reserved.
