Subscriptions and licenses
Developer 360 subscriptions
Customers subscribe to Harness modules using a subscription model called Developer 360. 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?
Every user who contributes to software development, deployment, operations, optimization, is considered a developer on the Harness Platform for the purpose of the Developer 360 subscription model. These users use Harness to create code repositories, build software, test & secure software, deploy software, run chaos experiments, manage SLOs, manage feature flags and more. Note that the definition of a developer (and the consumption entitlements if any) remain the same for all plans, namely Free, Startup and Enterprise.
Modules with direct developer tracking
The following Harness modules are directly involved in a developer’s day-to-day workflow, and hence consume a developer license for every developer involved.
Code Repository (CR)
All users who have permission to access the Harness CR module on the Harness Platform will be considered CR Developers and will consume a license.
Continuous Integration (CI)
All users who have permission to access the Harness CI module on the Harness Platform will be considered CI Developers and will consume a license.
Internal Developer Portal (IDP)
All users who have permission to access the Harness IDP module on the Harness Platform will be considered IDP Developers and will consume a license.
Software Engineering Insights (SEI)
All users read from a configured SCM or Issue Management tool will be considered SEI Developers and will consume a License.
Modules with no direct developer tracking
The following Harness modules are indirectly involved in a developer’s day-to-day workflow and hence track an indirect unit instead of a developer. Harness calls these indirect units as ‘Consumption Entitlements’. In these cases, developer license acts as a proxy for granting a predetermined set of consumption entitlements. Customers can subscribe to more consumption entitlements if needed at an additional cost.
Continuous Delivery & GitOps (CD)
Services: The CD module 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 & manage through Harness CD & GitOps. This will typically map 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
- 6 serverless functions in serverless environments
CD tracks ‘Service’ license consumption, instead of Developers. Note that all Service licenses are tracked over a last 30 day active window. For a detailed understanding of CD services and how they are tracked, go to Service licensing for CD.
Feature Flags (FF)
Developers & Monthly Active Users (MAUs): FF is a feature flag rollout and management module that tracks Developers based on their active engagement with the FF module. Every platform user that actively creates / edits / deletes a flag or a group, is tracked as a FF developer. MAUs or Monthly Active Users represent the unique users seen every month, from one or more client side applications that evaluate various flags managed via Harness.
FF tracks ‘Developers’ and ‘MAU’ license consumption.
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 will typically map 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
- 6 serverless functions in serverless environments
SRM tracks ‘Service’ license consumption, instead of Developers. Note that all Service licenses are tracked over a last 30 day active window.
Chaos Engineering (CE)
Services: CE helps run chaos experiments across various services in an R&D organization, with the goal of making them resilient. A Service is an independent unit of software you track & manage through Harness CD & GitOps. This will typically map 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
- 6 serverless functions in serverless environments
CE tracks ‘Service’ license consumption, instead of Developers. Note that all Service licenses are tracked over a last 30 day active window.
Infrastructure as Code Management (IACM)
Executions: Every successful IACM stage execution that uses an Infrastructure Provider’s `Apply’ command (such as terraform apply) that results in resource changes is counted as an execution.
IACM tracks ‘Executions’ license consumption, instead of Developers.
Security Test Orchestration (STO)
Security Scans: A Security Scan is defined as the execution of the STO step within a pipeline, tracked over a last 30-day active window. This involves scanning an artifact (referred to as the Target), which can be a Repository, Docker image, or a live application, for security vulnerabilities.
STO tracks ‘Security Scans’ license consumption, instead of Developers.
Software Supply Chain Assurance (SSCA)
Supply Chain Executions: A Supply Chain Execution is defined as the execution of an SSCA step in a pipeline, tracked over a last 30-day active window. Generating SBOMs, enforcing SBOM policies, generating SLSA provenance, or verifying SLSA provenance are all counted as unique SSCA steps.
SSCA tracks ‘Supply Chain Executions’ license consumption, instead of Developers.
Cloud Cost Management (CCM)
Cloud Spend: CCM is licensed on 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. As previously noted, CCM does not follow the Developer 360 subscription model.
Included & 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 it applies. Additionally, customers always have the flexibility to buy add-on consumption entitlements, as it applies to their needs.
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 Developer per Month |
| Software Supply Chain Assurance | 100 Supply Chain Executions per Developer per Month |
Add-on consumption entitlements
For every module where a consumption entitlement applies, customers can purchase any number of add-on entitlements. This implies that customers can buy more:
- Services for CD, SRM, and CE
- MAUs for Feature Flags
- Executions for IACM
- Security Scans for STO
- Supply Chain Executions for SSCA
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
If you purchased your module with a Developer 360 subscription, the Subscriptions page displays the the developer license count (Developers), as well as the consumption entitlement, for example, for CD, this would show Services or Service Instances.
Fields vary by module, based on the licensing unit of the module.
If you didn't purchase your module with a Developer 360 subscription, the Subscriptions page displays the License Count for your module-specific license, which is CD Services or CD Service Instances for CD.
Module subscriptions and licenses
For more information on module subscriptions and license information, go to:
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 build 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.