> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/instance-administration/license-management/overage-activation.md). # Overage activation How to activate and manage overage for Remediation Agent, Sonar Vortex, Hunter Agent, and Lines of Code (LOC) in SonarQube Server Enterprise and Data Center editions. Activate overage to keep using a product without interruption when your base usage allowance runs out. Usage for each product is tracked in its own consumption unit. The following products support overage: * [Remediation Agent](#how-overage-works), measured in [Remediation Agent](/sonarqube-server/instance-administration/ai-features/remediation-agent.md#what-counts-as-a-suggestion) * [Sonar Vortex](#how-overage-works), measured in [Sonar Vortex](/sonarqube-server/instance-administration/ai-features/sonar-vortex.md#what-counts-as-a-tool-call) * [Hunter Agent](#how-overage-works), measured in [Hunter Agent](/sonarqube-server/instance-administration/ai-features/hunter-agent.md#what-counts-as-a-scan-unit) * [Lines of code](#loc-overage), see [Lines of Code](/sonarqube-server/server-update-and-maintenance/monitoring/lines-of-code.md#calculating-lines-of-code) [Advanced Security](/sonarqube-server/advanced-security/introduction.md) does not support overage. It provides full access without usage limits. Overage is available on Enterprise and Data Center edition instances that use [online license activation](/sonarqube-server/instance-administration/license-management.md) and send daily pings to LicenseSpring. Overage is billed at a higher rate than your base subscription allowance. If you're consistently consuming overage, contact your Sonar account representative to adjust your core subscription. ## How overage works Overage usage is measured against a hard cap you define. When the cap is reached, new analyses are blocked until you raise the cap, the cap resets, or you contact your Sonar account representative to upgrade your existing contract. Invoice creation and cap resets vary by product: | Product | Billing period | Invoice creation | Resets | | ----------------- | -------------- | ---------------- | ------------------------------- | | Remediation Agent | Monthly | Monthly | Start of next calendar month | | Sonar Vortex | Monthly | Monthly | Start of next calendar month | | Hunter Agent | Monthly | Monthly | At the end of the contract term | Overage is billed monthly, based on actual usage above your base allowance. For Remediation Agent and Sonar Vortex, the base allowance and overage tracking reset at the start of each calendar month. For Hunter Agent, both reset only at the end of the contract term. Unused overage capacity does not carry forward to the next reset. The **License manager** page displays your total contract Hunter Agent overage [Hunter Agent](/sonarqube-server/instance-administration/ai-features/hunter-agent.md#what-counts-as-a-scan-unit), but overage billing occurs on a monthly basis. LOC overage is also invoiced monthly, based on the highest LOC peak recorded above your cap that month. Like Remediation Agent and Sonar Vortex, the cap resets at the start of each calendar month. See [LOC overage](#loc-overage) for how it's calculated. ## Activate overage > **Note:** Overage requires [online license activation](/sonarqube-server/instance-administration/license-management.md). If your instance uses a server ID-based license key, overage is not available. Overage requires continuous network connectivity. If your instance loses connectivity, overage usage and new analyses may be blocked until the connection is restored. To activate overage for a product: 1. Go to **Administration** > **Configuration** > **License manager**. 2. In the **Overage limit** column next to the product, select **Activate overage**. 3. Select **Allow overage usage** and enter a value for **Set monthly overage limit**. 4. Select **Next**. 5. Accept the terms and conditions and select **Activate overage**. Overage takes effect immediately. No new license key is required. After your first activation, select **Manage overage** to update your settings. At the start of the following month, you'll receive an invoice for any overage usage by email. If the **Overage limit** column doesn't show **Activate overage** or **Manage overage**, one of the following applies: * Your edition isn't Enterprise or Data Center. * Your instance doesn't use online license activation. * Your codebase has 100 million or more lines of code. * There's a payment issue on your account. Contact Sonar support to resolve it. * Your finance team hasn't agreed to overage billing. Contact your Sonar account representative. ![Active products table on the License manager page.](https://4213461411-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmX1WoFEHhJp6VdSbyTDi%2Fuploads%2Fgit-blob-369bf33a475e11735c7018fd7f3a557514b3387c%2Fsonarqube-server-active-products-table.png?alt=media) ## Track and manage overage The **Overage limit** column shows your current consumption against the overage cap. When the cap is reached, new analyses are blocked until you raise the cap, the cap resets, or you contact your Sonar account representative to upgrade your existing contract. To adjust the cap: 1. In the **Overage limit** column, select **Manage overage** next to the product. 2. Enter a new value for **Set monthly overage limit**. 3. Select **Next**. 4. Accept the terms and conditions and select **Confirm new limit**. The new cap takes effect immediately. ### Deactivate overage Deactivating overage removes the extra cap. The product continues running until your base subscription allowance is consumed; when it's fully consumed, new analyses are blocked until the base allowance resets or you contact your Sonar account representative to upgrade your existing contract. For Remediation Agent and Sonar Vortex, the base allowance resets at the start of the next calendar month. For Hunter Agent, it resets at the end of the contract term. See [How overage works](#how-overage-works). To deactivate overage for a product: 1. In the **Overage limit** column, select **Manage overage** next to the product. 2. Clear the **Allow overage usage** checkbox. 3. Select **Deactivate overage**. Overage used before deactivation appears on your next invoice. You can re-activate overage at any time. ## Overage notifications Administrators receive email notifications when overage consumption reaches the following thresholds: * When overage consumption begins. * 80% of the overage cap is reached. * 100% of the overage cap is reached. ## LOC overage SonarQube Server enforces a Lines of Code (LOC) limit based on your license, shown as **Purchased LOC**. Activate LOC overage to continue analyzing your codebase without interruption if it exceeds this limit. LOC overage is available on Enterprise and Data Center edition instances that use online license activation and send daily pings to LicenseSpring. LOC overage is billed at a higher rate than your base subscription. If you're consistently consuming LOC overage, contact your Sonar account representative to adjust your core subscription. ### How overage is calculated LOC overage is invoiced monthly, based on the highest LOC peak recorded above your **Purchased LOC** limit during that month, not on your average or total usage. The recorded peak resets at the start of each calendar month. If your codebase temporarily grows above the limit and then falls back, billing reflects the highest peak that exceeded the limit, not cumulative excess. Brief spikes are not smoothed or excluded from the calculation. ### Activate LOC overage LOC overage requires continuous network connectivity. If your instance loses connectivity, LOC overage and new analyses may be blocked until the connection is restored. To activate LOC overage: 1. Go to **Administration** > **Configuration** > **License manager**. 2. In the **Lines of code** section, select **Activate overage**. 3. Select **Allow overage usage** and enter a value for **Set monthly overage limit**. 4. Select **Next**. 5. Accept the terms and conditions and select **Activate overage**. LOC overage takes effect immediately. No new license key is required. After your first activation, select **Manage overage** to update your settings. If you don't see **Activate overage** or **Manage overage**, check the following: * **Talk to sales**: your account is not yet entitled to LOC overage. Contact your Sonar account representative to enable it. * **Talk to support**: there is a pricing error on your account. Contact Sonar support to resolve it. * **Not applicable**: LOC overage is not available for your edition or activation method. ### Track and manage LOC overage The **Lines of code** section shows your current LOC overage consumption against the hard cap. When the cap is reached, new analyses are blocked until you raise the cap. To adjust the cap: 1. In the **Lines of code** section, select **Manage overage**. 2. Enter a new value for **Set monthly overage limit**. 3. Select **Next**. 4. Accept the terms and conditions and select **Confirm new limit**. The new cap takes effect immediately. ### LOC overage notifications Administrators receive email notifications when LOC overage consumption reaches the following thresholds: * When LOC overage consumption begins. * 80% of the LOC overage cap is reached. * 100% of the LOC overage cap is reached. If you use online license activation, you can increase the overage cap at any time. See [Track and manage LOC overage](#track-and-manage-loc-overage). For notifications about your base Purchased LOC limit, see the [Lines of Code](/sonarqube-server/server-update-and-maintenance/monitoring/lines-of-code.md#checking-your-lines-of-code-consumption) page. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sonarsource.com/sonarqube-server/instance-administration/license-management/overage-activation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.