Softwr

APIs · head to head

Temenos Transact vs Tuum

Temenos Transact logo

Temenos Transact

APIs

Established core banking system used by banks in over a hundred countries

From
On request
Rated
-
Full reviewWebsite
Tuum logo

Tuum

APIs

Modular core banking platform from Estonia, formerly branded Modularbank

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Temenos Transact the codebase originates in the 1990s, so banks on older releases face major upgrade programmes to reach current versions, and many defer them for years.; 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: Temenos Transact covers Country model banks, Tuum covers Modular product structure.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Temenos Transact and Tuum actually diverge.

Attributes where Temenos Transact and Tuum differ
AttributeTemenos TransactTuum
PlatformsWeb, Linux, Windows, REST APIWeb, 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 Temenos Transact

  • Country model banks
  • Multi-product core
  • Payments processing
  • API layer
  • Cloud deployment
  • Accounting engine

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.

Temenos Transact

  • A bank in an emerging market needing local regulatory compliance without building it from scratchnot Tuum
  • An institution running Islamic banking products alongside conventional ones on one corenot Tuum
  • A bank that needs a large pool of experienced implementation consultants to de-risk a migrationnot Tuum
  • A group standardising subsidiaries in several countries onto one core banking systemnot Tuum

Tuum

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

Where each one falls short

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

Temenos Transact

  • The codebase originates in the 1990s, so banks on older releases face major upgrade programmes to reach current versions, and many defer them for years.
  • Total cost is dominated by implementation partner fees rather than licence, and those programmes routinely overrun their original estimates.
  • Product changes that cloud-native cores treat as configuration can require development work and a release cycle, which slows time to market for new products.
  • Heavy customisation is common and it makes every subsequent upgrade harder, creating a compounding cost that banks feel a decade after go-live.
  • Temenos has repeatedly restructured its product line and naming, so buyers must check carefully which components a proposal actually includes and which are separately licensed.

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

Temenos Transact

On request
  • Temenos Transact$undefined/year
    • Perpetual or subscription licence scaled by assets, accounts or users
    • Annual maintenance typically a percentage of licence value
    • Implementation delivered by partners and charged separately

Tuum

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

Which should you pick?

Choose Temenos Transact if

  • You need country model banks.
  • You work on Web, Linux, Windows, REST API.
  • You also want multi-product core.
Temenos Transact review

Choose Tuum if

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

Questions people ask

Is Temenos Transact or Tuum better?
Neither clearly leads. Temenos Transact 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, Temenos Transact or Tuum?
Temenos Transact starts at On request and Tuum at On request.
Does Temenos Transact or Tuum run on more platforms?
Temenos Transact runs on Web, Linux, Windows, REST API. Tuum runs on Web, API.
What is Temenos Transact best used for?
Temenos Transact is most often used for a bank in an emerging market needing local regulatory compliance without building it from scratch, an institution running islamic banking products alongside conventional ones on one core, a bank that needs a large pool of experienced implementation consultants to de-risk a migration, a group standardising subsidiaries in several countries onto one core banking system. Of those, a bank in an emerging market needing local regulatory compliance without building it from scratch and an institution running islamic banking products alongside conventional ones on one core are not what Tuum is typically brought in for.
What can Temenos Transact do that Tuum cannot?
Temenos Transact covers Country model banks, Multi-product core, Payments processing, API layer. Tuum covers Modular product structure, Low-code integration middleware, Cloud-agnostic deployment, Multi-currency real-time accounts.

Answered from the vendors’ own pages

Temenos Transact: Is Transact the same as T24?

Yes. T24 was renamed Temenos Transact; older installations and much of the consultant population still use the T24 name.

Tuum: Is Tuum the same company as Modularbank?

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

Temenos Transact: Can it run in the cloud?

Yes, it is offered on public cloud, though many existing installations remain on-premises and moving them is a project.

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.

Temenos Transact: What drives the cost?

Licence scaled by size, annual maintenance as a percentage of licence, and implementation partner fees that usually exceed the software cost.

Tuum: Is pricing published?

No, subscription and module pricing require a sales conversation.

Share

Related pages

More on Temenos Transact

More on Tuum

Keep looking

Other head to heads