Harness pricing

About

Harness was founded in 2017 by Jyoti Bansal — the founder and former CEO of AppDynamics, which Cisco acquired for $3.7 billion earlier that same year — alongside Rishi Singh. The company launched from stealth in October 2017 with a $20 million Series A and pitched itself as continuous-delivery-as-a-service, using AI/ML to detect bad deployments and roll them back automatically. Nine years and roughly $815 million in disclosed funding later, Harness closed a $240 million Series E in December 2025 led by Goldman Sachs at a $5.5 billion valuation, on track to exceed $250 million in annual recurring revenue for 2025 — a >65× step-up from that first $20 million round.

Most of Harness’s current breadth arrived through acquisition rather than in-house build: Drone.io (2020, open-source CI), Propelo (2023, engineering insights), Armory (2024, Spinnaker-based CD), Split Software (2024, feature flags/experimentation), Traceable (2025, API security, structured as a merger), and Codecov (2026, code-coverage governance, acquired from Sentry). Each acquisition became a licensed module inside the same platform rather than a separately sold product — see Pricing evolution for the full timeline.

The platform is organized around modular “Agents” spanning the lifecycle from code to production: a Software Delivery Agent (CI, CD, GitOps, infrastructure, databases, artifacts, repositories, code review), a Security Testing Agent (AI SAST, AI SCA, supply-chain security, security testing orchestration), a Runtime Protection Agent (API posture, API advanced protection, AI posture, AI firewall), and a Cost Management Agent (AI & cloud costs, engineering efficiency). Additional modules span incident response, an internal developer portal, resilience testing, and AI evals. Harness reports orchestrating 185M+ deployments and $2.8 billion in managed cloud spend annually across 1,000+ enterprise customers, and was named No. 24 on Fortune’s 2026 America’s Most Innovative Companies list.

The pricing page addresses three distinct buyers: individual developers and small teams (Free), growing organizations that want CI/CD/IaC/security bundled into one predictable package (Essentials), and larger teams that want to license exactly the modules they need from the full 15-module catalog (Enterprise). Customer logos shown on the pricing page (Citi, United, Ancestry, Morningstar, Workday, Experian) point to a buyer base that skews toward mid-market and enterprise engineering organizations, even though the entry point is a genuinely free, self-serve tier for individuals.

Competitively, Harness sits in the CI/CD and internal-developer-platform category alongside GitLab, CircleCI, and GitHub Actions on the delivery side, and alongside cloud-cost and security-testing point solutions on the Cost Management and Security Testing Agent side — its differentiation is bundling all of these into one platform with a single (if entirely sales-negotiated) commercial relationship, a packaging strategy discussed further in our guide to choosing the right usage metric.

Pricing summary : How Harness’s DevOps platform pricing model works — freemium plus sales-gated module bundles

Harness uses a freemium + sales-negotiated module bundle model with 3 dimensions:

1. Tier structure: Free ($0, self-serve, individual developers/small teams) leads to Essentials (Contact Sales, fixed all-in-one bundle for growing orgs) and Enterprise (Contact Sales, pick-any-module for teams that want exact-fit capabilities).
2. Module-based packaging: the platform is decomposed into 15 modules across 4 categories — DevOps (6: CD & GitOps, CI, Feature Management & Experimentation, IaC Management, Database DevOps, Artifact Registry), Testing (2: AI Test Automation, Resilience Testing), Security (3: Application Security Testing, Web Application & API Protection, AI Security), and Operations (4: Cloud AI Cost Management, AI DLC Insights, AI SRE, Internal Developer Portal). Essentials fixes a specific 4-module subset (CD & GitOps, CI, IaC Management, Security Testing Orchestration) as one non-separable SKU; Enterprise licenses any combination of all 15.
3. Capacity-gated entitlements, not usage rates: the only publicly quantified differences between Essentials and Enterprise are capacity caps — Maximum Users (up to 500 vs. Unlimited), Organizations (up to 1 vs. Unlimited), Custom Dashboards (up to 5 vs. Unlimited), Custom Roles (up to 5 vs. Unlimited), and Pipeline Execution History (6 months vs. 25 months, the latter as an add-on) — never a dollar figure.

What makes this different: Harness publishes a genuinely detailed, 20+ row capability-comparison table (with hover tooltips explaining every entitlement) while disclosing zero dollar amounts for either paid plan — transparency about what you get, total opacity about what it costs.

