SonarQube Enterprise Edition usage and billing policy
SonarQube Enterprise Edition usage in SHIP-HATS is measured based on the number of Lines of Code (LOC) analysed.
Each subscription unit corresponds to a defined LOC range. If the LOC analysed during a billing cycle exceeds the subscribed capacity, additional units will be charged.
Scan limits by subscription unit
| Subscription units | Lines of Code (LOC) range |
|---|---|
| 1 | Up to 400,000 LOC |
| 2 | More than 400,000 LOC and up to 800,000 LOC |
| 3 | More than 800,000 LOC and up to 1,200,000 LOC |
Public officers can refer to the SHIP-HATS pricing page using their non-SE GSIB or COMET device.
Example of LOC-based billing
If you subscribe to 1 unit of SonarQube Enterprise Edition, you can scan up to 400,000 LOC.
If the LOC analysed exceeds this limit at any time during the billing cycle, additional units will be charged as shown below.
| Units subscribed | LOC scanned | Units charged |
|---|---|---|
| 1 | Up to 400,000 | 1 unit |
| 1 | More than 400,000 and up to 800,000 | 2 units |
| 1 | More than 800,000 and up to 1,200,000 | 3 units |
If the LOC limit is exceeded at any point during a monthly billing cycle, the higher unit rate will apply for the entire billing cycle.
For example:
- You subscribe to 1 unit.
- On 2 August, your project scans 420,000 LOC.
- On 3 August, LOC is reduced below 400,000.
You will still be charged for 2 units for that monthly billing cycle.
Usage alerts
Subscription Admins receive email alerts when LOC usage approaches the subscribed limit:
| Usage level | Alert frequency |
|---|---|
| 80%–90% | Weekly alerts |
| Above 90% | Daily alerts |
These alerts help agencies monitor usage and avoid exceeding the subscribed capacity.
Recommendations
To manage LOC usage efficiently:
- Use SonarQube Community Edition for experimental projects or supporting branches.
- Reserve Enterprise Edition for production systems or large codebases.
- Monitor LOC consumption regularly.
Subscription Admins can view LOC consumption for projects.
