Softwr

APIs · head to head

Skaleet vs Tuum

Skaleet logo

Skaleet

APIs

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

From
On request
Rated
-
Tuum logo

Tuum

APIs

Modular core banking platform from Estonia, formerly branded Modularbank

From
On request
Rated
-

The short version

  • Each has a real cost: 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.; Tuum it is a smaller, younger company than Mambu, so it has fewer live reference deployments and a shorter track record to evaluate risk against.
  • They diverge on capability: Skaleet covers Cloud-native core, Tuum covers Modular product structure.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Skaleet and Tuum actually diverge.

Attributes where Skaleet and Tuum differ
AttributeSkaleetTuum
PlatformsWeb, REST API, LinuxWeb, API

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 Skaleet

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

Only in Tuum

  • Modular product structure
  • Low-code integration middleware
  • Cloud-agnostic deployment
  • Multi-currency real-time accounts
  • Cards and lending modules
  • Faster migration timeline

What people use each for

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

Skaleet

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

Tuum

  • A bank wanting to migrate specific banking products to the cloud within months rather than replacing its entire core at oncenot Skaleet
  • A fintech in the DACH region or Middle East wanting a European core banking vendor with regional expansion focusnot Skaleet
  • An institution wanting low-code middleware to connect new modules to an existing legacy core rather than a full rebuildnot Skaleet
  • A company researching "Modularbank" that needs to confirm it is the same company now branded Tuumnot Skaleet

Where each one falls short

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

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.

Tuum

  • It is a smaller, younger company than Mambu, so it has fewer live reference deployments and a shorter track record to evaluate risk against.
  • The 2022-era rebrand from Modularbank to Tuum means older funding records, case studies and press coverage appear under a different name, complicating due diligence for anyone unaware of the change.
  • Pricing is entirely unpublished, requiring a sales conversation to budget against competing composable core vendors.
  • Its geographic expansion into DACH and the Middle East is comparatively recent, so support depth and local regulatory expertise in those markets are less proven than in its home Baltic and Nordic base.
  • As with any core banking platform, choosing Tuum is a multi-year infrastructure commitment; switching cores after implementation is a major undertaking regardless of how modular the initial adoption was.

Pricing, plan by plan

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

Tuum

On request
  • Tuum$undefined/year
    • Subscription and module-based pricing, not published
    • Custom quote required via sales

Which should you pick?

Choose Skaleet if

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

Choose Tuum if

  • You need modular product structure.
  • You work on Web, API.
  • You also want low-code integration middleware.

Questions people ask

Is Skaleet or Tuum better?
Neither clearly leads. Skaleet starts at On request and Tuum at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Skaleet or Tuum?
Skaleet starts at On request and Tuum at On request.
Does Skaleet or Tuum run on more platforms?
Skaleet runs on Web, REST API, Linux. Tuum runs on Web, API.
What is Skaleet best used for?
Skaleet is most often used for a banking group launching a digital savings or deposit brand in a new country within a year, a bank modernising payments to iso 20022 without replacing its whole core, a payroll or hr software company adding embedded banking to its product, a payment service provider needing a ledger and accounts under its existing licence. Of those, a banking group launching a digital savings or deposit brand in a new country within a year and a bank modernising payments to iso 20022 without replacing its whole core are not what Tuum is typically brought in for.
What can Skaleet do that Tuum cannot?
Skaleet covers Cloud-native core, Payment hub, Card management, Lending. Tuum covers Modular product structure, Low-code integration middleware, Cloud-agnostic deployment, Multi-currency real-time accounts.

Answered from the vendors’ own pages

Skaleet: What was Skaleet called before?

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

Tuum: Is Tuum the same company as Modularbank?

Yes, Modularbank rebranded to Tuum; it is the same company and platform.

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.

Tuum: Where is it strongest geographically?

Its base is Estonia and the Nordic and Baltic region, with newer expansion into DACH and the Middle East.

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.

Tuum: Is pricing published?

No, subscription and module pricing require a sales conversation.

Share

Related pages

Other head to heads