Pricing by product

Harness Platform (plans)

Essentials vs. Enterprise (capability entitlements)

Module composition by plan

None of the 11 Enterprise-only modules (Feature Management and Experimentation, Database DevOps, Artifact Registry, AI Test Automation, Resilience Testing, Application Security Testing, Web Application and API Protection, AI Security, Cloud AI Cost Management, AI DLC Insights, AI SRE, Internal Developer Portal) are purchasable at the Essentials tier — Essentials is fixed to exactly 4 modules.

Sales motions across products: self-serve for Free; sales-led (Contact Sales, quote-only, no self-serve checkout) for Essentials and Enterprise.

Hidden costs : What Harness customers actually pay when there’s no public rate card to check against

Because harness.io/pricing never shows a dollar figure for Essentials or Enterprise, the only visibility into real-world spend comes from third-party SaaS-procurement benchmarking rather than Harness’s own page. Two representative archetypes, built from aggregated purchase-order data reported by Vendr’s Harness marketplace listing and CloudZero’s Harness pricing teardown:

A mid-market Essentials buyer (~200-employee engineering org)

Vendr’s aggregated purchase-order data (n=84) puts actual Harness contracts anywhere from $8,500 to $232,000+ per year, with a median of $48,350 — a greater than 27× spread between the smallest and largest observed deals, none of which a self-serve buyer could have predicted from the pricing page alone.

A multi-module Enterprise buyer with CI overage exposure

The lesson both archetypes teach: because every number above is negotiated rather than published, the same module set can cost a small team five figures and a heavy enterprise account six figures, and neither number is discoverable from harness.io/pricing itself — a textbook case of the pricing unpredictability problem that self-serve buyers usually avoid.

Want to estimate your own Harness bill? There’s no public rate to plug in, so the Harness pricing calculator is a starting scaffold rather than a live quote — pair it with the archetypes above, or compare other quote-only DevOps platforms in the pricing blueprint.

Pricing evolution : From a public per-instance rate card to an all-acquisitions, all-sales-gated module catalog

Cadence

Tracked range: 2018–2026. Quarters not listed above (2018 Q3–2019 Q1, 2019 Q4–2020 Q2, 2020 Q4–2022 Q4, 2023 Q2–2023 Q4, 2024 Q3–2024 Q4, 2025 Q2–2026 Q1) were not captured with high enough confidence to confirm zero activity and are left unlisted rather than asserted stable.

Notable changes

• 2019-08 — Harness removed its public $25/month per-Service-Instance rate card and moved to a fully quote-only, three-tier model — the largest transparency reversal in the company’s history, discovered by comparing archive.org snapshots of harness.io/pricing from May and August 2019.
• 2020-08-05 — Acquired Drone.io and committed to keeping it open source, per harness.io/blog/harness-acquires-ci-pioneer-drone-io-and-commits-to-open-source.
• 2024-03-22 — Published “Introducing Developer 360 pricing by Harness,” moving every module onto a single per-developer metric, per harness.io/blog/introducing-developer-360-pricing-by-harness.
• 2024-06-11/12 — Completed the Split Software acquisition (feature flags/experimentation), per prnewswire.com.
• 2025-03-04 — Completed the Traceable merger, forming what both companies called an “AI-native DevSecOps platform,” per prnewswire.com.
• 2026-09-01 — Pricing consolidated onto the current Free/Essentials/Enterprise structure with 15 modules across 4 categories, still without a single public dollar figure for either paid tier.

The 2019 transparency reversal in detail

Harness’s 2019 pricing pages are unusually well-documented for a pre-Series-B startup: the May 2019 snapshot doesn’t just list a price, it explains the mechanic in FAQ form — $25/month per Service Instance, counted at the 95th percentile over a rolling 30 days specifically so bursty, elastic workloads wouldn’t be penalized, with an explicit argument against per-user or per-deployment pricing (“You want Harness to deploy/verify/rollback all your deployments, everywhere — so that’s the heart of our pricing model”). By the very next captured snapshot (August 2019), that entire framework — the calculator, the FAQ, the per-instance meter — is gone, replaced by “Request a Quote” across both paid tiers. No blog post, press release, or press coverage announcing the change was found; the only evidence is the before/after page content itself. Every pricing page since has stayed sales-gated for paid tiers, through the 2024 Developer 360 rebrand and into the current 2026 Essentials/Enterprise structure.

