Softwr

Cybersecurity · head to head

Falco vs Ory Kratos

Falco logo

Falco

Cybersecurity

CNCF-graduated runtime threat detection for Linux and Kubernetes using eBPF

From
Free
Rated
-
Ory Kratos logo

Ory Kratos

Cybersecurity

Headless identity and user management API

From
Free
Rated
-

The short version

  • Each has a real cost: Falco falco detects and alerts but does not block; stopping an attack requires wiring up Falco Talon or your own response tooling, so out of the box a confirmed detection still means a human intervening after the fact.; Ory Kratos headless means you build every screen, which is significant work compared with a hosted login page
  • They diverge on capability: Falco covers eBPF kernel instrumentation, Ory Kratos covers Headless API.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

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

Attributes where Falco and Ory Kratos differ
AttributeFalcoOry Kratos
Pricing modelOpen source, no licence feeOpen-source self-hosted, with a paid managed network
PlatformsLinux, Kubernetes, Self-hostedLinux, Docker, Kubernetes, Self-hosted

Identical on both: starting price (Free), free tier (Yes), 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 Falco

  • eBPF kernel instrumentation
  • System call rules engine
  • Container and Kubernetes context
  • Default rule set
  • Falcosidekick
  • Falco Talon
  • Plugins framework
  • DaemonSet deployment

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.

Falco

  • A platform team that needs to know when a shell is opened inside a production container, which image scanning cannot detect because it happens at runtimenot Ory Kratos
  • A regulated business required to evidence host and container intrusion detection on Kubernetes nodes for an auditnot Ory Kratos
  • A security team wanting a vendor-neutral detection layer whose rules they can read and modify rather than a black-box agentnot Ory Kratos
  • A cluster where a compromised dependency might write to sensitive paths or open unexpected outbound connections, and only kernel-level visibility will catch itnot Ory Kratos

Ory Kratos

  • Products needing complete control over the look and flow of authenticationnot Falco
  • Applications that must not hand user identity data to a third partynot Falco
  • Teams building identity as infrastructure across several servicesnot Falco

Where each one falls short

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

Falco

  • Falco detects and alerts but does not block; stopping an attack requires wiring up Falco Talon or your own response tooling, so out of the box a confirmed detection still means a human intervening after the fact.
  • The default rule set is noisy in real clusters and generates a large volume of benign matches from normal operational activity; without weeks of tuning, alert fatigue sets in and the team stops reading the feed, which is the usual failure mode.
  • There is no storage, console, search or case management in the project, so a working detection capability means also running Falcosidekick, an event store, a dashboard and alert routing, all of which you build, host and maintain.
  • The modern eBPF driver requires kernel 5.8 or later; older hosts fall back to the legacy probe or the kernel module, which brings driver-building against kernel headers and the operational fragility that comes with it on every kernel upgrade.
  • Per-node syscall instrumentation carries measurable CPU overhead on busy hosts, and the cost scales with syscall volume rather than with cluster size, so the noisiest and most performance-sensitive workloads are exactly the ones that feel it most.

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

Falco

Free
  • Falco (open source)Free
    • Apache 2.0 licence, CNCF graduated project
    • eBPF and kernel module drivers
    • Full rules engine and default rule set

Ory Kratos

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

Which should you pick?

Choose Falco if

  • You need ebpf kernel instrumentation.
  • You want to start without paying.
  • You work on Linux, Kubernetes, Self-hosted.
  • You also want system call rules engine.

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.

Questions people ask

Is Falco or Ory Kratos better?
Neither clearly leads. Falco starts at Free and Ory Kratos at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Falco or Ory Kratos?
Falco starts at Free and Ory Kratos at Free.
Does Falco or Ory Kratos run on more platforms?
Falco runs on Linux, Kubernetes, Self-hosted. Ory Kratos runs on Linux, Docker, Kubernetes, Self-hosted.
Can I use Falco for free?
Both have a free tier, so you can try either at no cost before committing.
What is Falco best used for?
Falco is most often used for a platform team that needs to know when a shell is opened inside a production container, which image scanning cannot detect because it happens at runtime, a regulated business required to evidence host and container intrusion detection on kubernetes nodes for an audit, a security team wanting a vendor-neutral detection layer whose rules they can read and modify rather than a black-box agent, a cluster where a compromised dependency might write to sensitive paths or open unexpected outbound connections, and only kernel-level visibility will catch it. Of those, a platform team that needs to know when a shell is opened inside a production container, which image scanning cannot detect because it happens at runtime and a regulated business required to evidence host and container intrusion detection on kubernetes nodes for an audit are not what Ory Kratos is typically brought in for.
What can Falco do that Ory Kratos cannot?
Falco covers eBPF kernel instrumentation, System call rules engine, Container and Kubernetes context, Default rule set. Ory Kratos covers Headless API, Self-service flows, Multi-factor authentication, Pluggable identity schemas.

Answered from the vendors’ own pages

Falco: Does Falco block attacks?

No. It detects and emits events. Response requires Falco Talon or your own automation on top.

Ory Kratos: Is Ory Kratos free?

Yes, open source and free to self-host. Ory Network is a paid managed service.

Falco: Is Falco owned by Sysdig?

Sysdig created and open sourced it, but it graduated within the CNCF in February 2024, so governance sits with the foundation rather than the vendor.

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.

Falco: What does it cost?

The project is Apache 2.0 with no licence fee. The cost is the storage, routing, tuning and staff time needed to make its output useful.

Ory Kratos: Does Kratos do OAuth2?

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

Falco: What kernel version do I need?

Kernel 5.8 or later for the default modern eBPF driver. Older hosts need the legacy eBPF probe or the kernel module.

Share

Related pages

Other head to heads