Softwr

Cybersecurity · head to head

Feedzai vs Ory Kratos

Feedzai logo

Feedzai

Cybersecurity

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

From
On request
Rated
-
Full reviewWebsite
Ory Kratos logo

Ory Kratos

Cybersecurity

Headless identity and user management API

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Ory Kratos 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.; Ory Kratos headless means you build every screen, which is significant work compared with a hosted login page
  • They diverge on capability: Feedzai covers Real-time scoring, Ory Kratos covers Headless API.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Feedzai and Ory Kratos actually diverge.

Attributes where Feedzai and Ory Kratos differ
AttributeFeedzaiOry Kratos
Starting priceOn requestFree
Pricing modelquoteOpen-source self-hosted, with a paid managed network
Free tierNoYes
PlatformsWeb, LinuxLinux, Docker, Kubernetes, Self-hosted

Identical on both: user rating (Not yet rated), category (Cybersecurity).

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 Ory Kratos

  • Headless API
  • Self-service flows
  • Multi-factor authentication
  • Pluggable identity schemas

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 Ory Kratos
  • A card issuer whose existing rules engine cannot be changed without a release, so fraud waves run for daysnot Ory Kratos
  • An acquirer needing per-merchant risk models rather than one portfolio-wide modelnot Ory Kratos
  • A bank required by its regulator to explain automated declines to customers, which rules out opaque scoringnot Ory Kratos

Ory Kratos

  • Products needing complete control over the look and flow of authenticationnot Feedzai
  • Applications that must not hand user identity data to a third partynot Feedzai
  • Teams building identity as infrastructure across several servicesnot 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.

Ory Kratos

  • Headless means you build every screen, which is significant work compared with a hosted login page
  • More moving parts than a monolithic IAM: Kratos handles identity, and OAuth2 needs Ory Hydra alongside
  • Documentation assumes real familiarity with identity concepts and is not a gentle introduction
  • Self-hosting identity carries the security and availability burden that hosted providers absorb

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

Ory Kratos

Free
  • Self-hostedFree
    • Full identity server
    • All flows
    • Community support

Which should you pick?

Choose Feedzai if

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

Choose Ory Kratos if

  • You need headless api.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Self-hosted.
  • You also want self-service flows.
Ory Kratos review

Questions people ask

Is Feedzai or Ory Kratos better?
Neither clearly leads. Feedzai starts at On request and Ory Kratos at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Feedzai or Ory Kratos?
Ory Kratos has a free tier; the other does not. Paid plans start at On request for Feedzai and Free for Ory Kratos.
Does Feedzai or Ory Kratos run on more platforms?
Feedzai runs on Web, Linux. Ory Kratos runs on Linux, Docker, Kubernetes, Self-hosted.
Can I use Ory Kratos for free?
Yes. Ory Kratos 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 Ory Kratos is typically brought in for.
What can Feedzai do that Ory Kratos cannot?
Feedzai covers Real-time scoring, Rule and model hybrid, Case manager, Behavioural biometrics. Ory Kratos covers Headless API, Self-service flows, Multi-factor authentication, Pluggable identity schemas.

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.

Ory Kratos: Is Ory Kratos free?

Yes, open source and free to self-host. Ory Network is a paid managed 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.

Ory Kratos: What does headless mean here?

Kratos provides identity flows as APIs and no user interface. You build the login, registration and recovery screens yourself.

Feedzai: How fast are decisions?

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

Ory Kratos: Does Kratos do OAuth2?

No. Kratos handles user identity; OAuth2 and OpenID Connect provider functionality is Ory Hydra, a separate component.

Share

Related pages

More on Feedzai

More on Ory Kratos

Keep looking

Other head to heads