What’s unique : A usage-metered rate card, abandoned, then rebuilt entirely through acquisition

1. Harness is one of the few corpus companies with a documented retreat from real usage-based pricing. Most sales-gated companies in this corpus never published a rate card at all. Harness did — a genuinely metered $25/month-per-Service-Instance model with a 95th-percentile bursty-usage calculator — and then removed it entirely by August 2019 in favor of “Request a Quote.” That’s a rarer and more instructive data point than simple opacity: it shows a company consciously trading a defensible usage meter for sales-led negotiation leverage as it moved upmarket.

2. The platform is substantially a roll-up, not a build. At least 6 of Harness’s 15 modules trace to acquisitions (Drone.io, Propelo, Armory, Split, Traceable, Codecov) rather than organic engineering, yet all of it sits behind one Essentials/Enterprise contract. This is a different flavor of freemium platform consolidation than most CI/CD peers, who tend to build feature-flags or security-testing capability in-house rather than acquire a market leader outright.

3. Radical transparency about capability, total opacity about cost. The Essentials vs. Enterprise comparison table quantifies 20+ specific entitlements — concurrent pipeline executions (up to 60 vs. up to 500), pipeline history (6 vs. 25 months), custom dashboards (up to 5 vs. unlimited) — with genuine precision, while showing zero dollar signs anywhere on the page. Few sales-led vendors invest this much in publishing granular capability data given how little price data accompanies it.

4. AI features are bundled entitlements, not metered upsells. AIDA, AI Code Review, AI Test Automation, and AI SRE ship inside the modules a customer already licenses rather than as consumption-priced add-ons — the opposite of the token-metered or per-agent-action pricing common among AI-native coding tools, and a choice that keeps Harness’s “AI-native software delivery” pitch structurally simple even though its base pricing is opaque.

Strengths & weaknesses

Billing UX : Category-collapse and hover-tooltip controls on the plan-comparison table

• Category collapse/expand chevrons — the Essentials vs. Enterprise comparison table groups rows under “PLATFORM CAPABILITIES,” “DEVOPS,” “TESTING,” “SECURITY,” and “OPERATIONS” headers; each header carries a chevron control that collapses or expands that category’s rows (the page’s own instruction: “click a category to collapse it”).
• Hover-for-detail “i” tooltips — every capability row (e.g., “Continuous Delivery & GitOps,” “Concurrent Pipeline Executions”) carries an ”ⓘ” icon that surfaces a one-line plain-language description of that entitlement on hover (“Hover ⓘ for details”).
• Module-preview ”+” expanders — each plan card’s “PLAN DETAILS” panel has a ”+” control that expands a compact module-icon row into a named module list (e.g., Enterprise’s “Operations · 4 modules · +” expands to Cloud AI Cost Management / AI DLC Insights / AI SRE / Internal Developer Portal).
• Sticky dual “Contact Sales” CTAs — the same Contact Sales / Get Started for free buttons appear both at the top plan-card row and again as column headers pinned atop the comparison table, so the conversion action stays visible while scrolling the full entitlement grid.

Strategic wins : Why the module-bundle-plus-M&A playbook has worked for Harness

1. Consolidating a fragmented DevOps toolchain through disciplined bolt-on acquisitions

Rather than build feature flags, API security, or code-coverage tooling from scratch, Harness bought category-credible assets (Drone.io, Split, Traceable, Codecov) and folded each into the same Essentials/Enterprise contract. For a buyer, that converts what would otherwise be 4-5 separate vendor relationships and renewal cycles into one, which is a meaningful reduction in tool sprawl even before any pricing benefit is considered.

2. Keeping AI features bundled rather than bolting on a separate metered SKU

As AI coding assistants push teams toward the per-user-license-to-consumption shift many SaaS vendors are wrestling with, Harness chose to fold AIDA, AI Code Review, and AI Test Automation into existing module entitlements instead of inventing a new token-metered add-on. That avoids the “surprise AI bill” pattern showing up elsewhere in the market and keeps the sales conversation to one number per module, not two.

3. Publishing granular capability data even while withholding price

