Softwr

Cybersecurity · head to head

Feedzai vs Soketi

Feedzai logo

Feedzai

Cybersecurity

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

From
On request
Free plan
No
Full reviewWebsite
Soketi logo

Soketi

Developer Tools

Self-hosted, Pusher-compatible WebSockets server with a stalled maintenance record

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Only Soketi 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.; Soketi maintenance has effectively stalled: the maintainer has said time is severely limited, releases are infrequent, and the community has been discussing whether the project is abandoned, which means security fixes may not arrive.
  • They diverge on capability: Feedzai covers Real-time scoring, Soketi covers Pusher protocol compatibility.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Feedzai and Soketi actually diverge.

Attributes where Feedzai and Soketi differ
AttributeFeedzaiSoketi
Starting priceOn requestFree
Pricing modelquoteOpen source, no licence fee
Free tierNoYes
PlatformsWeb, LinuxLinux, macOS, Windows
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 Soketi

  • Pusher protocol compatibility
  • Presence and private channels
  • Horizontal scaling
  • App management backends
  • Webhooks
  • Prometheus metrics

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

Soketi

  • A Laravel application that already uses Echo and wants to stop paying a hosted realtime providernot Feedzai
  • Realtime notifications or presence indicators where data must not leave your own infrastructure for compliance reasonsnot Feedzai
  • A local or CI environment that needs a Pusher-compatible server without hitting a paid accountnot Feedzai
  • A high-connection-count application where hosted per-connection pricing has become the largest line in the infrastructure billnot 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.

Soketi

  • Maintenance has effectively stalled: the maintainer has said time is severely limited, releases are infrequent, and the community has been discussing whether the project is abandoned, which means security fixes may not arrive.
  • Dependency drift on Node and uWebSockets.js will eventually force you to fork or migrate, and that cost is unbudgeted at the point you adopt it.
  • There is no commercial support to buy, so a production incident at three in the morning is entirely your problem with no escalation path.
  • Scaling beyond a single node needs Redis and careful configuration, and getting presence channels correct across nodes is a genuine source of subtle bugs.
  • It implements the Pusher protocol rather than tracking it, so any protocol feature Pusher adds later will not appear, and the compatibility guarantee slowly decays.

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

Soketi

Free
  • SoketiFree
    • MIT licensed
    • Unlimited connections subject to your own hardware
    • No vendor billing

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 Soketi if

  • You need pusher protocol compatibility.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want presence and private channels.
Soketi review

Questions people ask

Is Feedzai or Soketi better?
Neither clearly leads. Feedzai starts at On request and Soketi at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Feedzai or Soketi?
Soketi has a free tier; the other does not. Paid plans start at On request for Feedzai and Free for Soketi.
Does Feedzai or Soketi run on more platforms?
Feedzai runs on Web, Linux. Soketi runs on Linux, macOS, Windows.
Can I use Soketi for free?
Yes. Soketi 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 Soketi is typically brought in for.
What can Feedzai do that Soketi cannot?
Feedzai covers Real-time scoring, Rule and model hybrid, Case manager, Behavioural biometrics. Soketi covers Pusher protocol compatibility, Presence and private channels, Horizontal scaling, App management backends.

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.

Soketi: Is Soketi still maintained?

Barely. The maintainer has stated that available time is very limited and releases have been sparse; treat it as community-maintained.

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.

Soketi: Do I need to change my client code?

No. Pusher client SDKs and Laravel Echo work by changing the host, port and credentials.

Feedzai: How fast are decisions?

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

Soketi: What does it cost?

Nothing in licence fees. It is MIT licensed; you pay for the server it runs on.

Soketi: What are people moving to?

Laravel Reverb for Laravel applications, and Sockudo, a Rust reimplementation, for others.

Share

Related pages

More on Feedzai

More on Soketi

Keep looking

Other head to heads