Subscription plans
SonarQube Cloud offers three subscription-based plans: Free, Team, and Enterprise, each with varying features and suitable for different team sizes.
SonarQube Cloud’s pricing model is subscription-based: each organization is assigned a subscription plan. Four 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.
OSS (Open Source Software) plan, a free plan for open source organizations that offers unlimited access to branch analysis and pull request analysis. See OSS plan (SonarQube for OSS).
Warning: The legacy paid plan 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 SonarQube Cloud's billing model, see the Billing model page.
Comparison table (Free, Team, and Enterprise)
The table below shows a comparison between features available in the SonarQube Cloud's Free, Team, and Enterprise plans.
General
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.
Maximum number of organization members
5
Unlimited
Unlimited
Enterprise-level hierarchy
You can group several organizations into an enterprise.
DevOps platform binding (GitHub, Bitbucket Cloud, GitLab, Azure DevOps)
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).
Code analysis
Pull request analysis
Only if the target branch is the main branch
Unlimited
Unlimited
Architecture
Visualize current and intended architecture, and raise architecture problems. See Architecture.
Report of security alerts in GitHub
SonarQube Cloud automatically provides feedback about security vulnerabilities inside the GitHub interface itself. See Code scanning alerts.
AI code analysis
Advanced security analysis
Software Composition Analysis (SCA)
Product1 (separate subscription)
Product1 (separate subscription)
Advanced SAST (Static Application Security Testing)
Product1 (separate subscription)
Product1 (separate subscription)
See Advanced SAST
AI-powered code remediation
Remediation Agent (on GitHub and Azure DevOps)
Sonar Agent Essentials2 (annual only)
Sonar Agent Essentials2
Agentic development
Sonar Vortex: context augmentation
Sonar Agent Essentials2 (annual only)
Sonar Agent Essentials2
Sonar Vortex: agentic analysis
Sonar Agent Essentials2 (annual only)
Sonar Agent Essentials2
Agent apps for GitHub
Requires access to GitHub agent apps
Management reporting
Integrations
Webhooks
SonarQube Cloud supports the configuration of webhooks, allowing you to send automatic notifications to external services of analysis activity. See Webhooks.
Enterprise security
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 Using permission 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 Introduction to 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 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 Granting permissions to users
1) These products require a separate subscription and are not included in your Team or Enterprise plan. To subscribe, see Subscribing to the Advanced Security product article for details.
2) Requires a separate Sonar Agent Essentials subscription. See Agent Centric Development Cycle for details.
Note: ABAP, APEX, COBOL, JCL, PL/I, and RPG languages are only supported with the Enterprise plan. See the Supported languages page for more information.
OSS plan (SonarQube for OSS)
If you are part of an open source organization, you may be interested in the OSS plan. It lets you analyze an unlimited number of public repositories but no private projects. Advanced features are also available, as described in the table below. Note that all legacy free organizations have been moved to the OSS plan. To sign up, see Signing up for OSS. To move your OSS organization to Free, see the Moving from OSS to Free page.
Maximum number of organization members
Unlimited.
Code analysis
Languages
All languages supported in the Team plan. See Supported languages.
Branch analysis
Unlimited. For more information about the feature, see Branch analysis.
Pull request analysis
Unlimited.
For more information about the feature, see Pull request analysis.
Custom quality profiles
Custom quality gates
Advanced SAST (Static Application Security Testing)
See Advanced SAST.
Integrations
Webhooks
SonarQube Cloud supports the configuration of webhooks, allowing you to send automatic notifications to external services of analysis activity. See Webhooks.
User administration
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 Projects Management page.
GitHub member synchronization
SonarQube Cloud synchronizes automatically organization members with GitHub. See GitHub member synchronization.
DevOps platform authentication
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 Using permission templates.
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). By default, the enterprise LOC is shared by all organizations in the enterprise (Shared LOC). You can also allocate an individual LOC limit to one or more organizations within the enterprise (Allocated LOC). The other organizations will share the remaining LOC limit. For more information, see About the enterprise lines of code limit (Shared LOC and Allocated LOC).
Warning: 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.
LOC limit management
You cannot exceed your LOC limit in SonarQube Cloud.
Organization LOC limit: applies to Free and Team plans, and to individual organizations with an Allocated LOC limit under an Enterprise plan. You'll receive a notification as you approach the limit, advising you to upgrade your plan or reduce your projects' LOC.
Enterprise-wide LOC limit: applies to the Shared LOC pool across an Enterprise plan. This notification is not currently supported.
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.
LOC limit application 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.
Organization LOC calculation 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.
Related pages
Last updated
Was this helpful?