Softwr

Government · head to head

Clariti vs Falco

Clariti logo

Clariti

Government

Permitting, licensing and land management for local government, built natively on Salesforce

From
On request
Free plan
No
Full reviewWebsite
Falco logo

Falco

Cybersecurity

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

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Only Falco has a free tier, so it costs nothing to try first.
  • Each has a real cost: Clariti salesforce platform licences sit underneath the subscription and are not always visible in the initial quote, so the fully loaded cost can be materially higher than the comparison against Accela or Tyler suggests.; 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.
  • They diverge on capability: Clariti covers Permitting workflows, Falco covers eBPF kernel instrumentation.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Clariti and Falco actually diverge.

Attributes where Clariti and Falco differ
AttributeClaritiFalco
Starting priceOn requestFree
Pricing modelquoteOpen source, no licence fee
Free tierNoYes
PlatformsWeb, iOS, AndroidLinux, Kubernetes, Self-hosted
CategoryGovernmentCybersecurity

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 Clariti

  • Permitting workflows
  • Business licensing
  • Inspections
  • Code enforcement
  • Public portal
  • Salesforce platform tooling

Only in Falco

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

What people use each for

The jobs each tool is most often brought in to do.

Clariti

  • A city already standardised on Salesforce that wants permitting inside the same platformnot Falco
  • An agency replacing a legacy permitting system whose vendor was acquired and whose roadmap stallednot Falco
  • A county needing configurable workflows across permits, licensing and code enforcementnot Falco
  • An IT department that wants to configure and report on its own permitting workflows without vendor ticketsnot Falco

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

Where each one falls short

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

Clariti

  • Salesforce platform licences sit underneath the subscription and are not always visible in the initial quote, so the fully loaded cost can be materially higher than the comparison against Accela or Tyler suggests.
  • Building on Salesforce means the agency inherits Salesforce release cycles and pricing changes, neither of which Clariti controls.
  • It has far less accumulated edge case handling than the incumbents, so unusual fee schedules, historic district rules or state mandated reporting can become configuration projects.
  • Professional services dominate the first year cost, as with every permitting implementation, and agencies that budget only for licence are the ones whose projects stall.
  • The install base is smaller than Accela or Tyler, so there are fewer peer agencies to call for reference and fewer trained implementation consultants in the market.

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.

Pricing, plan by plan

Clariti

On request
  • Clariti$undefined/year
    • Quoted by agency size and module scope
    • Salesforce platform licences are a separate cost underneath the subscription
    • Implementation and configuration services typically exceed first year licence cost

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

Which should you pick?

Choose Clariti if

  • You need permitting workflows.
  • You work on Web, iOS, Android.
  • You also want business licensing.
Clariti review

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

Questions people ask

Is Clariti or Falco better?
Neither clearly leads. Clariti starts at On request and Falco at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Clariti or Falco?
Falco has a free tier; the other does not. Paid plans start at On request for Clariti and Free for Falco.
Does Clariti or Falco run on more platforms?
Clariti runs on Web, iOS, Android. Falco runs on Linux, Kubernetes, Self-hosted.
Can I use Falco for free?
Yes. Falco has a free tier, so you can try it without paying. Clariti starts at On request.
What is Clariti best used for?
Clariti is most often used for a city already standardised on salesforce that wants permitting inside the same platform, an agency replacing a legacy permitting system whose vendor was acquired and whose roadmap stalled, a county needing configurable workflows across permits, licensing and code enforcement, an it department that wants to configure and report on its own permitting workflows without vendor tickets. Of those, a city already standardised on salesforce that wants permitting inside the same platform and an agency replacing a legacy permitting system whose vendor was acquired and whose roadmap stalled are not what Falco is typically brought in for.
What can Clariti do that Falco cannot?
Clariti covers Permitting workflows, Business licensing, Inspections, Code enforcement. Falco covers eBPF kernel instrumentation, System call rules engine, Container and Kubernetes context, Default rule set.

Answered from the vendors’ own pages

Clariti: Do we need Salesforce licences as well?

Yes. Clariti runs on the Salesforce platform, and those licences are a separate line item. Insist on a fully loaded quote.

Falco: Does Falco block attacks?

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

Clariti: How does it compare with Accela?

Accela has far deeper accumulated handling of edge cases. Clariti offers a more modern and configurable platform, at the price of Salesforce underneath.

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.

Clariti: Can we see what other agencies paid?

Yes. Permitting contracts are public records and award notices routinely list implementation and annual subscription values.

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.

Clariti: Is it suitable for a small town?

Usually not. The platform cost and implementation effort suit mid sized and larger agencies.

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 Clariti

More on Falco

Keep looking

Other head to heads