Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Split review

A strong fit for teams that want feature flags and experimentation in one platform.

9.0/10Editor score
Split9.0 Visit Split

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Split is a feature management and experimentation platform for engineering, product, and data teams. It supports feature flag creation, attribute-based targeting, percentage-based rollouts, exposure limits, reusable user segments, and multiple environments. Teams can manage flags programmatically through a REST API and use SDKs across server, browser, mobile, and framework-based applications. The platform is now referred to as Harness Feature Management & Experimentation following Harness's acquisition of Split in June 2024.

For teams evaluating cost and adoption, Split offers a Free Edition after a 30-day trial. Paid plans are available through a contact-sales model rather than a published numeric price. The free entry point can help teams begin with feature management before committing to a paid tier, while the paid option is positioned for organizations that need a larger operational or experimentation setup. Buyers should confirm which capabilities and usage levels apply to their selected plan before purchase.

Split's strongest distinction is the combination of controlled delivery and measurement. Targeting rules, segments, environments, approvals, and audit logs support teams that need oversight around releases, while experimentation and metric impact analysis connect feature changes with product evaluation. Integrations include Slack, Jira, Datadog, New Relic, Sentry, Segment, mParticle, and Amplitude. Teams choosing Split should want experimentation alongside flag management, governance, and ecosystem connections. Organizations seeking only straightforward toggles may find its broader workflow and analysis capabilities unnecessary.

Split pros and cons

  • Where it wins
    • Granular targeting, segments, percentage rollouts, and exposure limits
    • Audit logs and approval workflows support controlled feature changes
    • Experimentation and metric impact analysis extend flag management
  • Where it doesn't
    • Paid plans require contacting sales for pricing
    • The broad feature set may exceed basic flagging needs
    • Governance workflows can add process overhead for small teams

Split fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update