Splunk is sold by quote and gets expensive as your data grows. nano publishes its price per GB/day, includes every feature in one license, normalizes everything to OCSF at ingest, and runs on your own servers or cloud account. Your HEC pipelines move over in their HEC format, with one token per source type.
| nano | Splunk | |
|---|---|---|
| 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. Splunk Cloud Platform, Splunk Enterprise and Enterprise Security are priced by activity, ingest or workload, and none has a published list price. splunk.com · pricing ↗ |
| What the license includes | Everything: collection, OCSF parsing, detections, nPL search, cases, playbooks, risk-based alerting, pivt AI, SSO, high availability and air-gapped operation. | The platform and the SIEM are separate products: Splunk Enterprise Security, "a unified TDIR platform", is bought on top of Splunk Cloud Platform or Splunk Enterprise. splunk.com · Enterprise Security ↗ |
| Normalization | Once, at ingest. Parsers map each record to OCSF 1.9 before it is stored, so every search and detection runs on fields that are already normalized. docs · OCSF schema ↗ | At search time. "You normalize your data to be CIM compliant at search time," with field aliases, field extractions, lookups, tags and event types maintained over the indexed events. help.splunk.com · CIM ↗ |
| Storage | A columnar event store: OCSF events in ClickHouse. Older data tiers to your own S3-compatible object storage and stays searchable. | An indexer stack: forwarders send data to indexers, search heads fan searches out to them, and each index is a set of buckets aged hot, warm, cold, frozen and thawed. help.splunk.com · components ↗help.splunk.com · index storage ↗ |
| Search language | nPL, a pipe-based language that reads left to right, so it feels familiar to SPL users. A coding agent can port your saved searches and detections. docs · Porting rules ↗ | SPL |
| 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. | Splunk Cloud Platform (Splunk-managed SaaS), or Splunk Enterprise in a private cloud or on-prem. splunk.com · pricing ↗ |
| Free option | nano's engine is open source under AGPL-3.0, free to self-host with no daily limit from nano. | Splunk Free: up to 500 MB/day indexed, single instance, some features removed. help.splunk.com · Splunk Free ↗ |
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.
What each familiar Splunk concept is called in nano, and what it does there.
| nano | Splunk | What it is in nano |
|---|---|---|
| Log source and parser | Sourcetype | Each source type gets a log source with its own HEC token, and its parser maps records to OCSF. docs · HEC ↗ |
| Event store | Index | One ClickHouse event store. Filter by OCSF class or log source; retention is one setting, 365 days by default. docs · Storage ↗ |
| OCSF, at ingest | CIM, at search time help.splunk.com · CIM ↗ | Records are normalized once, before they are stored. docs · OCSF schema ↗ |
| nPL | SPL | Pipe-based and read left to right. A coding agent ports your searches; you review. docs · Porting rules ↗ |
| Detection rule | Detection (correlation search) help.splunk.com · ES glossary ↗ | An nPL rule over OCSF events that moves from Staging to Live to Alerting as you gain confidence in it. docs · Detection rules ↗ |
| Alert | Finding (notable event) help.splunk.com · ES glossary ↗ | Raised when a rule in Alerting mode matches, ready for triage. docs · Detection rules ↗ |
| Risk rule | Risk-based alerting, finding-based detection help.splunk.com · ES glossary ↗ | 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 ↗ |
| Case | Investigation help.splunk.com · ES glossary ↗ | Groups related alerts with evidence, entities and a timeline; related cases correlate into incidents. docs · Cases ↗ |
| Lookup table | Lookup | Reference data such as asset lists, allowlists and indicators, used in searches and rules. docs · Lookup tables ↗ |
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: point them at nano 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 ↗ |
| Parsing | Pick parsers from the catalog for each source, or let the AI parser builder write one from sample lines. Every source lands in OCSF. | Per source |
| Searches and detections | Hand your saved searches and correlation rules to a coding agent with nano's detection-as-code setup: it ports each one to nPL, and you review before you enable it. | Agent-assisted docs · Porting rules ↗ |
| Historical data | Keep it in Splunk until its retention runs out, or replay what you need through HEC. | Your choice |
Size the target with the host sizing guide and check what your install sends to nano before you start.
Price you can plan around and a simpler stack. nano publishes its list price per GB/day (from US$149/month at 5 GB/day) with every feature included, where Splunk is sold by quote. nano normalizes to OCSF once at ingest instead of mapping fields at search time, stores events in ClickHouse, and runs wherever you put it, including air-gapped, with your logs never leaving your environment.
Splunk prices its products by activity, ingest or workload, depending on the product, and sells them by quote; its pricing page lists no list prices for Splunk Cloud Platform, Splunk Enterprise or Enterprise Security. Splunk Free indexes up to 500 MB a day on a single instance. nano is priced per GB/day of ingest with published list prices and every feature included.
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. Point them at nano with one HEC token per source type: the token decides the log source, so a forwarder that sends several log types uses one HEC output per type. Splunk universal forwarders go through an HEC client such as Cribl Stream.
nPL is pipe-based and reads left to right, so SPL users pick it up quickly. To move existing content, give your saved searches and correlation rules to a coding agent with nano's detection-as-code setup: it ports each one to nPL, and you review it before enabling. 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.
Splunk applies its Common Information Model at search time, with field aliases, field extractions, lookups, tags and event types maintained over events already indexed. nano normalizes at ingest: parsers map each record to OCSF 1.9 before it is stored in ClickHouse, so searches and detections run on normalized fields with nothing to maintain at search time.
Yes: nano. You install it on your own servers, in your own cloud account or on Kubernetes, or run it air-gapped. It is a full SIEM on ClickHouse with OCSF parsing, detections, cases, risk-based alerting and AI-assisted investigation on your own model, licensed per GB/day with every feature included, and your logs never leave your environment.
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.