Softwr

APIs · head to head

Episode Six vs Skaleet

Episode Six logo

Episode Six

APIs

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

From
On request
Rated
-
Full reviewWebsite
Skaleet logo

Skaleet

APIs

Cloud-native core banking and payment hub with deployments measured in months

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Skaleet the installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.
  • They diverge on capability: Episode Six covers Tritium API platform, Skaleet covers Cloud-native core.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Episode Six and Skaleet actually diverge.

Attributes where Episode Six and Skaleet differ
AttributeEpisode SixSkaleet
PlatformsWeb, API, On-premiseWeb, REST API, Linux

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (APIs).

What each one covers

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 Skaleet

  • Cloud-native core
  • Payment hub
  • Card management
  • Lending
  • API-first
  • Configurable products

What people use each for

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 Skaleet
  • A large institution replacing a legacy card processor without moving off its own infrastructurenot Skaleet
  • A telco or airline launching a branded wallet and card product at national scalenot Skaleet
  • A bank running prepaid, debit and credit products that wants them on one ledger rather than three processorsnot Skaleet

Skaleet

  • A banking group launching a digital savings or deposit brand in a new country within a yearnot Episode Six
  • A bank modernising payments to ISO 20022 without replacing its whole corenot Episode Six
  • A payroll or HR software company adding embedded banking to its productnot Episode Six
  • A payment service provider needing a ledger and accounts under its existing licencenot Episode Six

Where each one falls 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.

Skaleet

  • The installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.
  • Speed references are mostly greenfield launches inside large groups, which is an easier problem than migrating an existing book off a legacy core.
  • It is European-centric, with payment rails and regulatory work concentrated on SEPA and EU requirements rather than global coverage.
  • As a smaller vendor carrying a bank core, it attracts hard concentration and viability questions in procurement that larger competitors do not face.
  • Pricing is unpublished and scaled by accounts and transactions, so a bank whose volumes grow faster than forecast faces cost escalation it did not model.

Pricing, plan by plan

Episode Six

On request
  • Tritium platform$undefined/year
    • 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

Skaleet

On request
  • Skaleet Core Banking Platform$undefined/year
    • Subscription licence scaled by accounts and transaction volume
    • Payment hub licensable separately from the full core
    • Implementation and configuration charged as a project

Which should you pick?

Choose Episode Six if

  • You need tritium api platform.
  • You work on Web, API, On-premise.
  • You also want flexible deployment.
Episode Six review

Choose Skaleet if

  • You need cloud-native core.
  • You work on Web, REST API, Linux.
  • You also want payment hub.
Skaleet review

Questions people ask

Is Episode Six or Skaleet better?
Neither clearly leads. Episode Six starts at On request and Skaleet at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Episode Six or Skaleet?
Episode Six starts at On request and Skaleet at On request.
Does Episode Six or Skaleet run on more platforms?
Episode Six runs on Web, API, On-premise. Skaleet runs on Web, REST API, Linux.
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 Skaleet is typically brought in for.
What can Episode Six do that Skaleet cannot?
Episode Six covers Tritium API platform, Flexible deployment, Multi product issuing, Digital wallets. Skaleet covers Cloud-native core, Payment hub, Card management, Lending.

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.

Skaleet: What was Skaleet called before?

TagPay. The company rebranded to Skaleet while keeping the same platform lineage.

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.

Skaleet: Can I buy just the payment hub?

Yes. The payment engine is licensable standalone and can sit over an existing core, which is a common first step.

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.

Skaleet: How fast are real deployments?

Named European deployments have gone live in six to twelve months, including a Crédit Agricole savings platform live in Germany in eight months.

Share

Related pages

More on Episode Six

More on Skaleet

Keep looking

Other head to heads