Softwr

APIs · head to head

Salt Edge vs Split

Salt Edge logo

Salt Edge

APIs

Independent open banking aggregator covering Europe by PSD2 API and other markets by direct connection

From
On request
Free plan
No
Split logo

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

  • Only Salt Edge lists account information; only Split lists feature flags with targeting.
  • Prices and features on this page were last checked on 20 November 2026.

How do Salt Edge and Split differ?

Salt Edge and Split differ on platforms and category (APIs against Testing). Only the attributes on which Salt Edge and Split actually diverge.

Attributes where Salt Edge and Split differ
AttributeSalt EdgeSplit
PlatformsWeb, APIWeb, API, iOS, Android, Windows
CategoryAPIsTesting

Identical on both: starting price (On request), pricing model (Quote), free tier (No).

Not yet recorded: founded for Split.

Which features does each one have?

They share no listed features; 8 appear only for Salt Edge 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 Salt Edge

  • Account information
  • Payment initiation
  • Wide country coverage
  • Open Banking Gateway
  • Categorisation and enrichment
  • Consent management
  • Partner and white label
  • Sandbox

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?

The jobs each tool is most often brought in to do.

Salt Edge

  • A lender operating across several European and non-EU markets that needs one aggregation contract rather than a different provider per countrynot Split
  • A fintech that wants an aggregator not owned by a card network because its use case competes with card productsnot Split
  • An accounting or treasury product that needs bank feeds in markets the large aggregators do not servenot Split
  • A bank that must publish PSD2-compliant APIs and would rather buy the compliance layer than build itnot Split

Split

  • A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Salt Edge
  • Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Salt Edge
  • Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Salt Edge
  • A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Salt Edge

Where do Salt Edge and Split fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Salt Edge

  • Coverage outside regulated open banking markets is not all direct bank API, and connections that are not regulated interfaces break when a bank changes its systems, so a headline country count overstates the reliability you will actually experience
  • Pricing is not published and is usage-based, so two providers cannot be compared without running both sales processes, and cost grows with the connected user base rather than with revenue
  • Support and engineering are distributed across Eastern Europe and Canada, and buyers in other time zones report slower turnaround on connection-specific breakages than they get from a domestic provider
  • PSD2 consent rules require customers to reauthenticate periodically, and Salt Edge cannot change that, so any product depending on continuous data must design for consent expiry and the drop-off it causes
  • United States coverage is weaker than Plaid or Mastercard Open Banking, so a company with meaningful US volume ends up running two aggregators and normalising between them

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 Salt Edge and Split cost?

Salt Edge is priced on request; Split is priced on request. Plan by plan below, from each vendor's own pricing page.

Salt Edge

On request
  • Salt Edge Open Banking APIOn request
    • Account information and payment initiation
    • Coverage across 50 plus countries
    • Consent management and enrichment

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 Salt Edge if

  • You need account information.
  • You work on Web, API.
  • You also want payment initiation.

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 Salt Edge or Split better?
Neither clearly leads. Salt Edge starts at On request and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Salt Edge or Split?
Salt Edge starts at On request and Split at On request.
Does Salt Edge or Split run on more platforms?
Salt Edge runs on Web, API. Split runs on Web, API, iOS, Android, Windows.
What is Salt Edge best used for?
Salt Edge is most often used for a lender operating across several european and non-eu markets that needs one aggregation contract rather than a different provider per country, a fintech that wants an aggregator not owned by a card network because its use case competes with card products, an accounting or treasury product that needs bank feeds in markets the large aggregators do not serve, a bank that must publish psd2-compliant apis and would rather buy the compliance layer than build it. Of those, a lender operating across several european and non-eu markets that needs one aggregation contract rather than a different provider per country and a fintech that wants an aggregator not owned by a card network because its use case competes with card products are not what Split is typically brought in for.
What can Salt Edge do that Split cannot?
Salt Edge covers Account information, Payment initiation, Wide country coverage, Open Banking Gateway. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

Answered from the vendors’ own pages

Salt Edge: Who owns Salt Edge?

It is independently owned, unlike Tink (Visa), Finicity (Mastercard) or Yodlee (Envestnet), which matters if your use case competes with the owner.

Split: 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.

Salt Edge: Is all coverage direct bank API?

No. Inside PSD2 markets connections use regulated APIs; elsewhere coverage relies on direct connections whose reliability depends on the bank not changing its systems. Ask for a per-institution answer.

Split: Can I buy just feature flags?

Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.

Salt Edge: Does it do payments as well as data?

Yes, payment initiation is supported in European markets where PSD2 applies.

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.

Salt Edge: What does it cost?

Not published. Pricing is usage-based and quoted, though the sandbox is free.

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.

Share

Related pages

Other head to heads