Developer Tools · head to head
Restate vs Thought Machine

Restate
Developer Tools
Durable execution engine in Rust with a free tier and low-latency workflows
- From
- Free
- Free plan
- Yes

Thought Machine
Technology
Cloud native core banking where products are written as smart contracts
- From
- On request
- Free plan
- No
The short version
- Only Restate has a free tier, so it costs nothing to try first.
- Each has a real cost: Restate the runtime is under a Business Source Licence rather than an open source licence, so building a competing managed offering on it is prohibited and some procurement functions will reject it on licence grounds alone.; 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: Restate covers Durable execution, 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 Restate and Thought Machine actually diverge.
| Attribute | Restate | Thought Machine |
|---|---|---|
| Starting price | Free | On request |
| Pricing model | Per month by durable action count | quote |
| Free tier | Yes | No |
| Platforms | Linux, macOS, Web | Web, API, Cloud |
| Category | Developer Tools | Technology |
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 Restate
- Durable execution
- Virtual objects
- Single binary runtime
- Multi-language SDKs
- Workflows and sagas
- Restate Cloud
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.
Restate
- Payment or order flows where a crash between two external API calls must not double-charge or lose the ordernot Thought Machine
- AI agent loops that call tools over minutes or hours and must survive a deployment mid-runnot Thought Machine
- Replacing hand-rolled retry, idempotency key and outbox code across a set of microservicesnot Thought Machine
- A small team that wants durable workflows without operating a Temporal cluster and its databasenot Thought Machine
Thought Machine
- A large bank launching a separate digital brand on a clean core rather than migrating the back booknot Restate
- A bank whose product launches are blocked by vendor change requests on a legacy corenot Restate
- An institution needing real time balances and postings for instant payment obligationsnot Restate
- A group consolidating multiple country cores onto one multi entity platformnot Restate
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Restate
- The runtime is under a Business Source Licence rather than an open source licence, so building a competing managed offering on it is prohibited and some procurement functions will reject it on licence grounds alone.
- Restate Cloud jumps from a free fifty thousand actions straight to 300 US dollars a month for twenty million, so a workload sitting at a few hundred thousand actions pays enterprise-shaped money for hobby-shaped volume.
- It is a young project against Temporal’s established base, so hiring engineers who already know it is unrealistic and the answer to most questions is in the docs rather than on Stack Overflow.
- The programming model requires structuring code around durable handlers and virtual objects, which is a genuine rewrite for existing services rather than a library you add.
- The single-binary simplicity that makes small deployments cheap also means fewer operational knobs at very large scale than a system designed as separable components.
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
Restate
Free- FreeFree
- Fifty thousand durable actions per month
- No credit card required
- Community support
- Starter$300/month
- Twenty million actions per month
- Two hundred actions per second, bursting to one thousand
- Twenty GB storage
- Pro$1000/month
- Fifty million actions per month
- Five hundred actions per second, bursting to two thousand
- Fifty GB storage
- Enterprise$undefined/year
- Negotiated volume
- Twenty-four seven P0 support
- 99.99 per cent SLA
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 Restate if
- You need durable execution.
- You want to start without paying.
- You work on Linux, macOS, Web.
- You also want virtual objects.
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 Restate or Thought Machine better?
- Neither clearly leads. Restate 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, Restate or Thought Machine?
- Restate has a free tier; the other does not. Paid plans start at Free for Restate and On request for Thought Machine.
- Does Restate or Thought Machine run on more platforms?
- Restate runs on Linux, macOS, Web. Thought Machine runs on Web, API, Cloud.
- Can I use Restate for free?
- Yes. Restate has a free tier, so you can try it without paying. Thought Machine starts at On request.
- What is Restate best used for?
- Restate is most often used for payment or order flows where a crash between two external api calls must not double-charge or lose the order, ai agent loops that call tools over minutes or hours and must survive a deployment mid-run, replacing hand-rolled retry, idempotency key and outbox code across a set of microservices, a small team that wants durable workflows without operating a temporal cluster and its database. Of those, payment or order flows where a crash between two external api calls must not double-charge or lose the order and ai agent loops that call tools over minutes or hours and must survive a deployment mid-run are not what Thought Machine is typically brought in for.
- What can Restate do that Thought Machine cannot?
- Restate covers Durable execution, Virtual objects, Single binary runtime, Multi-language SDKs. Thought Machine covers Smart contract product engine, Cloud native architecture, Real time ledger, Vault Payments.
Answered from the vendors’ own pages
Restate: Is Restate open source?
The SDKs are MIT. The runtime is under a Business Source Licence, which permits self-hosting but not offering it as a competing service.
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.
Restate: How does it compare with Temporal?
Same problem, different shape: one Rust binary with embedded storage instead of a server plus database plus workers, and lower per-step latency.
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.
Restate: Is there a free tier?
Yes, fifty thousand durable actions a month on Restate Cloud with no card required.
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.
Restate: Which languages are supported?
TypeScript, Java, Kotlin, Go, Python and Rust.
Related pages
More on Thought Machine
Other head to heads
- Restate vs Helix
- Restate vs Rust
- Restate vs Atlantis
- Restate vs Jitsu
- Restate vs Okteto
- Restate vs Argo CD
- Restate vs Steampipe
- Restate vs Cloud Native Buildpacks
- Restate vs Deno
- Restate vs Visual Studio Code
- Restate vs Turborepo
- Restate vs Keycloak
- Restate vs Garden
- Restate vs GitLab CI/CD
- Restate vs HCP Terraform
- Restate vs Helm
- Restate vs Notepad++
- Restate vs Finxact
- Restate vs Zeta
- Restate vs Alkami
- Restate vs Personetics
- Restate vs Istio
- Restate vs Terraform
- Restate vs Trino
- Restate vs Apache Hadoop
- Restate vs Apache Spark
- Restate vs Mozilla Firefox
- Restate vs Microsoft Outlook
- Restate vs GitHub
- Restate vs Vercel
- Restate vs CloudAMQP
- Restate vs Dropbox
- Restate vs Eclipse
- Restate vs Jenkins
- Thought Machine vs Helix
- Thought Machine vs Rust
- Thought Machine vs Atlantis
- Thought Machine vs Jitsu
- Thought Machine vs Okteto
- Thought Machine vs Argo CD
- Thought Machine vs Steampipe
- Thought Machine vs Cloud Native Buildpacks
- Thought Machine vs Deno
- Thought Machine vs Visual Studio Code
- Thought Machine vs Turborepo
- Thought Machine vs Keycloak
- Thought Machine vs Garden
- Thought Machine vs GitLab CI/CD
- Thought Machine vs HCP Terraform
- Thought Machine vs Helm
- Thought Machine vs Notepad++
- 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 Vercel
- Thought Machine vs CloudAMQP
- Thought Machine vs Dropbox
- Thought Machine vs Eclipse
- Thought Machine vs Jenkins
