Softwr

Cybersecurity · head to head

Falco vs Passbolt

Falco logo

Falco

Cybersecurity

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

From
Free
Rated
-
Passbolt logo

Passbolt

Cybersecurity

Open-source password manager for teams with self-hosted or cloud deployment

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.; Passbolt pro Edition requires a minimum of 10 users, making it costlier for very small teams.
  • They diverge on capability: Falco covers eBPF kernel instrumentation, Passbolt covers Password sharing and folders.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Falco and Passbolt actually diverge.

Attributes where Falco and Passbolt differ
AttributeFalcoPassbolt
Pricing modelOpen source, no licence feeopen-source
PlatformsLinux, Kubernetes, Self-hostedweb, windows, mac, linux, api

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 Passbolt

  • Password sharing and folders
  • Groups and role-based access
  • Browser extensions and CLI
  • Open API
  • LDAP provisioning and SSO
  • Activity audit log

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 Passbolt
  • A regulated business required to evidence host and container intrusion detection on Kubernetes nodes for an auditnot Passbolt
  • A security team wanting a vendor-neutral detection layer whose rules they can read and modify rather than a black-box agentnot Passbolt
  • A cluster where a compromised dependency might write to sensitive paths or open unexpected outbound connections, and only kernel-level visibility will catch itnot Passbolt

Passbolt

  • Self-hosting a team password manager for data sovereigntynot Falco
  • Provisioning vault access from an existing LDAP/AD directorynot Falco
  • Sharing credentials across engineering or IT teams via folders and groupsnot Falco
  • Automating credential retrieval through the CLI or open APInot 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.

Passbolt

  • Pro Edition requires a minimum of 10 users, making it costlier for very small teams.
  • Community Edition lacks SSO and LDAP provisioning, which many organizations need for onboarding at scale.
  • Self-hosting the Community Edition requires infrastructure and maintenance effort compared to fully managed competitors.
  • Enterprise-tier support and HA consulting require custom, quote-based pricing rather than transparent rates.

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

Passbolt

Free
  • Community EditionFree
    • Unlimited users
    • Password sharing and folders
    • Role-based access control
  • Pro Edition$4.9/month
    • Minimum 10 users, billed annually
    • LDAP/AD provisioning
    • Single sign-on
  • Enterprise Edition$undefined/month
    • High availability and disaster recovery consulting
    • White-glove migration
    • Custom feature development

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

  • You need password sharing and folders.
  • You want to start without paying.
  • You work on web, windows, mac, linux, api.
  • You also want groups and role-based access.

Questions people ask

Is Falco or Passbolt better?
Neither clearly leads. Falco starts at Free and Passbolt at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Falco or Passbolt?
Falco starts at Free and Passbolt at Free.
Does Falco or Passbolt run on more platforms?
Falco runs on Linux, Kubernetes, Self-hosted. Passbolt runs on web, windows, mac, linux, api.
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 Passbolt is typically brought in for.
What can Falco do that Passbolt cannot?
Falco covers eBPF kernel instrumentation, System call rules engine, Container and Kubernetes context, Default rule set. Passbolt covers Password sharing and folders, Groups and role-based access, Browser extensions and CLI, Open API.

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.

Passbolt: Is Passbolt free to use?

Yes. The Community Edition is free forever with unlimited users, including password sharing, folders, groups, role-based access, browser extensions, a CLI, and an open API.

Source
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.

Passbolt: What does the Pro Edition cost and add?

Pro Edition costs $4.90 per user per month billed annually, with a 10-user minimum, and adds LDAP/AD provisioning, single sign-on, account recovery escrow, activity audit logs, and next-business-day support.

Source
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.

Passbolt: What license is Passbolt distributed under?

All Passbolt editions, including Pro and Enterprise, are distributed under the AGPL v3 open-source license.

Source
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