View and manage subscriptions
You can view and manage module subscription details as well as license information directly within your Harness account. This includes monitoring current subscriptions, reviewing license allocations, and adjusting as necessary to meet your organizational needs.
Developer 360 subscriptions
You can subscribe to Harness modules using the Developer 360 subscription model. The Developer 360 subscription offers three plans: Free, Startup, and Enterprise. All plans include Harness AIDA, our AI Development Assistant.
This model spans all modules except Cloud Cost Management, which is on a Cloud Spend model.
The following sections explain how this subscription model works across the various modules on the platform.
Who is a developer?
A Developer contributes to code development, deployment, security, maintenance, optimization, or all other technical activities related to software code that is managed with Harness.
These users leverage Harness to create code repositories, build, test, secure, and deploy software, conduct chaos experiments, manage SLOs, handle feature flags, and more.
The definition of a Developer (and any associated consumption entitlements) remains consistent across all plans: Free, Startup, and Enterprise.
Modules with direct developer tracking
The following Harness modules are integral to a Developer's daily workflow. Each module requires a separate developer license for every user involved.
- Code Repository (CODE): All users on the Harness Platform who have permission to access Harness CODE module are considered as CODE Developers and consume a license.
- Continuous Integration (CI): All users on the Harness Platform who have permission to access Harness CI module are considered as CI Developers and consume a license.
- Internal Developer Portal (IDP): All users on the Harness Platform who have permission to access Harness IDP module are considered as IDP Developers and consume a license.
- Feature Flags (FF): All users on the Harness Platform who have permission to create / update / delete Feature Flags and/or Delivery Groups, within the Harness FF module, are considered as FF Developers and consume a license.
- Software Engineering Insights (SEI): All users whose actions or artifacts are read from configured Source Code Management or Issue / Project Management tool(s) are considered as SEI Developers and consume a license.
Modules with no direct developer tracking (consumption entitlements)
All other Harness modules (except CCM) are indirectly involved in a Developer's day-to-day workflow, and they track an indirect unit instead of a Developer license. Harness refers to these indirect units as Consumption Entitlements.
In these cases, the Developer license acts as a proxy for granting a predetermined set of consumption entitlements, as explained below.
You have the option to subscribe to additional Consumption Entitlements as needed, with an associated additional cost.
Continuous Delivery and GitOps (CD) Services
CD deploys software services onto infrastructure platforms spanning traditional VMs, Kubernetes, public cloud platforms, serverless functions, and other custom deployment targets. A Service is an independent unit of software you track and manage through Harness CD and GitOps. This typically maps to:
- A service in Kubernetes.
- A containerized service on a cloud (such as AWS ECS, Azure ACS, or Google Container Engine).
- A VM in the traditional VM-based apps.
- Five serverless functions in serverless environments.
CD tracks Service license consumption instead of Developers. All Service licenses are tracked over a last 30 days active window. For more information about CD services and how they are tracked, go to Service licensing for CD.
Feature Flags (FF) Developers and Monthly Active Users (MAUs)
Harness Feature Flags is a feature flag rollout and management module that tracks Developers and MAU (Monthly Active Users) for license consumption.
All users on the Harness Platform who have permission to create, update, or delete Feature Flags and/or Delivery Groups, within the Harness FF module, are considered FF Developers and consume a license. Monthly Active Users (MAUs) represent the unique users seen every month from one or more client-side applications that evaluate various flags managed by Harness.
Service Reliability Management (SRM) Services
SRM helps manage SLOs/SLIs for various services in an R&D organization. A Service is an independent unit of software you track & manage through Harness SRM. This typically maps to:
- A service in Kubernetes.
- A containerized service on a cloud (such as AWS ECS or Azure ACS or Google Container Engine).
- A VM in the traditional VM-based apps.
- Five serverless functions in serverless environments.
SRM tracks Service license consumption, instead of Developers. All Service licenses are tracked over a last 30 days active window.
Chaos Engineering (CE) Services
Chaos Engineering (CE) makes it easy to run chaos experiments across diverse services within an R&D organization, aimed at enhancing their resilience. A Service represents an autonomous software unit managed and tracked through Harness CD and GitOps. This typically maps to:
- A service in Kubernetes.
- A containerized service on a cloud (such as AWS ECS, Azure ACS, or Google Container Engine).
- A VM in the traditional VM-based apps.
- Five serverless functions in serverless environments.
CE tracks Service license consumption, instead of Developers. All Service licenses are tracked over a last 30 days active window.
Infrastructure as Code Management (IACM) Executions
An IACM Execution is counted as every successful IACM stage execution that uses an Infrastructure Provider's apply command (such as terraform apply) and results in resource changes.
IACM tracks Executions license consumption, instead of Developers.
Security Testing Orchestration (STO) Security Scans
A Security Scan is defined as the execution of the Security Testing Orchestration (STO) step within a pipeline. This involves scanning a Target for security vulnerabilities. A target can be a repository, container image, configuration, or live application.
STO tracks Security Scans license consumption, instead of Developers. Security Scans are tracked over a last 30 days active window.
Supply Chain Security (SCS) Supply Chain Executions
A Supply Chain Execution is defined as the execution of the Supply Chain Security (SCS) step in a pipeline. Generating SBOMs, enforcing SBOM policies, generating SLSA provenance, or verifying SLSA provenance are all counted as unique SCS steps.
SCS tracks Supply Chain Executions license consumption, instead of Developers. Supply Chain Executions are tracked over a last 30 days active window.
Included and add-on consumption entitlements
The Developer 360 subscription model includes module-specific consumption entitlements by default.
This means every developer license for a module includes a corresponding consumption entitlement, where applicable.
You can always acquire additional consumption entitlements as needed through add-on purchases.
Included consumption entitlements
| Harness Module | Included Consumption Entitlement |
|---|---|
| Code Repository | Not applicable since Developers are tracked directly |
| Continuous Integration | Not applicable since Developers are tracked directly |
| Continuous Delivery & GitOps | 1 Service for every 3 Developers |
| Feature Flags | 10K MAUs per Developer per month |
| Service Reliability Management | 1 Service for every 3 Developers |
| Chaos Engineering | 1 Service for every 3 Developers |
| Infrastructure as Code Management | 120 Executions per Developer per year |
| Software Engineering Insights | Not applicable since Developers are tracked directly |
| Internal Developer Portal | Not applicable since Developers are tracked directly |
| Security Testing Orchestration | 100 Security Scans per Developers per month |
| Supply Chain Security | 100 Supply Chain Executions per Developers per month |
Add-on consumption entitlements
For every module where a consumption entitlement applies, you can purchase any number of add-on entitlements.
This means you can purchase more:
- Services for CD, SRM, and CE
- MAUs for Feature Flags
- Executions for IACM
- Security Scans for STO
- Supply Chain Executions for SCS
Cloud Cost Management (CCM) Cloud Spend
CCM does not follow the Developer 360 subscription model.
Cloud Spend for CCM is licensed as a Monthly/Annual Cloud Spend that is managed and optimized via Harness. This cloud spend is actively tracked in the CCM module experience and tracked against the licensed cloud spend.
View subscriptions
You can view and manage your Harness module subscriptions in your Harness Account Settings.
In your Harness account, go to Account Settings to view which Harness modules you are currently subscribed to. Subscriptions are shown in the Subscribed Modules section on the Overview page. You can select Manage to go to the Subscriptions page.
Subscriptions page
For Developer 360 module subscriptions, the Subscriptions page displays the the developer license count (Developers), as well as the consumption entitlement, depending on the module's licensing unit.
For example, consumption entitlement for CD could include Services or Service Instances.
For module subscriptions not purchased under a Developer 360 subscription, the Subscriptions page displays the License Count for your module-specific license. For example, for CD this is CD Services or CD Service Instances.
Cloud credits
Currently, the Cloud Credits page is behind the feature flag PL_ENABLE_LICENSE_USAGE_COMPUTE. Contact Harness Support to enable the feature.
For Developer 360 module subscriptions, you can view your cloud credits on the Subscriptions page. In your Harness account, go to Account Settings, then select Subscriptions.
On the Subscriptions page, select Cloud Credits.
Credits & Usage
Credits & Usage enables you to view the following credit information:
- Available Credits: Current balance of active credits remaining to use.
- Month-to-date Credit Usage: Credits consumed month-to-date.
- Next Expiry Date: The next upcoming credit expiration date.
- Credit Overage: Current amount of credit overage. As a courtesy, Harness notifies you when you are running low on cloud credits. For more information, go to Credit allowance by plan tier and Credit overages (overuse).
Credits Breakdown
Credits Breakdown enables you to view your credit usage by organization, project, or resource class. You can also use the date filters to view by a Recommended range, Relative dates, Calendar months, or a selected custom range.
Credits Allocation
Credits Allocation enables you to view the following details for your credit allocation:
- Start Date: The date on which a block of credits were applied to your account.
- Expiry Date: The date on which a block of credits expires.
- Type: The credit type: Free, Team, or Enterprise.
- Quota: The total number or allocated credits.
- Used: Credits consumed during the active credit period.
- The active credit period is the time between the Start Date and Expiry Date for your oldest unexpired credits.
- For free accounts, the credit balance resets at the end of every calendar month. Your Start Date is the first of the month. Your Expiry Date is the end of the month.
- If you purchased additional credits that haven't yet expired, the Start Date for Used Credits is the date that you purchased the additional credits, and the active credit period covers the lifetime of your purchased credits. For example, if you purchase credits in January that last for six months, Used Credits tracks credit usage from January through July, when your purchased credits expire. Therefore, Used Credits could include credits with various expiration dates.
- Available: The number of credits available to use.
- Status: The credit status, Active or Expired.
For more information about Harness Cloud billing and cloud credit consumption, go to Subscriptions and licenses.
Manage subscriptions
You can quickly and securely manage your Harness subscriptions directly through your Harness account any time, including:
- Upgrading your plan.
- Managing payment details and billing admins.
- Viewing license usage data.
- Viewing Harness Cloud credit usage data.
Online subscription management is not available for all modules. If you want to upgrade your subscription for a module that doesn't yet support self-service subscription management, contact the Harness Sales team.
Module subscriptions and licenses
For more information about specific module subscriptions and licenses, go to:
- CI Subscriptions and licenses
- CD Service-based licensing and usage
- FF Subscriptions
- SRM subscriptions and licenses
Cloud Marketplace offerings
For information about Cloud Marketplace subscriptions, go to Cloud marketplace offerings.