Updated Reviewed by Charlton Swearingen, CBO
The main difference between LimaCharlie and Elastic Security is packaging. LimaCharlie gives every customer an isolated tenant with the same features, a year of hot, indexed data, and rules that run on each event. Elastic keeps the EDR response console, AI, automation, and long searchable retention in its top tiers, and detection rules run on a schedule.
There’s no cluster to size, and cloud security and email security live in the same tenant.
The quick verdict
At a glance
The main differences between the platforms, side by side.
| Capability | LimaCharlie | Elastic Security |
|---|---|---|
| Log pricing | Usage-based, with a year of retention included. See current pricing → | Serverless ingest from $0.09 to $0.11 per GB at volume, plus retention. Elastic’s own example starts Complete at $0.60 per GB for the first 50 GB [1] |
| A year of searchable data | Included, hot and fully indexed | Serverless keeps a 7-day search-ready window by default. On Hosted and self-managed, searchable cold and frozen tiers need Enterprise [2] |
| What you size and run | Nothing | Hosted and self-managed: nodes, tiers, shards, lifecycle policies, and upgrades [2] |
| How rules run | On every event as it arrives, typically under 100 ms | Scheduled, with a look-back window. On Serverless, most rules stop after 1 minute per run [4] |
| Response from a rule | Any endpoint command, run from the rule that fired, within milliseconds | Alert actions and Workflows. External actions need Gold, Workflows need Enterprise or Complete [5] |
| Endpoint response console | Every tier | Enterprise (Hosted) or Complete (Serverless) [5] |
| Windows and Linux coverage | Windows 7 and Server 2008 R2 onward. Linux back to RHEL/CentOS 6, including 32-bit | Windows 10, 11, and Server 2012 R2 onward. RHEL 7 and later, no 32-bit [7] |
| Multi-tenancy | Every customer is an isolated tenant in the region you pick | Kibana Spaces aren’t a security feature on their own. The clean option is one deployment per customer [8] |
| Email and cloud security | Both in the same tenant | Cloud posture is a per-asset add-on. No Elastic email security product found [1] [10] |
| AI | ask ai in any rule and AI agents started by detections, on the model you choose | AI Assistant and Attack Discovery need Enterprise or Complete [11] |
Data and retention
LimaCharlie keeps a full year of data hot and fully indexed, at any volume. On Elastic Serverless only a boost window, 7 days by default, is search-ready, and older searches are slower and share capacity with detection rules. On Hosted and self-managed, searchable cold and frozen tiers need Enterprise.
| Capability | LimaCharlie | Elastic Security |
|---|---|---|
| Extra meters | Outputs beyond same-region Google Cloud | Support uplift of 5 to 15% on the whole bill for Gold, Platinum, or Enterprise. Cloud posture per asset. Workflows, Agent Builder, and cross-project search per use [1] |
| Raw data out | Stream every event live to S3, GCS, BigQuery, Pub/Sub, Splunk, Elastic, Kafka, syslog, or a webhook. Same-region GCS is free | 50 GB of egress free per month on Serverless, then $0.05 per GB [1] |
| Search capacity | Nothing to scale | On Serverless, search capacity doesn’t scale up when query load increases [3] |
Detection engineering
LimaCharlie evaluates each rule on every event as it lands. Elastic rules run every few minutes with a look-back window, and on Serverless most rules stop after 1 minute per run. Elastic’s docs note that a run that stops early can miss alerts.
| Capability | LimaCharlie | Elastic Security |
|---|---|---|
| Rule logic | Process trees, sequences, threat-intel lookups, GeoIP, first-seen, and thresholds, plus an AI question inside the rule | Custom query, EQL, ES|QL, threshold, indicator match, new terms, and machine learning [4] |
| Testing | Unit tests on save, plus replay against a year of history | Rule preview [4] |
| Content | Every rule is editable, plus thousands of community rules converted by AI in one click | A large open rule repo. Editing a prebuilt rule needs Enterprise on Hosted and self-managed [5] |
| Detection as code | Every rule syncs from Git to every tenant, with dry-run | The open detection-rules repo and CLI, pushed through the Kibana API per deployment |
Endpoint
LimaCharlie includes full EDR on every endpoint, with every feature on every tier. Elastic includes malware prevention in every tier, puts ransomware, behavior, and memory protection and host isolation in Platinum, and puts the response console in Enterprise or Complete.
| Capability | LimaCharlie | Elastic Security |
|---|---|---|
| Live response | 65 sensor commands, memory string search, YARA on live process memory, packet capture, full memory and MFT dumps, and Velociraptor | Isolate, kill or suspend a process, get a file (100 MB cap outside Serverless), run a command, upload, scan, and memory dump [6] |
| Prevention | Microsoft Defender Antivirus, managed from LimaCharlie, plus application allowlisting on Windows and macOS | Elastic Defend’s own prevention engines |
| Windows | 7 through 11 and Server 2008 R2 through 2022 | Windows 10 and 11, Server 2012 R2 and later. Windows 8.1 marked unsupported [7] |
| Linux | x86_64, i386, ARM64, and Alpine, back to RHEL/CentOS 6 | RHEL 7 and later. CentOS 7 dropped from 8.18. No 32-bit [7] |
Running it as an MSSP
LimaCharlie isolates every customer in its own tenant by default, with one login and one rule push across all of them. In Elastic, Kibana Spaces aren’t a security feature on their own, so the clean option is one deployment or project per customer, and cross-project search on Serverless needs Complete on every project.
| Capability | LimaCharlie | Elastic Security |
|---|---|---|
| Working across customers | One login across every tenant | Serverless cross-project search, GA since September 2026. Links up to 100 projects by default, billed separately, and the Alerts page doesn’t show alerts from linked projects [9] |
| Rolling out changes | One Git template for rules, outputs, playbooks, and AI agents | Scripted per deployment or project |
| IR retainers | Sleeper-mode sensors at a reduced dormant rate, woken when an incident starts | No dormant mode found |
API and AI access
Both platforms publish APIs, and both offer an MCP server for outside AI assistants. Elastic’s Agent Builder MCP server is generally available on Serverless and in the Elastic Stack since 9.3. The difference is packaging. AI Assistant and Attack Discovery need Enterprise or Complete, while LimaCharlie’s AI agents run on every tier, on the model you choose with a budget cap per agent.
| Capability | LimaCharlie | Elastic Security |
|---|---|---|
| API coverage | Every console action is an API call: REST API, LimaCharlie CLI, Python and Go SDKs, and an MCP server | Elasticsearch and Kibana APIs, plus the Agent Builder MCP server [12] |
| AI in detection and response | ask ai inside any rule, plus AI agents started by detections, on every tier | AI Assistant and Attack Discovery need Enterprise or Complete [11] |
Pricing model
LimaCharlie is usage-based, with every feature on every tier and a year of retention included. Buy on an annual agreement or month to month, and add products whenever you need them. Elastic Serverless Complete starts at $0.60 per GB of ingest for the first 50 GB, with retention, support, and several features metered separately.
| What’s included | LimaCharlie | Elastic Security |
|---|---|---|
| Every feature on every tier | Yes | Response console, AI, and Workflows need Enterprise or Complete [5] |
| A year of searchable data | Included | Retention billed per GB per month. Searchable cold tiers need Enterprise [1] [2] |
| AI model costs | The model you choose, with a budget cap per agent | Managed LLM at $4.50 / $21 per million tokens, or your own connector [11] |
Why MSSPs switch
01
No tier decides whether your analysts can isolate a host, use AI, or search last quarter.
02
Isolation is the default, and your team works across every customer from one console, one Git repo, and one invoice.
03
Rules evaluate each event as it lands, and the response runs on the endpoint in the same moment.
04
Cloud security and email security live in the same tenant as the SIEM and EDR, so one detection can follow a phish to the laptop to the cloud account.
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.
Elastic details come from the public sources below, with the date of each source. Product names belong to their owners.