Softwr

Developer Tools · head to head

Hookdeck vs Thought Machine

Hookdeck logo

Hookdeck

Developer Tools

Event gateway that receives, queues, retries and replays inbound webhooks

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

  • Only Hookdeck has a free tier, so it costs nothing to try first.
  • Each has a real cost: Hookdeck pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.; 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: Hookdeck covers Ingest and persist, 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 Hookdeck and Thought Machine actually diverge.

Attributes where Hookdeck and Thought Machine differ
AttributeHookdeckThought Machine
Starting priceFreeOn request
Pricing modelPer month by delivered event countquote
Free tierYesNo
PlatformsWeb, Linux, macOS, WindowsWeb, API, Cloud
CategoryDeveloper ToolsTechnology

Identical on both: 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 Hookdeck

  • Ingest and persist
  • Automatic retries
  • Filters and fan-out
  • Transformations
  • Local development CLI
  • Rate limiting

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.

Hookdeck

  • A payments integration where losing a Stripe event during a deploy causes an order to go unfulfillednot Thought Machine
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot Thought Machine
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Thought Machine
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot Thought Machine

Thought Machine

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

Where each one falls short

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

Hookdeck

  • Pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • Free-tier retention is three days, which is shorter than the time it typically takes to notice a failing integration, so the payloads needed for a replay are often already gone.
  • It becomes a single point of failure in front of every third-party integration, and an outage there means every provider webhook queues or fails at once.
  • The transformation layer runs JavaScript in a constrained environment, so anything that needs a database lookup or an external call has to happen downstream instead.
  • For a team already running Kafka or SQS the value is mostly the console and the replay UI, which is a hard cost to justify against infrastructure they already operate.

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

Hookdeck

Free
  • DeveloperFree
    • Up to ten thousand events per month
    • Three-day retention
    • One user
  • Team$39/month
    • Ten thousand events included
    • Unlimited users
    • Pay as you go metering above the included events
  • Growth$499/month
    • Ten thousand events included plus metered usage
    • Thirty-day retention
    • Uptime and latency SLAs
  • Enterprise$undefined/year
    • Negotiated event volume
    • Custom retention
    • Dedicated 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 Hookdeck if

  • You need ingest and persist.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows.
  • You also want automatic retries.
Hookdeck 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 Hookdeck or Thought Machine better?
Neither clearly leads. Hookdeck 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, Hookdeck or Thought Machine?
Hookdeck has a free tier; the other does not. Paid plans start at Free for Hookdeck and On request for Thought Machine.
Does Hookdeck or Thought Machine run on more platforms?
Hookdeck runs on Web, Linux, macOS, Windows. Thought Machine runs on Web, API, Cloud.
Can I use Hookdeck for free?
Yes. Hookdeck has a free tier, so you can try it without paying. Thought Machine starts at On request.
What is Hookdeck best used for?
Hookdeck is most often used for a payments integration where losing a stripe event during a deploy causes an order to go unfulfilled, fanning one provider webhook out to several internal services without each subscribing separately, debugging a partner integration by replaying the exact failing payload after shipping a fix, receiving production-shaped webhooks on a developer laptop without running a public tunnel. Of those, a payments integration where losing a stripe event during a deploy causes an order to go unfulfilled and fanning one provider webhook out to several internal services without each subscribing separately are not what Thought Machine is typically brought in for.
What can Hookdeck do that Thought Machine cannot?
Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations. Thought Machine covers Smart contract product engine, Cloud native architecture, Real time ledger, Vault Payments.

Answered from the vendors’ own pages

Hookdeck: Is there a free plan?

Yes, ten thousand events a month with three-day retention and one user.

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.

Hookdeck: How is usage counted?

By delivered events, so a single inbound webhook fanned out to three destinations counts as three.

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.

Hookdeck: Can I replay a failed webhook?

Yes, individually or in bulk from the console, with the original payload.

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.

Hookdeck: Does it work for outbound webhooks too?

Yes, the same queueing, retry and observability applies to webhooks you send.

Share

Related pages

More on Hookdeck

More on Thought Machine

Keep looking

Other head to heads