Harness Review (2026)

What Harness actually is

Harness is a DevOps platform. CI, CD, an internal developer portal, and a growing stack of modules for shipping software. Feature flags are one of those modules. So the first thing to get straight is that you’re not evaluating a flag tool - you’re evaluating a module inside a large platform. That framing changes the whole decision.

The flags module is capable, and it should be, because it’s built on Split. Harness acquired Split Software and the feature-flag and experimentation product is now branded Harness FME. Existing Split customers are being folded into it. The underlying tech - local decisioning in the SDK, config pushed over a CDN, real experimentation - is Split’s, and Split was one of the strongest flag-and-experiment products in the market.

Harness itself is very well funded. It raised a $240M Series E in December 2025 at a $5.5B valuation, led by Goldman Sachs, with around $570M raised in total and $250M+ ARR. This is not a startup that might disappear. The question is a different one.

The real question: do you want flags in a bundle?

Here’s the decision that actually matters, and it has nothing to do with flag features. Should you buy feature flags as one line item in a whole DevOps platform?

If you already run Harness for CI/CD and your internal developer portal, the answer leans yes. The flags live in the same interface, share the same access controls, and cut down on tool sprawl. That integration is real value, and it’s the strongest reason to choose Harness flags over a standalone tool.

If you just want feature flags, the answer leans no. Buying flags here means buying into the platform’s commercial model: sales-led pricing, modular add-ons, and a surface area far larger than a flag tool needs. That’s the gotcha - platform-bundle lock-in. You come for flags and you’re steered toward the suite.

Pricing: modular, and hidden

There’s no published price for the paid tiers. The pricing page lists three plans:

Plan	Price	Who it’s for
Free	$0	Individual devs and small teams, flags included
Essentials	Contact sales	Paid modules, quoted on usage
Enterprise	Contact sales	Self-managed, governance, SLAs

Both paid tiers route to sales. Historically the flags module was free up to around 1,000 MAUs, then roughly $10 to $12 per 1,000 MAUs plus a per-service-connection charge - but that’s third-party data, and Harness changes it, so verify before you budget. The deeper issue is structural: because flags are a module, your real cost depends on which other modules you license and how the whole bundle is quoted. Some modules also carry seat minimums, which pushes the total up. You can’t price the flags in isolation, and that’s by design.

The Split migration to watch

If you’re an existing Split customer, this is your headline. Split is now Harness FME, and customers are being migrated into it. That migration carries two risks worth naming: product-transition friction as the platform changes underneath you, and repricing risk as your Split contract turns into a Harness one. It’s not a reason to run, but it’s a reason to read the renewal carefully.

Harness versus a standalone flag tool

The honest framing: Harness wins on integration and loses on focus. Against a dedicated flag vendor, it gives you flags plus a whole delivery platform, tightly wired together. That’s powerful if you use the platform. Against that same vendor, it asks you to adopt far more than flags, priced through sales, with the interface complexity that reviewers repeatedly flag - a cluttered UI and a steeper learning curve than standalone tools.

So the comparison isn’t really feature-versus-feature. It’s platform-versus-point-tool. If you want the platform, Harness flags are a strong reason to like it more. If you want a point tool, the bundle is overhead.

Should you use it?

Use Harness if you’re an enterprise DevOps or platform-engineering team already buying Harness modules, you want flags and experimentation in the same suite, and you’re comfortable with sales-led, modular pricing.

Don’t use Harness for flags alone if you just need a feature-flag tool, you want a published price you can budget against, or you don’t want to adopt a whole DevOps platform to get toggles. In that case a standalone flag vendor is simpler and more transparent.

Bottom line: the flags are good - they’re Split’s, after all - but that’s not the deciding factor. Decide whether you want to buy flags as part of a platform. If you’re already in the Harness ecosystem, it’s an easy yes. If you’re not, weigh the bundle lock-in and the sales-led pricing before you let a flag need pull you into a whole suite.

---

Pricing and features verified against harness.io on 23 July 2026. Feature-flag pricing changes often - we re-verify regularly. Historical flag pricing figures are third-party and labelled as such; Harness publishes no list price for its paid tiers.