The 20+ row Essentials-vs-Enterprise entitlement table (concurrent pipeline executions, pipeline history months, custom-dashboard caps) gives prospects real self-serve research value before they ever talk to sales — a partial answer to the value-metric transparency problem that many quote-only vendors don’t bother solving at all.

4. A genuinely free, unlimited-duration entry tier

Free isn’t a time-boxed trial — it’s forever, and it bundles Harness Open Source plus the Litmus Chaos engineering tool. That gives individual developers and small teams a real product to standardize on before any commercial conversation starts, which is the textbook freemium funnel mechanic done well.

Areas to improve : Where the sales-gated model still leaves buyers guessing

1. No directional pricing anchor at all

Even sales-led competitors often publish a “starting at” figure or a per-seat range to let prospects self-qualify. Harness shows nothing — not even the kind of indicative floor other quote-only vendors in this corpus use to filter unqualified leads. Publishing even a single “Essentials typically starts around $X/year for teams of Y” data point, sourced from the company’s own aggregate book of business, would cut the number of unqualified sales calls without giving away real deal-by-deal leverage.

2. Essentials’ rigidity discourages growth-stage adoption

Harness’s own FAQ confirms Essentials customers cannot add any of the 11 Enterprise-only modules à la carte — they must fully upgrade to Enterprise to add even one more module. A middle path (e.g., allowing 1-2 add-on modules onto Essentials at a quoted incremental rate) would better serve the “growing organization” segment Essentials is explicitly targeted at, instead of forcing an all-or-nothing jump to Enterprise.

3. Three pricing-model rewrites in eight years erodes buyer trust in any future public figure

Moving from per-instance metering (2018-2019) to quote-only tiers (2019-2024) to Developer 360 per-developer licensing (2024-2026) to the current fixed-bundle-plus-pick-any-module structure means a prospect researching Harness pricing today can find at least three contradictory “how Harness prices” descriptions across cached web content, review sites, and Harness’s own historical blog posts. A single canonical “how we price today” explainer page, kept current and cross-linked from every historical post, would reduce this confusion — see our guide on usage-based pricing migrations for how vendors typically communicate a pricing-model change.

4. Professional-services and support-tier costs remain fully invisible

Per third-party benchmarking, implementation/migration services can add 10-30% to first-year cost and premium support packages another 15-25% — neither disclosed anywhere on harness.io/pricing, including in the FAQ that otherwise names Professional Services as a purchasable add-on. Naming even indicative percentage ranges for these line items (as some competitors do) would materially improve total-cost-of-ownership planning for prospective buyers.

Key takeaways

1. A real usage meter can be abandoned, not just never built. Harness ran a defensible $25/month-per-Service-Instance rate card with a bursty-usage-friendly 95th-percentile calculator through mid-2019, then removed it entirely in favor of quote-only pricing. Teams considering a move upmarket should study this as a cautionary example of what gets lost — self-serve conversion, comparability, trust — even when the switch is deliberate and well-reasoned.
2. Acquisition-led platform consolidation can outrun pricing-model coherence. Six modules arrived via M&A (Drone.io, Propelo, Armory, Split, Traceable, Codecov) across eight years, and each one landed inside whatever pricing structure was current at the time rather than forcing a unified rebuild — resulting in three distinct historical pricing eras for the same expanding platform.
3. Publishing detailed capability data without price is a legitimate middle ground. Harness’s 20+ row Essentials-vs-Enterprise entitlement table shows that “sales-only” doesn’t have to mean “opaque about everything” — quantifying capacity and feature differences while withholding cost still gives buyers real self-serve research value.
4. Bundling AI features into existing entitlements avoids a second pricing conversation. As many SaaS vendors bolt separately metered AI add-ons onto their core product, Harness’s choice to fold AIDA and its AI Code Review/Test Automation features into modules customers already license keeps the AI story simple, even if it also means Harness can’t yet show AI-specific revenue or usage data publicly.
5. A genuinely permanent free tier is a durable trust signal, even inside an otherwise opaque pricing page. Free-forever access to Harness Open Source and Litmus Chaos, with no credit card and no time limit, gives individual developers a real reason to standardize on the platform years before any commercial conversation — a pattern worth studying alongside Harness’s freemium approach.

UBP implications

