Softwr

Cybersecurity · head to head

Feedzai vs Restate

Feedzai logo

Feedzai

Cybersecurity

Real-time transaction fraud and financial crime detection for banks and payment processors

From
On request
Free plan
No
Restate logo

Restate

Developer Tools

Durable execution engine in Rust with a free tier and low-latency workflows

From
Free
Free plan
Yes

The short version

  • Only Restate has a free tier, so it costs nothing to try first.
  • Each has a real cost: Feedzai pricing is per transaction with an annual minimum, so a bank with seasonal or growing volume commits to a floor it may not use and pays overage above the band.; 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.
  • They diverge on capability: Feedzai covers Real-time scoring, Restate covers Durable execution.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Feedzai and Restate actually diverge.

Attributes where Feedzai and Restate differ
AttributeFeedzaiRestate
Starting priceOn requestFree
Pricing modelquotePer month by durable action count
Free tierNoYes
PlatformsWeb, LinuxLinux, macOS, Web
CategoryCybersecurityDeveloper Tools

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 Feedzai

  • Real-time scoring
  • Rule and model hybrid
  • Case manager
  • Behavioural biometrics
  • Model explainability
  • Deployment options

Only in Restate

  • Durable execution
  • Virtual objects
  • Single binary runtime
  • Multi-language SDKs
  • Workflows and sagas
  • Restate Cloud

What people use each for

The jobs each tool is most often brought in to do.

Feedzai

  • A bank joining an instant payments scheme where transfers are irrevocable and post-hoc recovery is impossiblenot Restate
  • A card issuer whose existing rules engine cannot be changed without a release, so fraud waves run for daysnot Restate
  • An acquirer needing per-merchant risk models rather than one portfolio-wide modelnot Restate
  • A bank required by its regulator to explain automated declines to customers, which rules out opaque scoringnot Restate

Restate

  • Payment or order flows where a crash between two external API calls must not double-charge or lose the ordernot Feedzai
  • AI agent loops that call tools over minutes or hours and must survive a deployment mid-runnot Feedzai
  • Replacing hand-rolled retry, idempotency key and outbox code across a set of microservicesnot Feedzai
  • A small team that wants durable workflows without operating a Temporal cluster and its databasenot Feedzai

Where each one falls short

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

Feedzai

  • Pricing is per transaction with an annual minimum, so a bank with seasonal or growing volume commits to a floor it may not use and pays overage above the band.
  • It sits in the authorisation path, which makes every upgrade a change-controlled event with rollback plans, and the operational burden falls on the bank rather than the vendor.
  • Out of the box models need months of the customer own labelled fraud history before they beat the rules they replace, so the value case starts late.
  • AML and fraud are licensed as separate modules, so institutions expecting one platform fee find the transaction monitoring capability is a second line item.
  • The buyer profile is large institutions, so smaller banks and fintechs face minimums that make per-transaction economics unattractive below significant scale.

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.

Pricing, plan by plan

Feedzai

On request
  • Feedzai Financial Crime Platform$undefined/year
    • Priced by transaction volume with annual minimum commitment
    • Modules for fraud, AML and account opening licensed separately
    • Cloud, private cloud and on-premises deployment

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

Which should you pick?

Choose Feedzai if

  • You need real-time scoring.
  • You work on Web, Linux.
  • You also want rule and model hybrid.

Choose Restate if

  • You need durable execution.
  • You want to start without paying.
  • You work on Linux, macOS, Web.
  • You also want virtual objects.

Questions people ask

Is Feedzai or Restate better?
Neither clearly leads. Feedzai starts at On request and Restate at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Feedzai or Restate?
Restate has a free tier; the other does not. Paid plans start at On request for Feedzai and Free for Restate.
Does Feedzai or Restate run on more platforms?
Feedzai runs on Web, Linux. Restate runs on Linux, macOS, Web.
Can I use Restate for free?
Yes. Restate has a free tier, so you can try it without paying. Feedzai starts at On request.
What is Feedzai best used for?
Feedzai is most often used for a bank joining an instant payments scheme where transfers are irrevocable and post-hoc recovery is impossible, a card issuer whose existing rules engine cannot be changed without a release, so fraud waves run for days, an acquirer needing per-merchant risk models rather than one portfolio-wide model, a bank required by its regulator to explain automated declines to customers, which rules out opaque scoring. Of those, a bank joining an instant payments scheme where transfers are irrevocable and post-hoc recovery is impossible and a card issuer whose existing rules engine cannot be changed without a release, so fraud waves run for days are not what Restate is typically brought in for.
What can Feedzai do that Restate cannot?
Feedzai covers Real-time scoring, Rule and model hybrid, Case manager, Behavioural biometrics. Restate covers Durable execution, Virtual objects, Single binary runtime, Multi-language SDKs.

Answered from the vendors’ own pages

Feedzai: Can Feedzai run on-premises?

Yes. On-premises and private cloud deployments are supported, which is why it appears in markets where transaction data cannot legally leave the country.

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.

Feedzai: Does it cover AML as well as fraud?

It does, but transaction monitoring is a separately licensed module. Assume two line items if you want both.

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.

Feedzai: How fast are decisions?

Designed for the authorisation window, typically tens of milliseconds. This is the constraint that rules out batch scoring architectures.

Restate: Is there a free tier?

Yes, fifty thousand durable actions a month on Restate Cloud with no card required.

Restate: Which languages are supported?

TypeScript, Java, Kotlin, Go, Python and Rust.

Share

Related pages

Other head to heads