Softwr

APIs · head to head

Skaleet vs Thought Machine

Skaleet logo

Skaleet

APIs

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

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: 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.; 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: Skaleet covers Cloud-native core, 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 Skaleet and Thought Machine actually diverge.

Attributes where Skaleet and Thought Machine differ
AttributeSkaleetThought Machine
PlatformsWeb, REST API, LinuxWeb, 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 Skaleet

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

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.

Skaleet

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

Thought Machine

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

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

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

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 Skaleet if

  • You need cloud-native core.
  • You work on Web, REST API, Linux.
  • You also want payment hub.
Skaleet 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 Skaleet or Thought Machine better?
Neither clearly leads. Skaleet 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, Skaleet or Thought Machine?
Skaleet starts at On request and Thought Machine at On request.
Does Skaleet or Thought Machine run on more platforms?
Skaleet runs on Web, REST API, Linux. Thought Machine runs on Web, API, Cloud.
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 Thought Machine is typically brought in for.
What can Skaleet do that Thought Machine cannot?
Skaleet covers Cloud-native core, Payment hub, Card management, Lending. Thought Machine covers Smart contract product engine, Cloud native architecture, Real time ledger, Vault Payments.

Answered from the vendors’ own pages

Skaleet: What was Skaleet called before?

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

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.

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.

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.

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.

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 Skaleet

More on Thought Machine

Keep looking

Other head to heads