Softwr

Developer Tools · head to head

Cortex vs Thought Machine

Cortex logo

Cortex

Developer Tools

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

From
On request
Free plan
No
Full reviewWebsite
Thought Machine logo

Thought Machine

Technology

Cloud native core banking where products are written as smart contracts

From
On request
Free plan
No
Full reviewWebsite

The short version

  • Each has a real cost: Cortex pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.; 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: Cortex covers Service catalogue, 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 Cortex and Thought Machine actually diverge.

Attributes where Cortex and Thought Machine differ
AttributeCortexThought Machine
PlatformsWeb, APIWeb, API, Cloud
CategoryDeveloper ToolsTechnology

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 Cortex

  • Service catalogue
  • Scorecards
  • Initiatives
  • Self-service templates
  • Query language
  • Eng intelligence
  • Integrations layer
  • On-call and ownership mapping

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.

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Thought Machine
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Thought Machine
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Thought Machine
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Thought Machine

Thought Machine

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

Where each one falls short

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

Cortex

  • Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
  • The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything.
  • Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue.
  • It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves.
  • Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract.

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

Cortex

On request
  • Cortex$undefined/year
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

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

  • You need service catalogue.
  • You work on Web, API.
  • You also want scorecards.
Cortex 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 Cortex or Thought Machine better?
Neither clearly leads. Cortex 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, Cortex or Thought Machine?
Cortex starts at On request and Thought Machine at On request.
Does Cortex or Thought Machine run on more platforms?
Cortex runs on Web, API. Thought Machine runs on Web, API, Cloud.
What is Cortex best used for?
Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Thought Machine is typically brought in for.
What can Cortex do that Thought Machine cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Thought Machine covers Smart contract product engine, Cloud native architecture, Real time ledger, Vault Payments.

Answered from the vendors’ own pages

Cortex: How is Cortex different from Backstage?

Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.

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.

Cortex: Is pricing published?

No. Cortex requires a sales conversation and prepares a custom proposal.

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.

Cortex: Can it self-host?

It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.

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.

Cortex: What is the main adoption risk?

Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.

Share

Related pages

More on Cortex

More on Thought Machine

Keep looking

Other head to heads