Automation Integration · head to head
Merge vs Split

Merge
Automation Integration
One API for all your integrations
- From
- Free
- Free plan
- Yes

Split
Testing
Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME
- From
- On request
- Free plan
- No
The short version
- Merge is a unified API platform.
- Merge starts at $650/mo; Split prices on request.
- Only Merge lists unified API; only Split lists feature flags with targeting.
- Where Merge falls short: cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings.
- Prices and features on this page were last checked on 20 November 2026.
How do Merge and Split differ?
Merge and Split differ on starting price (Free against On request), pricing model (Usage-based against Quote) and free tier (Yes against No). Only the attributes on which Merge and Split actually diverge.
Not yet recorded: founded for Split.
Which features does each one have?
They share no listed features; 20 appear only for Merge and 8 only for Split. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Merge
- Unified API
- HRIS integrations
- Accounting integrations
- CRM integrations
- ATS integrations
- Ticketing integrations
- File storage integrations
- Workday
Only in Split
- Feature flags with targeting
- Metrics impact engine
- Guardrail metrics
- Statistical significance testing
- Event ingestion
- SDKs and streaming updates
- Audit and approvals
- Harness platform integration
What is each one used for?
Merge is most often brought in for workflow Automation. The jobs each tool is most often brought in to do.
Merge
- Workflow Automationnot Split
- Data Integrationnot Split
- Process Automationnot Split
- App Integrationnot Split
- API Connectivitynot Split
Split
- A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Merge
- Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Merge
- Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Merge
- A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Merge
Where do Merge and Split fall short?
Merge's most cited limit: cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Merge
- Cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
- Merge holds customer OAuth tokens, creating vendor lock-in; switching providers requires re-authentication from all customers
- No support for legacy systems without APIs; limited to modern SaaS applications
- Pricing complexity at scale with multiple dimensions (workflows, tasks, connectors) affecting costs
Split
- Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
- Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
- The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
- Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
- As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product
How much do Merge and Split cost?
Merge has a free plan, with paid plans from $650/mo; Split is priced on request. Plan by plan below, from each vendor's own pricing page.
Merge
Free- FreeFree
- 1 linked account
- All integrations
- Standard support
- Launch$650/mo
- 50 linked accounts
- All categories
- Email support
- Scale$2,500/mo
- Unlimited accounts
- Priority support
- SLA
- EnterpriseOn request
- Dedicated support
- Custom contracts
- Advanced security
Split
On request- Harness FreeFree
- Harness Open Source and community support
- Intended for individuals and small teams
- Feature management capability limited at this tier
- Harness EssentialsOn request
- Bundled DevOps modules including CI, CD, IaC and security testing
- Standard support
- Pricing requires contacting sales
- Harness EnterpriseOn request
- Mix and match from 15 or more modules including Feature Management and Experimentation
- Premier support with a dedicated account manager
- Higher pipeline concurrency and organisation limits
Which should you pick?
Choose Merge if
- You need unified api.
- You want to start without paying.
- You work on API.
- You also want hris integrations.
Choose Split if
- You need feature flags with targeting.
- You work on Web, API, iOS, Android, Windows.
- You also want metrics impact engine.
Questions people ask
- Is Merge or Split better?
- Neither clearly leads. Merge starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Merge or Split?
- Merge has a free tier; the other does not. Paid plans start at Free for Merge and On request for Split.
- Does Merge or Split run on more platforms?
- Merge runs on API. Split runs on Web, API, iOS, Android, Windows.
- Can I use Merge for free?
- Yes. Merge has a free tier, so you can try it without paying. Split starts at On request.
- What is Merge best used for?
- Merge is most often used for workflow automation, data integration, process automation, app integration. Of those, workflow automation and data integration are not what Split is typically brought in for.
- What can Merge do that Split cannot?
- Merge covers Unified API, HRIS integrations, Accounting integrations, CRM integrations. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.
Answered from the vendors’ own pages
Merge: What is a Linked Account in Merge?
A Linked Account represents an end customer's authenticated connection to a third-party application (like Salesforce, HubSpot, or Zendesk). Merge pricing is based on the number of production Linked Accounts your end users activate.
SourceSplit: Is Split still called Split?
It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.
Merge: Can I access custom data not in Merge's universal schema?
No. Merge works well for standardized integrations but hits limits with enterprise customers. You cannot access data outside Merge's universal schema, cannot customize integration behavior for specific customers, and cannot pull deeply custom data from source systems.
SourceSplit: Can I buy just feature flags?
Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.
Merge: What happens if I switch away from Merge?
Merge holds your customers' OAuth tokens. Switching providers means asking every customer to re-authenticate, resulting in potential customer churn and unhappy users.
Split: What does it do that a plain flag service does not?
It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.
Merge: Does Merge work with legacy systems?
No. Merge only works if there's an API. Legacy ERPs, government portals, insurance carriers, and older enterprise systems that customers depend on often don't have APIs, making Merge unable to support these integrations.
Split: Do we need a lot of traffic?
Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.
Related pages
Other head to heads
- Merge vs Nango
- Merge vs Paragon
- Merge vs Alloy Automation
- Merge vs Zapier
- Merge vs Xano
- Merge vs Cyclr
- Merge vs SnapLogic
- Merge vs Windmill
- Merge vs Jitterbit
- Merge vs Temporal
- Merge vs MuleSoft
- Merge vs Microsoft Power Automate
- Merge vs Hatchet
- Merge vs Informatica
- Merge vs jBPM
- Merge vs Mage AI
- Merge vs Parabola
- Merge vs Prefect
- Merge vs GrowthBook
- Merge vs Kameleoon
- Merge vs Eppo
- Merge vs Katalon
- Merge vs Selenium
- Merge vs Sauce Labs
- Merge vs TestRail
- Merge vs Applitools
- Merge vs CloudBees Smart Tests
- Merge vs QA Wolf
- Merge vs CircleCI
- Merge vs BrowserStack
- Merge vs BugHerd
- Merge vs SoapUI
- Merge vs Playwright
- Merge vs GitHub Actions
- Merge vs Cypress
- Merge vs Appium
- Split vs Nango
- Split vs Paragon
- Split vs Alloy Automation
- Split vs Zapier
- Split vs Xano
- Split vs Cyclr
- Split vs SnapLogic
- Split vs Windmill
- Split vs Jitterbit
- Split vs Temporal
- Split vs MuleSoft
- Split vs Microsoft Power Automate
- Split vs Hatchet
- Split vs Informatica
- Split vs jBPM
- Split vs Mage AI
- Split vs Parabola
- Split vs Prefect
- Split vs GrowthBook
- Split vs Kameleoon
- Split vs Eppo
- Split vs Katalon
- Split vs Selenium
- Split vs Sauce Labs
- Split vs TestRail
- Split vs Applitools
- Split vs CloudBees Smart Tests
- Split vs QA Wolf
- Split vs CircleCI
- Split vs BrowserStack
- Split vs BugHerd
- Split vs SoapUI
- Split vs Playwright
- Split vs GitHub Actions
- Split vs Cypress
- Split vs Appium
