Subscription plans
The SonarQube Cloud’s pricing model is subscription-based: each organization is assigned a subscription plan. Three different plans are available for new organizations:
- 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 cannot be purchased anymore.
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 | x | x | x | See Project concept. |
| Analysis of private projects | Up to 50k LOC | Up to 1.9M LOC | Unlimited | The maximum number of lines of code (LOC) in an organization's plan restricts the analysis of private projects. See LOC-based pricing below. |
| Maximum number of organization members | 5 | Unlimited | Unlimited | |
| Enterprise-level hierarchy | x | 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. |
| Custom quality profiles | x | x | See Quality profiles. | |
| Custom quality gates | x | x | See Quality gates. | |
| Webhooks | x | x | 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 | x | SonarQube Cloud automatically provides feedback about security vulnerabilities inside the GitHub interface itself. See GitHub code scanning alerts. | ||
| Issue resolution | ||||
| AI CodeFix | x | x | See AI CodeFix. | |
| Management reporting | ||||
| Portfolios | x | See Viewing portfolios. | ||
| Security reports | x | See Viewing security reports. | ||
| Project PDF reports | x | See Viewing project PDF reports. | ||
| User authentication and provisioning | ||||
| GitHub member synchronization | x | x | SonarQube Cloud synchronizes automatically organization members with GitHub. See GitHub member synchronization in DOP user accounts. | |
| DevOps platform authentication | x | x | x | See DevOps platform user accounts. |
| SSO authentication | x | See SAML SSO user accounts. | ||
| Administration | ||||
| Groups | x | x | As an organization admin, you can manage custom groups and change the permissions of any group. See User group concept. | |
| Permission templates | x | x | 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 | x | 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 | x | 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 Delegating permission to manage quality profiles in Managing quality profiles. |
Legacy free and paid plans
This paragraph explains what happens with existing organizations that are on the legacy Free plan or Paid plan.
Organizations on the legacy free plan
In the first instance, your organization can stay on the legacy Free plan. At some point, you’ll have to migrate your organization to the new Free plan or upgrade it to the Team plan. For more information, see Migrating to the new Free plan or Upgrading to the Team plan.
Organizations on the legacy paid plan
If your legacy paid plan organization is billed on a monthly basis, it will still benefit, for a given period, from some features that were moved to the Enterprise plan:
- Report of security alerts in GitHub.
- Support of the ABAP, APEX, COBOL, JCL, PL/I, and RPG languages.
- Centralized project management.
See Changing your legacy paid plan on the Changing your subscription plan page.
LOC-based pricing
The Lines of Code (LOC) based pricing 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.
With the Team and Enterprise plans, you can choose the maximum total number of LOC for your organization's private projects.
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.
You cannot exceed your LOC threshold 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.
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.
Related pages
Was this page helpful?
© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARQUBE, and CLEAN AS YOU CODE are trademarks of SonarSource SA.
