Updated Reviewed by Charlton Swearingen, CBO
The main difference between LimaCharlie and Wazuh is who runs the platform. Wazuh is free, open-source software you deploy and operate, or a hosted cloud service. LimaCharlie is a commercial SaaS platform that gives every customer an isolated tenant, a year of searchable data, and live response on the endpoint, with nothing to host.
LimaCharlie is a separate commercial product with its own sensor, rule engine, and data platform.
The quick verdict
At a glance
The main differences between the platforms, side by side.
| Capability | LimaCharlie | Wazuh |
|---|---|---|
| License | Commercial SaaS, with a free tier for labs and testing | Free and open source. Wazuh Cloud is a paid hosted option [1] [3] |
| Hosting | SaaS in six regions, nothing to operate | Self-hosted indexer, server, and dashboard, or Wazuh Cloud on AWS [1] [3] |
| Multi-tenancy | Every customer is an isolated tenant in the region you pick | Dashboard tenants are spaces for saved objects such as index patterns and dashboards [2] |
| Searchable retention | 1 year of every event, included | Wazuh Cloud keeps data indexed until a retention or capacity limit, then rotates the oldest out. Archive data isn’t searchable [3] |
| Detection rules | Rules on any field of any event, process trees, sequences, threat intel, and an AI question inside the rule | XML rules and decoders [4] |
| Rule testing | Unit tests on save, plus replay against a year of history | wazuh-logtest for decoders and rules [4] |
| Response | 65 sensor commands, including isolation, process-tree kill, memory forensics, YARA, and packet capture | Active Response scripts, such as blocking an IP or disabling a user account [5] |
| Agent platforms | Windows, macOS, Linux, containers, plus Chrome and Edge | Linux, Windows, macOS, and AIX [1] |
| Pricing | Usage-based. See current pricing → | Free software. Wazuh Cloud is priced by environment settings such as agents, retention, and support [3] |
Running it as an MSSP
Wazuh dashboard tenants are spaces for saved objects such as index patterns, visualizations, and dashboards. MSSPs on the Wazuh mailing list ask how to keep each client’s data separate, and third-party guides describe multi-tenancy as something you build yourself. LimaCharlie gives every customer an isolated tenant by default.
| Capability | LimaCharlie | Wazuh |
|---|---|---|
| Tenant isolation | Isolated by default, in the region you choose | Built and maintained by the operator [2] [6] |
| Rolling out changes | One Git template pushes rules, outputs, playbooks, and AI agents to every tenant | Centralized agent configuration and agent groups [1] |
| IR retainers | Sleeper-mode sensors at a reduced dormant rate, woken when an incident starts | No dormant mode found |
Data and retention
LimaCharlie keeps every event searchable for a year. In Wazuh Cloud, data stays indexed until it reaches either the retention or the capacity setting, and then the oldest data rotates out. Archive data is stored in S3 as compressed files that aren’t searchable, and if ingestion passes peak EPS and the queue fills, new events are discarded.
Detection and response
Wazuh responds through Active Response, which runs scripts on the agent, such as blocking an IP or disabling a user account. LimaCharlie gives analysts 65 sensor commands, including isolation that survives reboot, process-tree kill, memory string search, YARA on live process memory, and packet capture, and any of them can run from the rule that fired.
| Capability | LimaCharlie | Wazuh |
|---|---|---|
| Response from a rule | Any sensor command, within milliseconds | Active Response scripts, default or custom [5] |
| Forensics | Memory dumps and string search, MFT dumps, file collection, and Velociraptor at fleet scale | File integrity monitoring and YARA integration [1] |
| Detection content | Thousands of community Sigma, Anvilogic, Panther, and Okta rules, converted by AI in one click | Default ruleset with MITRE ATT&CK mapping [1] |
API and AI access
Both platforms publish APIs. Wazuh has a server API and an indexer API. LimaCharlie makes every console action an API call and adds AI inside the platform: an AI question inside any detection rule, and AI agents started by detections, on the model you choose with a budget cap per agent.
| Capability | LimaCharlie | Wazuh |
|---|---|---|
| API coverage | Every console action is an API call: REST API, LimaCharlie CLI, Python and Go SDKs, and an MCP server | Wazuh server API and Wazuh indexer API [1] |
| Detection as code | Every rule syncs from Git to every tenant, with dry-run | Rules and decoders as XML files on the server [4] |
Pricing model
Wazuh software is free, and you pay for the infrastructure and people to run it, or for Wazuh Cloud, which is priced by settings such as active agents, indexed retention, archive length, and support plan. LimaCharlie is usage-based. Buy on an annual agreement or month to month, add products whenever you need them, and pay only for what you use.
| What’s included | LimaCharlie | Wazuh |
|---|---|---|
| Software | Usage-based. See current pricing | Free and open source [1] |
| Infrastructure to run | None | Self-hosted, or Wazuh Cloud [3] |
| A year of searchable data | Included | Set by indexed retention and capacity [3] |
| Buying model | Annual agreement or month to month | Wazuh Cloud is purchased in the cloud console [3] |
Why MSSPs switch
01
No indexer, server, or dashboard to deploy, patch, or scale for every customer.
02
Isolation is the default, and your team works across every customer from one console, one Git repo, and one invoice.
03
Memory string search, YARA on live process memory, packet capture, and fleet-wide Velociraptor, started by an analyst, an API call, a rule, or an AI agent.
04
Every event stays searchable for a year, and any of it can stream to the customer’s own bucket or SIEM.
It’s a very low barrier to entry. I’d say you can go in and experiment with it, and if you don’t like it, that’s fine. And you’re not stuck with it for a year... you don’t have to commit to a thousand endpoints for a year to just give it a shot.

Co-founder, Soteria
LimaCharlie was really designed with service providers in mind. It was multi-tenant. More important for me, it was designed to be built upon and extended and expanded.

CTO, Recon InfoSec
We’re very much in our SOC, like an MSSP, in the fact that we have multiple customers with multiple different levels. Also, when we’re looking at licensing, getting down to brass tacks, the model for a lot of vendors is not flexible to work with us as we scale up.

CEO, Black Hills Information Security
FAQ
Compare more tools
Book a demo with our team, or open a free tenant and connect a test endpoint today.
Wazuh details come from the public sources below, read November 13, 2026. Product names belong to their owners.