1. Sales-gating isn’t a fixed destination — companies can and do move both directions. Harness’s trajectory (public per-instance meter → quote-only → per-developer → current fixed-bundle model) shows that “contract-negotiated” pricing isn’t necessarily where a usage-based product ends up permanently; it can be a deliberate retreat from metering as a company shifts toward enterprise sales motion, not just an immature startup’s temporary state before it “graduates” to public pricing.
2. A capability-transparency layer can partially substitute for price transparency. Harness’s granular entitlement comparison table suggests that vendors uncomfortable publishing prices can still ship real self-serve research value — quantified capacity caps, feature-by-tier breakdowns — without disclosing a rate card, narrowing (without closing) the information gap that usage-based pricing advocates usually solve with published per-unit rates.
3. Bundling AI capability into existing entitlements delays, rather than resolves, the AI-cost-attribution question. By folding AIDA and its AI features into modules customers already license instead of metering them separately, Harness avoids a second pricing conversation today — but also forgoes the usage-based pricing playbook’s core promise (cost tracks value delivered), a trade-off other AI-native platforms are making differently as they meter tokens or agent actions directly.

Sources

• Harness pricing page (accessed 2026-09-01)
• Harness blog (accessed 2026-09-01)
• Introducing Developer 360 pricing by Harness (accessed 2026-09-01)
• Harness Acquires CI Pioneer Drone.io and Commits to Open Source (accessed 2026-09-01)
• Welcome Split to the Harness Team (accessed 2026-09-01)
• Harness and Traceable merge to enhance secure software delivery (accessed 2026-09-01)
• Harness Acquires Codecov from Sentry (accessed 2026-09-01)
• Harness Platform FAQs (Developer Hub) (accessed 2026-09-01)

Bottom line

Harness sells a genuinely useful free tier and a granular, well-documented feature-comparison table — but every dollar figure above the free plan has been sales-negotiated since August 2019, when the company quietly retired a real, usage-metered $25-per-Service-Instance rate card that it had spent real effort explaining to prospects. Eight years, six acquisitions, and three pricing-model rewrites later, “AI-native software delivery” ships bundled into that same opaque, quote-only structure — buyers get exceptional visibility into what they’d get, and none at all into what it costs.

Want to compare Harness against other quote-only DevOps and platform pricing models? Browse the pricing blueprint.

Pricing timeline : Major events on a vertical axis

Each milestone below corresponds to a public pricing change, product launch, or material adjustment. Major events use a filled marker; minor adjustments use a faded one.

Baseline capture: single consolidated pricing page, fully sales-gated paid tiers

Sep 2026

Verified 2026-09-01: harness.io/pricing shows three plans — Free ($0, self-serve), Essentials (Contact Sales, fixed 4-module DevOps bundle), and Enterprise (Contact Sales, pick-any of 15 modules across DevOps/Testing/Security/Operations). No numeric price is disclosed for either paid tier; a public capability-comparison table quantifies entitlement caps (users, orgs, dashboards, pipeline history) but never a rate. price_transparency = sales-only, has_free_tier = true. (Evidence: 2026-09-01-main-default.txt / 2026-09-01-main-modules-expanded.txt.)

Acquires Codecov from Sentry, adding code-coverage governance

Jun 2026

Harness acquired Codecov from Sentry to 'strengthen software delivery governance in the AI era,' embedding code-coverage intelligence into the delivery pipeline as AI agents generate a growing share of committed code; Sentry retained Codecov's brand and free access for open-source projects under a continuity agreement. Source: harness.io/press-and-news/harness-acquires-codecov (accessed 2026-09-01).

Completes Traceable merger, adding the Runtime Protection Agent (API security)

Mar 2025

Harness and API-security vendor Traceable completed a merger (announced 2025-02-10, closed 2025-03-04), forming what both companies called 'the world's most advanced AI-native DevSecOps platform.' Traceable's API posture, API advanced protection, and AI posture/firewall capabilities became the Runtime Protection Agent, sold as additional negotiated modules rather than a separately priced product. Source: harness.io/blog/harness-traceable (accessed 2026-09-01); prnewswire.com/news-releases/harness-and-traceable-complete-merger-creating-worlds-most-advanced-ai-native-devsecops-platform-302392412.html.

Completes acquisition of Split Software, adding Feature Management & Experimentation

Jun 2024

