# Subscription plans The SonarQube Cloud’s [pricing model](https://www.sonarsource.com/plans-and-pricing/sonarcloud/) 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 plan, a free plan for open source organizations that offers unlimited access to branch analysis and pull request analysis. {% hint style="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-plan](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-subscription/changing-plan "mention"). {% endhint %} For information about the billing model, see the [billing-model](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-subscription/billing-model "mention") page. ## Comparison table (Free, Team, and Enterprise) The table below shows a comparison between the SonarQube Cloud's Free, Team, and Enterprise.

Feature	Free	Team	Enterprise	Note
General
Analysis of public projects: unlimited number of projects				See projects
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.
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).
Automatic GitHub repo import				See auto-import-new-repos
Bulk import of all repositories (in beta, only for GitHub)				See #bulk-import
Code 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				See understanding-quality-profiles
Custom quality gates				See introduction-to-quality-gates
Report of security alerts in GitHub				SonarQube Cloud automatically provides feedback about security vulnerabilities inside the GitHub interface itself. See GitHub code scanning alerts.
AI code analysis
AI Code Assurance				See ai-code-assurance
Advanced security analysis
Software Composition Analysis (SCA)			Add-on¹	See #sca
Advanced SAST (Static Application Security Testing)			Add-on¹	See #advanced-sast
AI-powered code remediation
AI CodeFix				See ai-codefix
Remediation Agent (on GitHub only)				See ai-agents
Management reporting
Portfolios				See viewing-portfolios
Security reports				See project-security-reports
Project PDF reports				See project-pdf-reports
Integrations
Jira Cloud				See jira-cloud
Slack				See integration-overview
JFrog Evidence Collection				See jfrog
Webhooks				SonarQube Cloud supports the configuration of webhooks, allowing you to send automatic notifications to external services of analysis activity. See webhooks.
User authentication and provisioning
GitHub member synchronization				SonarQube Cloud synchronizes automatically organization members with GitHub. See GitHub member synchronization in devops-platform-authentication
DevOps platform authentication				See devops-platform-authentication
SSO authentication				See sso
Enterprise security
Scoped Organization Token (SOT)				#about-scoped-organization-tokens
Audit logs				See audit-logs
IP allow list restriction				See ip-allow-lists
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 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 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-quality-profile

1\) Enterprise's add-ons require a separate subscription to your Enterprise license. {% hint style="info" %} ABAP, APEX, COBOL, JCL, PL/I, and RPG languages are only supported with the Enterprise plan. See [overview](https://docs.sonarsource.com/sonarqube-cloud/discovering-sonarcloud/overview "mention") for more information. {% endhint %} ## OSS plan (SonarQube for OSS) If you are part of an open source organization, you may be interested in the OSS plan. This plan is a free plan that allows you to analyze an unlimited number of public repositories but *no private project*, and to benefit from advanced features as described below. Note that all legacy free organizations have been moved to the OSS plan.

Feature	Description
Maximum number of organization members	Unlimited.
Code analysis
Languages	All languages supported in the Team plan. See overview.
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	See understanding-quality-profiles.
Custom quality gates	See introduction-to-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 projects-management-page.
GitHub member synchronization	SonarQube Cloud synchronizes automatically organization members with GitHub. See github-member-synchronization.
DevOps platform authentication	See 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 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-enterprise-loc-limit](https://docs.sonarsource.com/sonarqube-cloud/managing-enterprise/managing-the-lines-of-code-within-your-enterprise#about-enterprise-loc-limit "mention"). {% hint style="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. {% endhint %} ### 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 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.

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 * [billing-model](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-subscription/billing-model "mention") * [signing-up-for-plan](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-subscription/signing-up-for-plan "mention") * [getting-started-with-enterprise](https://docs.sonarsource.com/sonarqube-cloud/getting-started-with-enterprise "mention") * [changing-plan](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-subscription/changing-plan "mention") * [updating-billing-payment-details](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-subscription/updating-billing-payment-details "mention") * [viewing-billing-and-usage](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-subscription/viewing-billing-and-usage "mention") * [viewing-taxes-and-invoices](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-subscription/viewing-taxes-and-invoices "mention")