Softwr

APIs · head to head

Temenos Transact vs Thought Machine

Temenos Transact logo

Temenos Transact

APIs

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

From
On request
Rated
-
Full reviewWebsite
Thought Machine logo

Thought Machine

Technology

Cloud native core banking where products are written as smart contracts

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.; Thought Machine a core replacement is a two to four year programme at an established bank, and the licence is a minority of total cost against system integrator fees, parallel running and data migration.
  • They diverge on capability: Temenos Transact covers Country model banks, Thought Machine covers Smart contract product engine.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Temenos Transact and Thought Machine actually diverge.

Attributes where Temenos Transact and Thought Machine differ
AttributeTemenos TransactThought Machine
PlatformsWeb, Linux, Windows, REST APIWeb, API, Cloud
CategoryAPIsTechnology

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

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 Thought Machine

  • Smart contract product engine
  • Cloud native architecture
  • Real time ledger
  • Vault Payments
  • API first design
  • Multi entity and multi currency
  • Product versioning and testing
  • Configurable posting rules

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 Thought Machine
  • An institution running Islamic banking products alongside conventional ones on one corenot Thought Machine
  • A bank that needs a large pool of experienced implementation consultants to de-risk a migrationnot Thought Machine
  • A group standardising subsidiaries in several countries onto one core banking systemnot Thought Machine

Thought Machine

  • A large bank launching a separate digital brand on a clean core rather than migrating the back booknot Temenos Transact
  • A bank whose product launches are blocked by vendor change requests on a legacy corenot Temenos Transact
  • An institution needing real time balances and postings for instant payment obligationsnot Temenos Transact
  • A group consolidating multiple country cores onto one multi entity platformnot 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.

Thought Machine

  • A core replacement is a two to four year programme at an established bank, and the licence is a minority of total cost against system integrator fees, parallel running and data migration.
  • The smart contract model presumes a bank can write and maintain Python financial products, and institutions without that engineering capability end up outsourcing the very flexibility they bought.
  • Cloud infrastructure cost sits with the bank and is not trivial at scale, so total cost of ownership comparisons against a hosted legacy core often miss a large recurring line.
  • Thought Machine has made two rounds of job cuts pursuing profitability, which is a legitimate supplier stability concern for a system a bank expects to run for fifteen years.
  • The functional footprint is core ledger and product engine, so origination, collections, regulatory reporting and channels all come from other vendors, and the integration estate around Vault is the bank's problem to design and own.

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

Thought Machine

On request
  • Vault Core$undefined/year
    • Quoted per institution, typically on account volumes or annual contract value
    • Implementation and system integrator costs commonly exceed the licence fee
    • Cloud infrastructure costs are the bank's and are not included

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 Thought Machine if

  • You need smart contract product engine.
  • You work on Web, API, Cloud.
  • You also want cloud native architecture.
Thought Machine review

Questions people ask

Is Temenos Transact or Thought Machine better?
Neither clearly leads. Temenos Transact starts at On request and Thought Machine at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Temenos Transact or Thought Machine?
Temenos Transact starts at On request and Thought Machine at On request.
Does Temenos Transact or Thought Machine run on more platforms?
Temenos Transact runs on Web, Linux, Windows, REST API. Thought Machine runs on Web, API, Cloud.
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 Thought Machine is typically brought in for.
What can Temenos Transact do that Thought Machine cannot?
Temenos Transact covers Country model banks, Multi-product core, Payments processing, API layer. Thought Machine covers Smart contract product engine, Cloud native architecture, Real time ledger, Vault Payments.

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.

Thought Machine: Is Vault Core genuinely cloud native?

Yes. It is containerised, runs on Kubernetes on public cloud, and posts in real time rather than in overnight batch.

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.

Thought Machine: How long does a migration take?

Eighteen months at the absolute fastest for a narrow greenfield launch; two to four years for a phased migration at an established bank.

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.

Thought Machine: Does the licence fee represent the total cost?

No. Implementation, system integration, parallel running and cloud infrastructure typically cost more than the licence over the programme.

Share

Related pages

More on Temenos Transact

More on Thought Machine

Keep looking

Other head to heads