Harness completed its acquisition of feature-flag/experimentation vendor Split Software (agreement announced 2024-05-29, close announced 2024-06-11/12), rebranding it Feature Management & Experimentation (FME) and licensing it as a distinct, MAU-based module rather than publishing a standalone rate card. Source: harness.io/blog/harness-to-acquire-split (accessed 2026-09-01); prnewswire.com/news-releases/harness-completes-acquisition-of-split-software-302170987.html.

Introduces Developer 360: per-developer pricing across every module

Mar 2024

Harness published 'Introducing Developer 360 pricing by Harness,' replacing prior per-service-instance and per-module licensing with a single per-developer metric applied uniformly across all modules ('Developers, DevOps, Quality Engineers, Data Engineers, Product Managers, Security Engineers' all count as a developer seat). Plans were Free (6 modules) and Enterprise (14+ modules across 4 categories); still no public per-developer rate. Source: harness.io/blog/introducing-developer-360-pricing-by-harness (accessed 2026-09-01, publish date 2024-03-22).

Acquires Armory for $7M cash, deepening the Continuous Delivery module

Jan 2024

Harness acquired Spinnaker-commercial vendor Armory for $7 million in cash, absorbing its enterprise CD assets into the existing Continuous Delivery & GitOps module rather than creating a new SKU. Source: harness.io/blog (via Hacker News listing 'Harness Acquires Armory for $7 million in cash', 2024-01-15, https://www.harness.io/blog/harness-acquires-armory-assets).

Acquires Propelo, becomes the Software Engineering Insights (SEI) module

Jan 2023

Harness acquired engineering-productivity analytics vendor Propelo and folded it into the platform as the Software Engineering Insights module, adding an engineering-metrics/DORA-style product line to the module catalog sold under the same sales-negotiated umbrella. Source: harness.io press coverage via devops.com/harness-acquires-propelo-to-surface-software-engineering-bottlenecks (accessed 2026-09-01).

Acquires Drone.io, adding a dedicated open-source-rooted CI product line

Aug 2020

Harness acquired Drone.io, the open-source continuous-integration project, and committed to keeping Drone open source. By the October 2020 snapshot of harness.io/pricing, the page had reorganized into separate Continuous Integration / Continuous Delivery / Continuous Efficiency product sections, each with its own Community/Essentials/Professional tiers — still entirely 'Request Quote' for paid tiers. Source: harness.io/blog/harness-acquires-ci-pioneer-drone-io-and-commits-to-open-source (accessed 2026-09-01); techcrunch.com/2020/08/05/harness-makes-first-acquisition-snagging-open-source-ci-company-drone-io.

Public per-instance price disappears; pricing becomes fully quote-only

Aug 2019

Archive.org capture (2019-08) shows the $25/month per-Service-Instance rate card replaced by a three-tier Community (free) / Essentials / Professional structure, with both paid tiers now labeled 'Request a Quote' and no dollar figure anywhere on the page — the same transition Harness's pricing page still reflects in 2026. This is the single largest transparency inflection found in Harness's pricing history: a company that had built and marketed a genuinely metered, usage-based rate card abandoned public pricing entirely within about three months of the 2019-05 snapshot. Source: web.archive.org snapshots of harness.io/pricing, May and August 2019.

Same $25/month per-instance model, now with a self-serve volume calculator

May 2019

Archive.org capture (2019-05) confirms the $25/month per Service Instance rate held for nearly a year, with a published FAQ explaining the mechanic: deployment type (Kubernetes pods, ECS tasks, PCF app instances, containers, VM processes, serverless-function increments) times instance count, banded from 0-50 up to 5,000+ (custom quote above that), counted at the 95th percentile over a rolling 30 days to stay friendly to bursty workloads. The FAQ explicitly argues against per-user or per-deployment pricing ('the heart of our pricing model' is licensing what Harness manages, not who uses it). Source: web.archive.org snapshot of harness.io/pricing, May 2019.

Public rate card: Lite (free) vs. Pro at $25/month per Service Instance

Jun 2018

Archive.org capture of harness.io/pricing (2018-06) shows a two-tier Lite/Pro structure. Lite is free forever (25 Service Instances, 3 pipelines, 3 users, 2-day history). Pro is $25/month per Service Instance (also billed per 1M/day of serverless function calls), unlocking unlimited service instances/pipelines/users, continuous verification, secrets management, audit trails, RBAC, LDAP/SAML, and 1-year history. Source: web.archive.org snapshot of harness.io/pricing, June 2018.