Technology · head to head
Postgres vs Thought Machine

Thought Machine
Technology
Cloud native core banking where products are written as smart contracts
- From
- On request
- Rated
- -
The short version
- Only Postgres has a free tier, so it costs nothing to try first.
- Each has a real cost: Postgres each major version is supported for only 5 years after its initial release, after which it is end-of-life; 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: Postgres covers ACID compliance, 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 Postgres and Thought Machine actually diverge.
| Attribute | Postgres | Thought Machine |
|---|---|---|
| Starting price | Free | On request |
| Pricing model | open-source | quote |
| Free tier | Yes | No |
| Platforms | Linux, Windows, Macos, Docker | Web, API, Cloud |
| Founded | 1996 | Unknown |
Identical on both: user rating (Not yet rated), category (Technology).
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 Postgres
- ACID compliance
- Complex queries
- Foreign keys
- Triggers
- Views
- Stored procedures
- JSON/JSONB support
- Full-text search
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.
Postgres
- Running a general purpose relational database for applicationsnot Thought Machine
- Self-hosting an open source SQL database with no licence feenot Thought Machine
- Workloads needing extensions, JSON and full text search in one enginenot Thought Machine
Thought Machine
- A large bank launching a separate digital brand on a clean core rather than migrating the back booknot Postgres
- A bank whose product launches are blocked by vendor change requests on a legacy corenot Postgres
- An institution needing real time balances and postings for instant payment obligationsnot Postgres
- A group consolidating multiple country cores onto one multi entity platformnot Postgres
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Postgres
- Each major version is supported for only 5 years after its initial release, after which it is end-of-life
- Major version upgrades break on-disk compatibility and require a full dump and reload or the pg_upgrade tool
- New major versions ship about once a year, so staying supported means a disruptive upgrade cycle
- Minor releases contain only frequently-encountered bug fixes, low-risk fixes, security issues and data corruption fixes, so feature gaps are not addressed within a major version
- There is no vendor SLA; commercial support must be bought separately from third party professional services listed by the project
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
Postgres
Free- Community EditionFree
- Full database features
- No limitations
- Community support
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 Postgres if
- You need acid compliance.
- You want to start without paying.
- You work on Linux, Windows, Macos, Docker.
- You also want complex queries.
Choose Thought Machine if
- You need smart contract product engine.
- You work on Web, API, Cloud.
- You also want cloud native architecture.
Questions people ask
- Is Postgres or Thought Machine better?
- Neither clearly leads. Postgres starts at Free and Thought Machine at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Postgres or Thought Machine?
- Postgres has a free tier; the other does not. Paid plans start at Free for Postgres and On request for Thought Machine.
- Does Postgres or Thought Machine run on more platforms?
- Postgres runs on Linux, Windows, Macos, Docker. Thought Machine runs on Web, API, Cloud.
- Can I use Postgres for free?
- Yes. Postgres has a free tier, so you can try it without paying. Thought Machine starts at On request.
- What is Postgres best used for?
- Postgres is most often used for running a general purpose relational database for applications, self-hosting an open source sql database with no licence fee, workloads needing extensions, json and full text search in one engine. Of those, running a general purpose relational database for applications and self-hosting an open source sql database with no licence fee are not what Thought Machine is typically brought in for.
- What can Postgres do that Thought Machine cannot?
- Postgres covers ACID compliance, Complex queries, Foreign keys, Triggers. Thought Machine covers Smart contract product engine, Cloud native architecture, Real time ledger, Vault Payments.
Answered from the vendors’ own pages
Postgres: How much does PostgreSQL cost to use?
PostgreSQL is completely free to download, install, and use. No licensing fees, subscription costs, or per-seat charges apply. The database is open source under the PostgreSQL License. Source: https://www.postgresql.org
SourceThought 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.
Postgres: Are there commercial PostgreSQL support options available?
Official PostgreSQL (the project) is free. Commercial PostgreSQL services such as hosting, professional support, training, and managed database services are offered by third-party vendors, not the PostgreSQL project itself. Source: https://www.postgresql.org
SourceThought 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.
Postgres: Do I need a license to use PostgreSQL commercially?
No. PostgreSQL is open source under the PostgreSQL License, which permits free commercial use without royalties, licensing fees, or support obligations. Source: https://www.postgresql.org
SourceThought 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.
Related pages
More on Thought Machine
Other head to heads
- Postgres vs Linear
- Postgres vs Asana
- Postgres vs ClickUp
- Postgres vs Figma
- Postgres vs Supabase
- Postgres vs Redis
- Postgres vs Aha!
- Postgres vs Eclipse
- Postgres vs Excalidraw
- Postgres vs MongoDB
- Postgres vs Okta
- Postgres vs Notion
- Postgres vs Close
- Postgres vs Coda
- Postgres vs Drift
- Postgres vs JetBrains IntelliJ IDEA
- Postgres vs LogRocket
- Postgres vs Neovim
- Postgres vs Finxact
- Postgres vs Zeta
- Postgres vs Alkami
- Postgres vs Personetics
- Postgres vs Istio
- Postgres vs Terraform
- Postgres vs Trino
- Postgres vs Apache Hadoop
- Postgres vs Apache Spark
- Postgres vs Mozilla Firefox
- Postgres vs Microsoft Outlook
- Postgres vs GitHub
- Postgres vs Attio
- Postgres vs CloudAMQP
- Postgres vs Dropbox
- Postgres vs Jenkins
- Postgres vs Miro
- Thought Machine vs Linear
- Thought Machine vs Asana
- Thought Machine vs ClickUp
- Thought Machine vs Figma
- Thought Machine vs Supabase
- Thought Machine vs Redis
- Thought Machine vs Aha!
- Thought Machine vs Eclipse
- Thought Machine vs Excalidraw
- Thought Machine vs MongoDB
- Thought Machine vs Okta
- Thought Machine vs Notion
- Thought Machine vs Close
- Thought Machine vs Coda
- Thought Machine vs Drift
- Thought Machine vs JetBrains IntelliJ IDEA
- Thought Machine vs LogRocket
- Thought Machine vs Neovim
- Thought Machine vs Finxact
- Thought Machine vs Zeta
- Thought Machine vs Alkami
- Thought Machine vs Personetics
- Thought Machine vs Istio
- Thought Machine vs Terraform
- Thought Machine vs Trino
- Thought Machine vs Apache Hadoop
- Thought Machine vs Apache Spark
- Thought Machine vs Mozilla Firefox
- Thought Machine vs Microsoft Outlook
- Thought Machine vs GitHub
- Thought Machine vs Attio
- Thought Machine vs CloudAMQP
- Thought Machine vs Dropbox
- Thought Machine vs Jenkins
- Thought Machine vs Miro

