Updated Reviewed by Charlton Swearingen, CBO
The main difference between LimaCharlie and Splunk is how detection runs across many customers. LimaCharlie evaluates rules on every event as it arrives, keeps a year of data hot and indexed, and gives each customer an isolated tenant. Splunk runs detections as scheduled searches and recommends a separate deployment per customer for MSPs.
LimaCharlie also includes its own EDR, cloud security, and email security in the same tenant as the SIEM.
The quick verdict
At a glance
The main differences between the platforms, side by side.
| Capability | LimaCharlie | Splunk Enterprise Security |
|---|---|---|
| Pricing | Usage-based and published. See current pricing → | Quote only, metered by ingest, compute, or ingest plus search [1] |
| Retention | 1 year of search, hot and fully indexed, included | Searchable storage sized into the subscription. Archived data must be restored before search, and restored data expires after 30 days [2] |
| What you size and run | Nothing. No indexers, search heads, or compute units | Splunk Cloud is sized in SVCs, and Enterprise Security Premium adds 1 SVC per 10 GB of daily ingest [3] [4] |
| How rules run | On every event as it arrives, typically under 100 ms | Scheduled correlation searches, for example every 15 minutes [5] |
| Response from a rule | Any endpoint command, run from the rule that fired, within milliseconds | Splunk SOAR, in the Premier edition or sold separately [6] |
| Endpoint (EDR) | Included in the platform | Cisco Secure Endpoint, a separate product [8] |
| Email and cloud security | Both in the same tenant | Cisco Secure Email Threat Defense is separate. No CNAPP in either Enterprise Security edition [6] [8] |
| UEBA and AI | First-seen, cardinality, and volume rules on any data, plus AI agents on the model you choose | UEBA and AI agents in the Premier edition only [6] |
| Multi-tenancy | Every customer is an isolated tenant in the region you pick | Splunk’s 2026 MSP guide recommends a deployment per customer [10] |
| Buying model | Annual agreement or month to month, one invoice across all tenants | Annual subscriptions for Splunk Cloud, term licenses on-premises [1] |
Data and retention
LimaCharlie keeps every log and endpoint event hot and indexed for a year, with no archive to restore from. In Splunk Cloud, longer storage is an optional archive subscription, archived data has to be restored before it can be searched, and restored data expires after 30 days.
| Capability | LimaCharlie | Splunk Enterprise Security |
|---|---|---|
| Going over | Billed for what you use that month | Ingest subscriptions can exceed the daily volume up to five times a month [3] |
| 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 | Self-storage export (DDSS) to your own bucket [2] |
| Self-managed footprint | Nothing to run | Self-managed Enterprise Security needs its own search head cluster [4] |
Detection engineering
LimaCharlie evaluates each rule on every event as it lands and can run the response on the endpoint in the same moment. Splunk Enterprise Security runs detections as scheduled correlation searches, with risk-based alerting that scores users and systems.
| Capability | LimaCharlie | Splunk Enterprise Security |
|---|---|---|
| Rule logic | Process trees, sequences, threat-intel lookups, GeoIP, first-seen, and thresholds, plus an AI question inside the rule | SPL searches with risk-based alerting [5] |
| Testing | Unit tests on save, plus replay against a year of history | Test detections against production data into test indexes, from Enterprise Security 8.4 [5] |
| Content | Thousands of community Sigma, Anvilogic, Panther, and Okta rules, converted by AI in one click | Splunk Security Content: 2,204 detections as of November 2026 [7] |
| Detection as code | Every rule, output, and response syncs from Git to every tenant, with dry-run | Detection versioning in the console and the open-source contentctl tool [5] |
Beyond the SIEM
LimaCharlie includes full EDR, managed Microsoft Defender prevention, cloud security, and email security in the same tenant as the SIEM. With Splunk, endpoint and email security are separate Cisco products, and cloud security isn’t in either Enterprise Security edition.
| Capability | LimaCharlie | Splunk Enterprise Security |
|---|---|---|
| Endpoint | 65 live-response commands, YARA on live process memory, packet capture, and a year of telemetry | Cisco Secure Endpoint, connected through a Splunkbase app [8] |
| Prevention | Microsoft Defender Antivirus, managed from LimaCharlie, with 11 ready-made tamper alerts | Through the separate endpoint product |
| UEBA | Built into the rule engine | UEBA in Premier only. Legacy UBA reaches end of life on January 31, 2027 [6] [9] |
Running it as an MSSP
LimaCharlie gives every customer an isolated tenant on one platform, with one login, one Git repo, and one invoice. Splunk’s 2026 MSP guide recommends a separate deployment per customer and does not recommend one shared deployment split by roles and indexes as a general MSP pattern. That guide covers self-managed Splunk Enterprise, not Enterprise Security or Splunk Cloud.
| Capability | LimaCharlie | Splunk Enterprise Security |
|---|---|---|
| Working across customers | Org groups give staff access to every tenant with one login | A federated search hub across customer deployments [10] |
| Onboarding a customer | Create the tenant from a Git template in one step | A namespace, deployment, federated search, and app catalog for each customer [10] |
| Licensing per customer | One price list, one invoice, usage broken out per tenant | A license per customer, or a pooled MSP license with a community chargeback app [10] |
| 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. Splunk Enterprise Security has an OpenAPI reference for findings, investigations, risk scores, assets, and identities, and Splunk documents an MCP server for the Splunk platform. The difference is where AI runs. LimaCharlie can call an AI model inside any detection rule and start AI agents from detections on the model you choose, while Splunk’s AI agents are in the Premier edition.
| Capability | LimaCharlie | Splunk Enterprise Security |
|---|---|---|
| API coverage | Every console action is an API call: REST API, LimaCharlie CLI, Python and Go SDKs, and an MCP server | Enterprise Security API for findings, investigations, risk scores, assets, and identities, with an OpenAPI spec [12] |
| AI assistants | An MCP server for any AI client | MCP Server for Splunk Platform [12] |
| AI in detection and response | ask ai inside any rule, plus AI agents started by detections, with a budget cap per agent | AI agents in the Premier edition only [6] |
Pricing model
LimaCharlie publishes a unit price for every product. Buy on an annual agreement or month to month, add products whenever you need them, and pay only for what you use. Splunk publishes no SIEM price. The public figures we found are AWS Marketplace listings, including a reseller’s 10 GB per day Enterprise term license at $12,650 a year, before servers and Enterprise Security.
| What’s included | LimaCharlie | Splunk Enterprise Security |
|---|---|---|
| Published prices | Yes, for every product | Quote only [1] |
| A year of hot, searchable data | Included | Sized into the subscription, with archive restores [2] |
| SOAR, UEBA, and AI agents | Included in the platform | Premier edition [6] |
| Buying model | Annual agreement or month to month | Annual subscription or term license [1] [11] |
Why MSSPs switch
01
Every product has a published unit price, so you can model margin per customer before you talk to anyone.
02
Each tenant is isolated by default, and your team works across all of them 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
One detection can follow a phish to the laptop to the cloud account, without reselling three more vendors.
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.
Splunk details come from the public sources below, with the date of each source. Product names belong to their owners.