Developer 360 is the name Harness gives to its Developer-based subscription model. In it, a Developer licence is the base unit for modules that people use directly, and a set of consumption entitlements per Developer covers modules whose natural unit is a service, a scan or an execution.[2] This article explains the Developer definition, which modules track it, and the unit of each module as listed in the Products and License Unit Definitions page, version June 2, 2026.[1]
Editions
The pricing page presents Essentials and Enterprise plans. Essentials is an “all-in-one package” of CI, CD, Code Repository, Security Testing Orchestration and IaCM. Enterprise lets the customer choose modules in the groups DevOps, Testing, Security and Operations.[4] Essentials has limits of one organization and up to 500 users, whereas Enterprise has unlimited organizations and users, and the platform resource limits table lists 1 organization and 500 users for Essentials against 5,000 organizations and 90,000 users for Enterprise.[4][5] The table gives Free 1 organization and 100 users.[5] These are described as “default platform limits” that “are not hard restrictions” and can be adjusted through support.[5] Catalog rows: Essentials plan, Enterprise plan and the rule Platform resource limits differ by Free, Essentials and Enterprise.
Metrics
The Developer
The contract definition states that “Developer” means “each person, identified by a specific, unique email address, who is an employee, agent, or contractor of the Customer or Customer’s Affiliate that accesses Software or the Harness Platform directly, or contributes to code development, deployment, security, maintenance, optimization or any other technical activities related to software code that is managed with Harness products, across all production and non-production environments”.[1] Three further rules follow.
- A person who does several of these things is counted once.[1]
- Using bots or robotic process automation to run the Software or Platform requires Harness’ prior written consent and may carry additional restrictions.[1]
- Harness may revise the definition on notice, but not retroactively or so as to materially decrease its overall obligations during an Order Form licence term.[1]
The Subscription Terms are consistent: users may be “employees and contractors of Customer and its Affiliates”, and where unlimited License Units are bought, each Affiliate that will use the platform “must be named on the applicable Order Form”.[3] The pricing page defines a user differently and more narrowly, as “an individual who has been granted direct access to the Harness platform” who can log in, act in the product and has an email address.[4] See Developer is a unique email address that accesses or contributes to Harness-managed code, A person active in several ways counts as one Developer and Bots and robotic process automation need Harness’s prior written consent.
Modules that track Developers directly
In Developer 360 four modules track Developers directly, and “each module requires a separate developer license for every user involved”.[2]
| Module | Who consumes a licence |
|---|---|
| Code Repository (CODE) | All users with permission to access the CODE module[2] |
| Continuous Integration (CI) | All users with permission to access the CI module[2] |
| Internal Developer Portal (IDP) | All users with permission to access the IDP module[2] |
| AI DLC Insights (AIDI) | Developers explicitly imported for whom Insights are generated, even if they “may never login to the Harness Platform”[2] |
The practical effect is that a licence is consumed by permission to reach a module rather than by use. A person with CI access who never runs a build still counts as a CI Developer.[2] The rows are CODE, CI and IDP consume a licence for every user with module access and AI DLC Insights counts imported developers even if they never log in.
Included consumption entitlements
Modules without direct developer tracking, apart from Cloud Cost Management, “track an indirect unit instead”, which Harness calls consumption entitlements. The Developer licence acts as a proxy that grants a set of them.[2]
| Module | Included entitlement per Developer |
|---|---|
| Continuous Delivery and GitOps | 1 Service for every 3 Developers[2] |
| Service Reliability Management | 1 Service for every 3 Developers[2] |
| Chaos Engineering | 1 Service for every 3 Developers[2] |
| Infrastructure as Code Management | 120 Executions per Developer per year[2] |
| Security Testing Orchestration | 100 Security Scans per Developer per month[2] |
| Supply Chain Security | 100 Supply Chain Executions per Developer per month[2] |
Additional entitlements can be purchased for each of these.[2] The contract page expresses the same ratios as “.33” of a service per Developer for CD and SRM and 0.33 for Resilience Testing, ten IaCM Executions and one hundred Security Scans and supply chain Executions per Developer per month.[1] The documentation describes the Developer 360 subscription as offering Free and Enterprise plans for all modules except Cloud Cost Management.[2] See Developer licences include fixed consumption entitlements.
Counting / floors
The following unit definitions come from the License Unit Definitions page.[1]
Feature Flags and FME. “Monthly Tracked Keys” correspond to the number of unique user, device, account or other keys on which flag decisions are based within a calendar month.[1] FME de-duplicates keys across projects, environments, traffic types and flags, so a key evaluated across several flags counts once.[6] FME also includes a daily quota of 5,000 CDN requests and 5,000 received impressions per MTK entitlement, with overage at USD 0.20 per million CDN requests and USD 0.15 per million impressions if a notified issue is not resolved within five business days.[1] FME seats are being replaced: Harness says it is “transitioning away from seat-based pricing” to active users, defined as anyone who accesses an FME capability, including view-only use.[6] The Feature Flags documentation lists Free (up to 2 developers, 25,000 client MAUs), Team (up to 50 developers, 100,000) and Enterprise (unlimited developers, 1 million) plans.[7] Rows: Monthly Tracked Key, FME includes daily CDN and impression quotas per MTK, FME user seats are being replaced by active users.
Cloud and AI Cost Management. Fees are “charged as a percentage of the Total Tracked Cloud Spend”, up to an agreed amount stated in the Order Form, and additional capacity during the term requires a new Order Form.[1] The page sets Cloud Cost Insights at 1% of tracked cloud spend, Commitment Orchestrator at 1.25% of tracked EC2 spend, Autostopping at 1.25% of non-production spend and Cluster Orchestrator at 2% of Kubernetes spend.[1] The CACM documentation measures usage against Total Cloud Spend Managed, total unblended spend less Enterprise Discount Program discounts and marketplace spend, and offers a Free Forever plan for up to USD 250,000 a year with 2 Kubernetes clusters, 10 AutoStopping rules and 30 days of data. The same page states the free threshold as USD 250K per year in one place and per month in another.[8] Rows: Total Tracked Cloud Spend, CACM SKUs are priced at 1% to 2% of different spend bases, CACM usage is measured against Total Cloud Spend Managed.
Security Testing Orchestration. A Security Scan is “a single execution of a security test initiated through STO against a unique application target, service, or codebase”, and each Developer is entitled to 100 per month.[1] The DevOps Essentials terms define it as the execution of the STO step in a pipeline against a repository, container image, configuration or live application.[10]
Resilience Testing. An RT Service is any Target Resource that undergoes chaos experiments in a 12-month period: a Kubernetes workload, a VM or bare-metal host, a cloud load balancer or container service, or five serverless functions. Repeated experiments on the same resource do not add services, and 100 experiments on an unlisted resource equal one.[1] The Chaos Engineering documentation shows the mapping as 1:1 for Kubernetes workloads, VMs and cloud services, 5:1 for serverless functions and 100:1 for miscellaneous targets, measured over a yearly cycle.[9]
Infrastructure as Code Management. An Execution is a successful Terraform apply or destroy run that changes resources. A Workspace is one state file (or one Terragrunt unit), and an Active Host is a host that received an Ansible playbook in the preceding 30 days, measured at the high-watermark in the period.[1]
Supply Chain Security, Database DevOps and Artifact Registry. An SCS Execution is one end-to-end security validation run per artifact per scan event. A DB Instance is “each copy of a Schema deployed within a database environment”, and Artifact Registry is measured in allocated gigabytes of storage.[1]
API modules. For the Traceable-based API Protection, Web Application Firewall and Bot and Abuse Protection modules, each API Call is counted individually “whether the request is allowed, blocked or flagged”, and the monthly entitlement is provisioned as a Calls Per Minute rate without guaranteed burst capacity.[1]
Code Repository. The Free plan allows 10 GB of storage and 50 GB of monthly bandwidth, and paid plans 250 GB of each. Exceeding storage blocks pushes and exceeding bandwidth returns HTTP 429.[11]
Virtualization & partitioning
No Harness unit counts processors or cores. Virtual machines appear as a type of CD service, as an RT Target Resource and as an Active Host in IaCM, in each case counted as a single unit.[1] A virtualization or hard-partitioning rule of the kind described in virtualization and partitioning is absent from the retrieved documents.
Cloud / BYOL
The Developer 360 units apply to the SaaS platform and to Self-Managed Enterprise Edition, whose licence keys enable the core platform and its modules.[2] Where customers run pipelines on their own infrastructure, the Cloud Credit unit is not consumed for that execution.[1] See Harness Cloud credits, Flex Pricing and overage.
Programs
- Developer 360 subscription model. Developer licences with the entitlements listed above.[2]
- Add-on entitlements. More services for CD, SRM and Chaos, more Executions for IaCM, and more Security Scans and Supply Chain Executions can be purchased.[2]
- Flex Pricing. An alternative pool of units described in Harness Cloud credits, Flex Pricing and overage.
Audits and compliance
Licence counts are visible under Account Settings, Subscriptions, where the page shows the Developer count and the consumption entitlement for each module.[2] Because licences for CODE, CI and IDP follow access permissions, an administrator who wants to reduce the count must remove module permissions, not just stop using a module.[2] The Subscription Terms allow Harness to verify usage.[3]
Out of scope
- Prices per Developer, which Harness does not publish.
- The Qwiet-based SAST and SCA modules, which define a Developer as a person who created or modified content analyzed by the service within the last ninety days, and the Codecov module, which counts users who author pull requests on private repositories.[1]
- Order Form amendments that change the definitions.