Splunk Enterprise Security is sold by quote and runs on top of the Splunk platform. nano publishes its price per GB/day and includes detections, risk-based alerting, cases and playbooks in one license, normalizes to OCSF at ingest, and runs on your own servers or cloud account. Your HEC pipelines move over in their HEC format.
| nano | Splunk ES | |
|---|---|---|
| Price | Published list price, per GB/day of ingest: from US$149/month at 5 GB/day, US$279/month at 10 GB/day. No per-user, endpoint or query fees. | By quote. Both ES editions, Essentials and Premier, show "Get a quote" instead of a price, with activity-based, workload or ingest pricing. splunk.com · pricing ↗ |
| What you buy | One product. Collection, OCSF parsing, nPL search, detections, cases, playbooks, risk-based alerting and pivt AI are all in the same license. | ES, "a unified TDIR platform", runs on top of the Splunk platform: on a search head or search head cluster of Splunk Enterprise, or as a service on Splunk Cloud Platform. splunk.com · Enterprise Security ↗help.splunk.com · ES deployment ↗ |
| Where it runs | Wherever you run it: your servers, your own cloud account in any region, Kubernetes, or air-gapped. Your logs never reach nano. docs · Kubernetes ↗docs · Air-gapped ↗ | On premises, on Splunk Cloud Platform, or hybrid. Splunk Cloud Platform customers work with Splunk Support to set up, manage and maintain their cloud infrastructure, and hybrid search with ES is not supported with Splunk Cloud Platform. help.splunk.com · ES deployment ↗ |
| Normalization | Once, at ingest. Parsers map each record to OCSF 1.9 before it is stored, so every detection, risk rule and case reads normalized fields. docs · OCSF schema ↗ | At search time, with the CIM: field aliases, extractions, lookups, tags and event types maintained over events already indexed. help.splunk.com · CIM ↗ |
| Detections | Detection rules in nPL, scheduled or real-time, promoted from Staging to Live to Alerting. They can live in Git as YAML files. docs · Detection rules ↗ | "Scheduled correlation searches or risk rules" in SPL. Event-based detections create findings or intermediate findings; finding-based detections group them. help.splunk.com · ES detections ↗help.splunk.com · ES findings ↗ |
| Risk-based alerting | Included in every license. Rules add risk with the risk command; nano accumulates each entity's risk over 24 hours and 7 days with decay, and a risk rule alerts on the total. docs · Risk-based alerting ↗ | Finding-based detections, formerly risk incident rules, create findings when they exceed a risk threshold. help.splunk.com · ES risk-based findings ↗help.splunk.com · ES detections ↗ |
| Asset and identity context | Lookup tables you upload or import on a schedule, the asset and resolve_identity commands, and entities extracted from every alert into its case. docs · Lookup tables ↗docs · resolve_identity ↗docs · Entities ↗ | The asset and identity framework fills lookups from external sources and correlates them with events at search time. help.splunk.com · ES asset and identity ↗ |
| Response | Cases and playbooks for analysts and pivt AI, on the model you choose, including a self-hosted one. docs · Playbooks ↗docs · pivt AI ↗ | Adaptive response actions on detections and findings, such as send an email, run a script or create a finding, plus Splunk SOAR. help.splunk.com · ES adaptive response ↗ |
The license is priced per GB/day of ingest. Nothing per user, endpoint or query.
Above 100 GB/day, sized with sales. Prices in US dollars, excluding taxes.
Each Splunk ES concept and its closest nano equivalent, with the nano docs for each. Splunk ES 8 renamed notable events to findings and risk events to intermediate findings; both names are shown.
| nano | How it works in nano | Splunk ES |
|---|---|---|
| Detection rule in nPL | A scheduled or real-time nPL query over OCSF events. New rules start in Staging, bake in Live, and raise alerts in Alerting. docs · Detection rules ↗ | Correlation search (detection in ES 8) |
| Alert | Created when a rule in Alerting mode matches. Analysts acknowledge it and close it with a disposition. docs · Alerts ↗ | Notable event (finding in ES 8) |
| Finding with a risk score | nano records a finding for every rule match. The risk command attributes it to an entity with a score and a reason, without raising an alert of its own. docs · Risk-based alerting ↗ | Risk event (intermediate finding in ES 8) |
| Risk rule | A detection rule over the risk dataset that alerts when an entity's accumulated, decaying score crosses your threshold. docs · Risk-based alerting ↗ | Risk incident rule (finding-based detection) |
| Case | Alerts grouped by host, user, IP or rule into one workspace with entities, a timeline and an investigation notebook. docs · Cases ↗ | Investigation |
| Entity context | Lookup tables for owners, criticality and departments; asset and resolve_identity in nPL; users, hosts and IPs extracted from each alert into its case. docs · Lookup tables ↗docs · asset ↗docs · resolve_identity ↗docs · Entities ↗ | Asset and identity framework |
| Playbook | A versioned plan of queries, pivots, enrichments, decisions and actions, attached to a case for analysts and pivt to work. docs · Playbooks ↗ | Adaptive response action |
| OCSF 1.9 | Applied once at ingest by the source's parser, so there is nothing to maintain at search time. docs · OCSF schema ↗ | CIM data model |
Every paid nano license includes all of this, at every GB/day size, on top of ingest, OCSF parsing, nPL search, detections and alerting.
| Capability | What it does |
|---|---|
| Cases, playbooks and incidents | Group related alerts into cases with evidence, timeline, queues and routing; correlate cases into incidents. |
| Risk-based alerting | Detections add risk to a user, host, IP or account; a risk rule alerts when the accumulated score crosses a threshold. docs · Risk-based alerting ↗ |
| pivt AI investigations | AI triage and investigation, off by default. When on, it calls the model endpoint you configure, including a self-hosted one. docs · pivt AI ↗ |
| SSO | OIDC single sign-on with group mapping and SCIM. |
| High availability and Kubernetes | Multi-node clusters and Helm deployment at every license size. docs · Kubernetes ↗ |
| Air-gapped operation | Offline license, signed image bundle and content packs you import by hand. docs · Air-gapped ↗ |
| Support | Business-hours support from nano. |
nano's engine is also free and open source under AGPL-3.0, with fewer features: open source.
Run both side by side, move sources over one at a time, and compare detections before you switch.
| Piece | What to do | Status |
|---|---|---|
| HEC senders Cribl, Fluent Bit, OTel Collector, apps | Point them at nano. nano's HEC endpoint accepts the Authorization: Splunk <token> header, /services/collector/event and /raw, and indexer acknowledgements, so your pipelines keep their HEC format, with one HEC token per source type. | Drop-in docs · HEC ↗ |
| Splunk forwarders Universal forwarder (S2S) | Route them through an HEC client such as Cribl Stream, or swap the forwarder for Vector or the OpenTelemetry Collector. | Via an HEC client docs · HEC ↗docs · Cribl ↗ |
| Correlation searches and risk rules | Hand them to a coding agent with nano's detection-as-code setup. It ports each one to nPL, carrying risk scores into the risk command, and you review it before you enable it. Recreate your risk thresholds as risk rules. | Agent-assisted docs · Porting rules ↗docs · Risk-based alerting ↗ |
| Asset and identity lists | Export them as CSV and upload them as lookup tables, or import them from a URL on a schedule. | Upload docs · Lookup tables ↗ |
| Response | Write your adaptive response and SOAR steps as nano playbooks attached to cases. | Your plan docs · Playbooks ↗ |
| Historical data | Keep it in Splunk until its retention runs out, or replay what you need through HEC. | Your choice |
Moving off the Splunk platform as a whole: nano and Splunk. Size the target with the host sizing guide and check what your install sends to nano before you start.
To get the SOC features of ES without a quote or a second product. nano publishes its list price per GB/day (from US$149/month at 5 GB/day) and includes detections, risk-based alerting, cases, playbooks and AI investigation in one license. It normalizes to OCSF once at ingest instead of mapping fields at search time, and runs on your own servers, in your cloud account or air-gapped.
By quote. Splunk's pricing page shows "Get a quote" for both ES editions, Essentials and Premier, with activity-based, workload or ingest pricing, and no list price. ES runs on the Splunk platform, on Splunk Enterprise or Splunk Cloud Platform. nano is priced per GB/day of ingest with published list prices and every feature included.
In Splunk ES 8.0 and higher, the term finding replaces notable events and the term intermediate finding replaces risk events. Findings are alerts or events created by detections; intermediate findings are not shown in the analyst queue, and finding-based detections can combine them with other findings. In nano, an alert is what an analyst triages, and a finding is the record of a rule match, often with a risk score attributed to an entity.
Yes, in every license. A detection rule adds risk to a user, host, IP, email address or cloud account with the risk command. nano accumulates each entity's risk over 24 hours and 7 days with older findings decaying, and a risk rule, a detection rule over the risk dataset, alerts when the total crosses your threshold.
Upload your asset and identity lists as lookup tables, or import them from a URL on a schedule, and add them to events with lookup. The asset command investigates a host, user, IP or MAC across its related identities, resolve_identity fills in the host or user an IP belonged to at the time, and every alert's users, hosts and IPs are extracted into its case.
Yes. nano's HEC endpoint accepts the Authorization: Splunk <token> header, the /services/collector/event and /raw paths and indexer acknowledgements, so Cribl Stream, Fluent Bit, the OpenTelemetry Collector and your own HEC clients keep their HEC format. Use one HEC token per source type. Splunk universal forwarders go through an HEC client such as Cribl Stream.
Give your correlation searches and risk rules to a coding agent with nano's detection-as-code setup. It ports each one to nPL, and you review it before enabling it. Because nano normalizes to OCSF at ingest, a ported rule can cover other sources that map to the same fields; test it against each one before you enable it.
Nowhere outside your environment. nano is software you run on your own servers, in your own cloud account, on Kubernetes or air-gapped, and nano, LLC never receives your logs. A connected install sends nano a daily license check-in and one GB/day number, and downloads content and feeds; air-gapped installs send nothing. pivt AI is off by default and calls the model endpoint you configure.
Last reviewed 14 November 2026.
From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.