Softwr

Cybersecurity · head to head

Falco vs Incode

Falco logo

Falco

Cybersecurity

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

From
Free
Free plan
Yes
Full reviewWebsite
Incode logo

Incode

Government

Financial & HR Software for Government

From
$700/month
Free plan
No
Full reviewWebsite

The short version

  • Only Falco has a free tier, so it costs nothing to try first.
  • 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.; Incode incode is now sold as Tyler ERP Pro and tylertech.com/products/incode redirects to the ERP Pro product page
  • They diverge on capability: Falco covers eBPF kernel instrumentation, Incode covers General Ledger.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Falco and Incode actually diverge.

Attributes where Falco and Incode differ
AttributeFalcoIncode
Starting priceFree$700/month
Pricing modelOpen source, no licence feesubscription
Free tierYesNo
PlatformsLinux, Kubernetes, Self-hostedWeb, Desktop
CategoryCybersecurityGovernment
FoundedUnknown1966

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 Falco

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

Only in Incode

  • General Ledger
  • Accounts Payable
  • Payroll Management
  • Utility Billing
  • Budget Management
  • Bank Integrations
  • ADP
  • Third-party Payroll

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

Incode

  • Financial management and ERP for small and mid-sized local governmentsnot Falco
  • Utility billing, payroll and human resources for city and county administrationnot Falco
  • Court and public safety records for municipalitiesnot 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.

Incode

  • Incode is now sold as Tyler ERP Pro and tylertech.com/products/incode redirects to the ERP Pro product page
  • No pricing is published; Tyler routes all enquiries through contact and demo requests with no published rate, minimum or cost driver
  • The product is sold only to public sector organisations

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

Incode

$700/month
  • Municipal Suite$700/month
    • Financial Management
    • HR/Payroll
    • Utility Billing

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.
Falco review

Choose Incode if

  • You need general ledger.
  • You work on Web, Desktop.
  • You also want accounts payable.
Incode review

Questions people ask

Is Falco or Incode better?
Neither clearly leads. Falco starts at Free and Incode at $700/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Falco or Incode?
Falco has a free tier; the other does not. Paid plans start at Free for Falco and $700/month for Incode.
Does Falco or Incode run on more platforms?
Falco runs on Linux, Kubernetes, Self-hosted. Incode runs on Web, Desktop.
Can I use Falco for free?
Yes. Falco has a free tier, so you can try it without paying. Incode starts at $700/month.
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 Incode is typically brought in for.
What can Falco do that Incode cannot?
Falco covers eBPF kernel instrumentation, System call rules engine, Container and Kubernetes context, Default rule set. Incode covers General Ledger, Accounts Payable, Payroll Management, Utility Billing.

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.

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.

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.

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

More on Falco

More on Incode

Keep looking

Other head to heads