Softwr

APIs · head to head

Episode Six vs Split

Episode Six logo

Episode Six

APIs

Payment processing and ledger platform deployable on premise or in your own cloud

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 Episode Six lists flexible deployment; only Split lists feature flags with targeting.
  • Prices and features on this page were last checked on 20 November 2026.

How do Episode Six and Split differ?

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

Attributes where Episode Six and Split differ
AttributeEpisode SixSplit
PlatformsWeb, API, Self-hostedWeb, API, iOS, Android, Windows
CategoryAPIsTesting

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

Which features does each one have?

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

  • Tritium API platform
  • Flexible deployment
  • Multi product issuing
  • Digital wallets
  • Multi currency ledger
  • Network connectivity
  • Configurable product engine
  • Institutional controls

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?

Episode Six is most often brought in for A telco or airline launching a branded wallet and card product at national scale. The jobs each tool is most often brought in to do.

Episode Six

  • A bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloudnot Split
  • A large institution replacing a legacy card processor without moving off its own infrastructurenot Split
  • A telco or airline launching a branded wallet and card product at national scalenot Split
  • A bank running prepaid, debit and credit products that wants them on one ledger rather than three processorsnot Split

Split

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

Where do Episode Six and Split fall short?

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

Episode Six

  • Deployment on premise or in a private tenancy means the institution carries infrastructure, upgrade and PCI scope work that a hosted processor would absorb
  • Implementation runs to quarters and involves core banking, network certification and fraud system integration, so time to first card is far longer than with a self serve issuer processor
  • Pricing is entirely bespoke and weighted to large programmes, which prices out fintechs and small issuers who would be better served by a hosted platform
  • Being smaller than the incumbent processors, its network certifications and operational presence vary by region, so a global rollout can find gaps in specific markets
  • The flexibility of six hundred APIs and a configurable product engine shifts design responsibility onto the buyer, and institutions without strong internal payments architects end up dependent on professional services

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 Episode Six and Split cost?

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

Episode Six

On request
  • Tritium platformOn request
    • Licence and implementation quoted per institution
    • Deployment model affects cost materially: on premise, private cloud or hosted
    • Processing fees typically per transaction or per active card

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 Episode Six if

  • You need tritium api platform.
  • You work on Web, API, Self-hosted.
  • You also want flexible deployment.

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 Episode Six or Split better?
Neither clearly leads. Episode Six 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, Episode Six or Split?
Episode Six starts at On request and Split at On request.
Does Episode Six or Split run on more platforms?
Episode Six runs on Web, API, Self-hosted. Split runs on Web, API, iOS, Android, Windows.
What is Episode Six best used for?
Episode Six is most often used for a bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloud, a large institution replacing a legacy card processor without moving off its own infrastructure, a telco or airline launching a branded wallet and card product at national scale, a bank running prepaid, debit and credit products that wants them on one ledger rather than three processors. Of those, a bank in a jurisdiction with data residency rules that forbid processing customer data in a shared multi tenant cloud and a large institution replacing a legacy card processor without moving off its own infrastructure are not what Split is typically brought in for.
What can Episode Six do that Split cannot?
Episode Six covers Tritium API platform, Flexible deployment, Multi product issuing, Digital wallets. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

Answered from the vendors’ own pages

Episode Six: Can Episode Six run inside our own data centre?

Yes. On premise and private cloud deployment is the main reason banks choose it over hosted only processors.

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.

Episode Six: Is it suitable for a startup issuing its first cards?

Not really. The licence, implementation timeline and cost are aimed at banks and large institutions.

Split: Can I buy just feature flags?

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

Episode Six: Do we still need a card licence or sponsor?

Yes. Episode Six is a processor. Network membership, licensing or a sponsor arrangement remains your responsibility.

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.

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