Softwr

Technology · head to head

GitLab vs Thought Machine

GitLab logo

GitLab

Technology

The One DevOps Platform

From
Free
Rated
-
Thought Machine logo

Thought Machine

Technology

Cloud native core banking where products are written as smart contracts

From
On request
Rated
-

The short version

  • Only GitLab has a free tier, so it costs nothing to try first.
  • Each has a real cost: GitLab baseline requires 8 vCPU and 16 GB RAM for single-node installations; resource-intensive; 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: GitLab covers Git repository management, 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 GitLab and Thought Machine actually diverge.

Attributes where GitLab and Thought Machine differ
AttributeGitLabThought Machine
Starting priceFreeOn request
Pricing modelopen-sourcequote
Free tierYesNo
PlatformsLinux, Kubernetes, Docker, Cloud (AWS, GCP, Azure)Web, API, Cloud
Founded2011Unknown

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 GitLab

  • Git repository management
  • CI/CD pipelines
  • Issue tracking
  • Code review
  • Wiki
  • Container registry
  • Security scanning
  • Monitoring

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.

GitLab

  • Git repository management and version controlnot Thought Machine
  • CI/CD pipeline automationnot Thought Machine
  • DevOps and release managementnot Thought Machine
  • Security and compliance workflowsnot Thought Machine

Thought Machine

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

Where each one falls short

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

GitLab

  • Baseline requires 8 vCPU and 16 GB RAM for single-node installations; resource-intensive
  • PostgreSQL is mandatory; no support for alternative databases
  • Redis or Valkey cache required; adds infrastructure complexity
  • High-availability deployments require inter-node latency below 5 ms; difficult to achieve across geographically distributed sites
  • Requires self-hosting and maintenance; GitLab.com SaaS only available to GitLab team members for administration

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

GitLab

Free

No published plan breakdown. See the GitLab review.

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

  • You need git repository management.
  • You want to start without paying.
  • You work on Linux, Kubernetes, Docker, Cloud (AWS, GCP, Azure).
  • You also want ci/cd pipelines.

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 GitLab or Thought Machine better?
Neither clearly leads. GitLab 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, GitLab or Thought Machine?
GitLab has a free tier; the other does not. Paid plans start at Free for GitLab and On request for Thought Machine.
Does GitLab or Thought Machine run on more platforms?
GitLab runs on Linux, Kubernetes, Docker, Cloud (AWS, GCP, Azure). Thought Machine runs on Web, API, Cloud.
Can I use GitLab for free?
Yes. GitLab has a free tier, so you can try it without paying. Thought Machine starts at On request.
What is GitLab best used for?
GitLab is most often used for git repository management and version control, ci/cd pipeline automation, devops and release management, security and compliance workflows. Of those, git repository management and version control and ci/cd pipeline automation are not what Thought Machine is typically brought in for.
What can GitLab do that Thought Machine cannot?
GitLab covers Git repository management, CI/CD pipelines, Issue tracking, Code review. Thought Machine covers Smart contract product engine, Cloud native architecture, Real time ledger, Vault Payments.

Answered from the vendors’ own pages

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.

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.

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

Other head to heads