Softwr

Technology · head to head

Height vs Thought Machine

H

Height

Technology

A project management tool from a small independent vendor that uses AI agents to handle routine ticket maintenance.

From
Free
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

  • Only Height has a free tier, so it costs nothing to try first.
  • Each has a real cost: Height it is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.; 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: Height covers Autonomous triage, 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 Height and Thought Machine actually diverge.

Attributes where Height and Thought Machine differ
AttributeHeightThought Machine
Starting priceFreeOn request
Pricing modelUnknownquote
Free tierYesNo
PlatformsWebWeb, API, Cloud
Founded2018Unknown

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 Height

  • Autonomous triage
  • Duplicate detection
  • Attribute maintenance
  • Per-task chat
  • Multiple views
  • Developer integrations
  • Custom fields and filters
  • Public API

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.

Height

  • A product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has timenot Thought Machine
  • Teams leaving Jira because its configuration and administration cost more attention than the tracking is worthnot Thought Machine
  • A support or intake queue where incoming requests need categorising and deduplicating before anyone can plan themnot Thought Machine
  • Startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat appnot Thought Machine

Thought Machine

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

Where each one falls short

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

Height

  • It is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.
  • The 2024 relaunch as Height 2.0 reoriented the product around AI agents and changed workflows customers had already built on, which is the clearest available evidence of how much the product may be re-shaped again under you.
  • The ecosystem is small next to Jira, Linear and Asana: fewer third-party integrations, no consultancy market, and far less written material to search when something behaves unexpectedly, so support questions go to the vendor and wait.
  • The automation only pays off if tasks contain enough substance for a model to work with; on a team whose tickets are two-word titles, the agents have nothing to triage or deduplicate and the product reduces to an ordinary tracker at a premium.
  • Task content is processed by hosted large language models, so a security review becomes a question about subprocessors and data handling, and there is no self-hosted or on-premises deployment to fall back on if the answer is unacceptable.
  • There is no widely used two-way synchronisation with Jira, so an organisation where one team adopts Height and the rest stay on Jira ends up with two systems of record and manual reconciliation between them.

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

Height

Free

No published plan breakdown. See the Height 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 Height if

  • You need autonomous triage.
  • You want to start without paying.
  • You also want duplicate detection.
Height 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 Height or Thought Machine better?
Neither clearly leads. Height 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, Height or Thought Machine?
Height has a free tier; the other does not. Paid plans start at Free for Height and On request for Thought Machine.
Does Height or Thought Machine run on more platforms?
Height runs on Web. Thought Machine runs on Web, API, Cloud.
Can I use Height for free?
Yes. Height has a free tier, so you can try it without paying. Thought Machine starts at On request.
What is Height best used for?
Height is most often used for a product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has time, teams leaving jira because its configuration and administration cost more attention than the tracking is worth, a support or intake queue where incoming requests need categorising and deduplicating before anyone can plan them, startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat app. Of those, a product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has time and teams leaving jira because its configuration and administration cost more attention than the tracking is worth are not what Thought Machine is typically brought in for.
What can Height do that Thought Machine cannot?
Height covers Autonomous triage, Duplicate detection, Attribute maintenance, Per-task chat. Thought Machine covers Smart contract product engine, Cloud native architecture, Real time ledger, Vault Payments.

Answered from the vendors’ own pages

Height: How is this different from Jira automation?

Jira automation is rule-based: you define a trigger and an action. Height's agents read the content of tasks and act on judgement, such as recognising that two tickets describe the same bug, which no rule can express.

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.

Height: Can we self-host it?

No. It is software as a service only, with no on-premises or private-cloud deployment. If your requirements rule out a hosted tracker, this is not a candidate.

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.

Height: What happens to our data if the company fails?

You would need an export and a migration to another tool. This is the standard risk with a single-product startup, and it is worth confirming the export path covers task history, comments and custom fields before committing to it.

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.

Height: Does it work for non-engineering teams?

Yes, the views and custom fields are generic enough for marketing, operations or support queues. Its integrations, though, are aimed at software teams, so a non-engineering team gets less of the surrounding value.

Height: Do the AI features need our tickets to be well written?

In practice, yes. Triage, deduplication and attribute maintenance work from what is written in the task, so the return is much higher on a team that already writes descriptive tickets than on one that does not.

Share

Related pages

More on Height

More on Thought Machine

Keep looking

Other head to heads