S

Split.io (now Harness FME)

Feature flags + experimentation built for engineering teams โ€” acquired by Harness in June 2024 and now branded Harness Feature Management & Experimentation

Feature Flags / Experimentation 4.4 / 5 (1 Rating) Free dev tier / Custom enterprise Updated May 2026 ๐ŸŒ Global, Harness-billed

Quick Verdict

Split.io is a feature-flagging and experimentation platform aimed at engineering-led product teams โ€” the closest direct competitor to LaunchDarkly throughout the late 2010s and early 2020s. The product was founded in 2015 in Redwood City, California by Adil Aijaz (CEO), Patricio Echague (CTO) and Trevor Stuart (President), backed by Lightspeed Venture Partners and others, and raised $100M+ in venture funding across Seed through Series D before its exit. On 11 June 2024 Harness completed its acquisition of Split Software (announced 29 May 2024), and the product is now sold inside the Harness platform under the name Harness Feature Management & Experimentation (FME). The standalone Split.io brand and console still work for existing customers, but new procurement now flows through Harness contracts. For Indian product and engineering teams, Split is the right call when you want a mature feature-flag platform with a real built-in experimentation engine, you already use Harness for CI/CD, or you want a credible alternative to LaunchDarkly without going pure open-source.

Feature-flag SDK breadth
4.7
Built-in experimentation
4.4
Developer experience
4.5
Harness-stack synergy
4.4
India support & billing
3.2

What is Split.io?

Split.io โ€” formally Split Software โ€” is a feature-flagging and experimentation platform that pioneered the "feature flags as a measurement layer" idea: every flag is also a treatment in an experiment, and every flag rollout is an opportunity to measure the impact of the change on user-level metrics. This was less common when Split launched in 2015 โ€” most flag platforms (LaunchDarkly included, in its early years) were release-control tools first and measurement tools second. Split flipped that ordering, and the design has aged well; modern feature-flag platforms now uniformly bundle experimentation in some form.

The company was founded in Redwood City, California, by Adil Aijaz, Patricio Echague and Trevor Stuart โ€” Aijaz and Stuart had previously worked together on RingCentral's growth and analytics stack, and Echague brought engineering-platform pedigree from prior roles. Lightspeed led the early rounds, and Split went on to raise $100M+ in total venture capital across Series A through D, including a $50M+ Series D in the early 2020s.

On 29 May 2024, Harness announced its intent to acquire Split, and the deal closed on 11 June 2024. Harness โ€” the developer-platform company founded by Jyoti Bansal (also founder of AppDynamics) โ€” was previously focused on CI/CD, deployment automation and chaos engineering, but had no native feature-management or experimentation product. The Split acquisition closed that gap in one move. The product was renamed Harness Feature Management & Experimentation (FME) and is now both sold standalone and bundled inside Harness's broader developer-platform contract.

For Indian buyers in 2026, the practical change is in the procurement path. If you're already a Harness customer, FME shows up as an add-on to your existing contract โ€” usually quicker and cheaper than buying Split standalone was. If you're not on Harness, the standalone product still works, but the product roadmap is now visibly Harness-shaped (deeper CI/CD integrations, deployment-pipeline-aware flag rollouts), which may or may not align with your stack.

Capabilities

๐Ÿšฉ Feature flags

Mature server-side and client-side feature-flag SDKs in 15+ languages including JavaScript, Python, Java, Go, Ruby, .NET, PHP, Node, iOS, Android. Targeting rules support segments, geographies, percentage rollouts, and gradual ramps with automatic guardrails.

๐Ÿงช Built-in experimentation

Every feature flag can be turned into an A/B experiment. Built-in statistical engine computes treatment effect, confidence intervals and significance against your defined success metrics โ€” no need to bolt on a separate analytics tool.

๐Ÿ“Š Metric monitoring

Send Split your event stream and it computes per-treatment metric impact automatically. Guardrail metrics (reverse-direction signals like errors, latency) are first-class โ€” Split alerts you if a flag rollout is silently degrading a metric you didn't plan to test.

๐Ÿ”„ Progressive delivery

Gradual rollouts (1% โ†’ 5% โ†’ 25% โ†’ 50% โ†’ 100%), kill-switch, scheduled rollouts, automatic rollback on guardrail breach. Standard release-engineering workflows now codified inside the platform.

๐Ÿ”Œ Harness integration (2024+)

Post-acquisition, Split is being deeply integrated with Harness CD: flag flips can be tied to deployment events, deployment pipelines can pause and resume based on flag-experiment outcomes, and flag changes are tracked in the same audit log as deployments.

๐Ÿ›ก๏ธ Enterprise controls

SSO/SAML, granular role-based access, audit log, data-residency options for EU customers, SOC2 Type 2. The bar for procurement at large enterprises โ€” important if your buyer is an Indian financial-services or healthcare team.

Pricing & plans (2026)

Split has historically had a free Developer tier (limited keys + monthly tracked users) and per-seat / usage-based paid tiers. Post-Harness acquisition, the published price card has been pulled in favour of custom Harness contracts. Real-world deals in 2025โ€“2026 typically land in the $25Kโ€“$150K+ per year range depending on monthly active users, number of feature flags, and which experimentation modules you license. For Indian buyers that's roughly โ‚น20Lโ€“โ‚น1.25Cr+ per year all-in. The page's previous "From โ‚น2,772/user/month" figure (~$33/user) appears to come from an old Split-standalone Team plan that no longer applies post-acquisition. Always validate via a quote on split.io or through your existing Harness AE.

When Split.io / Harness FME is the right call

  1. You already use Harness CI/CD โ€” same procurement, same audit log, same identity layer. The integration savings compound.
  2. You want a managed feature-flag platform with serious experimentation built in โ€” Split is the most experimentation-mature option in the flag-platform category, alongside LaunchDarkly Experimentation.
  3. You're an engineering-led team โ€” Split's UX is unapologetically developer-first; PMs can use it but it doesn't pretend to be a marketing tool.
  4. You need enterprise-grade controls (SSO, audit, data residency) โ€” Split has the procurement-friendly checkbox set most Indian large-enterprise buyers expect.

Split is the wrong call when: you specifically don't want vendor lock-in (use GrowthBook open-source), you need warehouse-native experimentation analysis (use Eppo or Statsig), or your need is pure A/B testing on a marketing site (use VWO or Convert.com).

Pros & cons

โœ“ Pros

  • Mature feature-flag platform with 15+ language SDKs
  • Built-in experimentation engine โ€” no separate analytics needed
  • First-class guardrail-metric monitoring
  • Strong enterprise controls (SSO, audit log, data residency)
  • Harness backing post-acquisition gives stability + bundle path
  • Tight CI/CD integration if you're already on Harness

โœ— Cons

  • Pricing pulled from public site โ€” custom contracts only post-acquisition
  • Roadmap visibly shifting toward Harness-stack integration; less standalone investment
  • UX is engineering-first โ€” not the easiest for non-technical PMs
  • Less mature than Eppo/Statsig for warehouse-native metric analysis
  • India billing/support routed through US team; no IST-aligned local presence

Related insights & playbooks