Elastic Security runs on the Elastic Stack, self-managed or on Elastic Cloud. nano is a SIEM you run yourself, with events in OCSF on ClickHouse, licensed per GB/day with every feature included.
| nano | Elastic Security | |
|---|---|---|
| What it is | A SIEM: log collection, OCSF parsing, nPL search, detections, cases, risk-based alerting and AI-assisted investigation in one product. docs · Getting started ↗ | Elastic Security, on the Elastic Stack (Elasticsearch, Kibana and Integrations): "Unified SIEM, XDR, and native automation included." elastic.co · SIEM ↗elastic.co · subscriptions ↗ |
| License | Commercial license for the full product. The engine is also published free under AGPL-3.0, with fewer features. github.com/nano-rs ↗ | Elasticsearch and Kibana are offered under ELv2, SSPL or AGPL. Elastic's detection rules repository is under the Elastic License v2. elastic.co · licensing ↗github.com/elastic/detection-rules ↗ |
| Where it runs | Only where you run it: one server with Docker Compose, a high-availability cluster, or Kubernetes with Helm, on your servers or your own cloud account, or air-gapped. Your logs never reach nano. docs · Kubernetes ↗docs · Air-gapped ↗ | Elastic Cloud Hosted, Elastic Cloud Serverless, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, or self-managed. "Elastic deploys on-premises, in the cloud, or in air-gapped environments." elastic.co/docs · Deploy ↗elastic.co · SIEM ↗ |
| Storage and search | Events normalized to OCSF 1.9 at ingest and stored in ClickHouse, searched with nPL, nano's own query language. docs · OCSF schema ↗ | Elasticsearch. Detection rules can use KQL or Lucene, EQL for event correlation, and ES|QL pipe-based queries. elastic.co/docs · detection rules ↗ |
| Detection rules | Scheduled detections in nPL with MITRE ATT&CK mapping, retro hunt and risk scoring. Detections can live in Git as YAML files. docs · Porting rules ↗ | Seven rule types: custom query, event correlation, ES|QL, machine learning, threshold, indicator match and new terms. Rules are "developed by Elastic Security Labs, validated by the community, and open for review." elastic.co/docs · detection rules ↗elastic.co · SIEM ↗ |
| AI | pivt AI triage and investigation, off by default. When on, it calls the model endpoint you configure, including a self-hosted one. docs · pivt AI ↗ | "The Elastic AI Agent ships with purpose-built skills for every SOC stage out of the box." Elastic Security is also reachable from MCP-compatible AI tools. elastic.co · SIEM ↗ |
| How it is sold | Per GB/day of ingest, from US$149/month at 5 GB/day (US$279/month at 10 GB/day). Every paid license includes every feature. | Self-managed subscriptions, including the free Basic tier and Enterprise. Elastic Cloud Hosted is resource based and Elastic Cloud Serverless is usage based. elastic.co · subscriptions ↗elastic.co · pricing ↗ |
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.
Every paid nano license includes all of this, at every GB/day size. The free open-source engine includes ingest, parsing, nPL search, detections and alerting, but not these.
| 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. |
Compare nano's free and paid editions line by line: open source. Open source SIEMs side by side: Wazuh, Security Onion, Elastic and nano.
What each familiar Elastic Security concept is called in nano, and what it does there.
| nano | Elastic Security | What it is in nano |
|---|---|---|
| OCSF, at ingest | ECS elastic.co/docs · ECS ↗ | nano's parsers map each record to OCSF 1.9 before it is stored. docs · OCSF schema ↗ |
| nPL | KQL, EQL and ES|QL elastic.co/docs · detection rules ↗ | One pipe-based language for search and detection. A coding agent ports your rules; you review. docs · Porting rules ↗ |
| Detection rule | Detection rule elastic.co/docs · detection rules ↗ | An nPL rule over OCSF events that moves from Staging to Live to Alerting as you gain confidence in it. docs · Detection rules ↗ |
| Alert | Alert elastic.co/docs · detection rules ↗ | Raised when a rule in Alerting mode matches, ready for triage. docs · Detection rules ↗ |
| Risk rule | Entity risk scoring elastic.co/docs · entity risk scoring ↗ | 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 | Case elastic.co/docs · cases ↗ | Groups related alerts with evidence, entities and a timeline; related cases correlate into incidents. docs · Cases ↗ |
Run both side by side, move sources over one at a time, and compare detections before you switch.
| Piece | What to do | Status |
|---|---|---|
| Sources | Onboard each source in nano from the catalog: every install starts with zero log sources. Logs arrive over HEC, HTTP, OTLP, cloud pull and Vector agents; if your pipeline already publishes to Kafka, nano can consume the topic. | Per source docs · Integrations ↗docs · Kafka ↗ |
| Running both | Keep Elastic running while you compare. Where a collector can write to more than one destination, send the same events to both during the overlap. | Your plan |
| Your own rules and searches | For rules you wrote, a coding agent with nano's detection-as-code setup ports each one to nPL, and you review it before you enable it. For Elastic's prebuilt rules, use nano's detection packs from the catalog. | Agent-assisted docs · Porting rules ↗ |
| Historical data | Keep it in Elasticsearch for its retention period, and plan the cut-over date around your retention obligations. | Your plan |
Size the target with the host sizing guide and check what your install sends to nano before you start.
Yes. Elastic presents Elastic Security as a security operations platform with SIEM, XDR and native automation, built on the Elastic Stack. Its detection engine supports custom query, EQL, ES|QL, machine learning, threshold, indicator match and new terms rules.
Yes. Elastic lists self-managed installs, Elastic Cloud Enterprise and Elastic Cloud on Kubernetes alongside its Elastic-operated Elastic Cloud Hosted and Serverless offerings, and says Elastic deploys on-premises, in the cloud or in air-gapped environments.
Elastic added AGPL in 2024 as a license option for Elasticsearch and Kibana, next to the Elastic License v2 and SSPL. Elastic's detection rules repository is licensed under the Elastic License v2. nano's engine is open source under AGPL-3.0, and its paid license is commercial.
Another SIEM that can run in your own environment. nano is one: a SIEM on ClickHouse that normalizes events to OCSF at ingest, searches them with nPL, and includes cases, risk-based alerting and AI-assisted investigation on your own model in every paid license. Wazuh, Security Onion and nano's own AGPL engine are free options.
Elastic Security runs on Elasticsearch and offers several query languages (KQL, Lucene, EQL and ES|QL), with Elastic-operated cloud options as well as self-managed ones. nano stores OCSF events in ClickHouse, uses one query language, nPL, runs only where you run it, and is licensed per GB/day with every feature included.
Hand the rules you wrote to a coding agent with nano's detection-as-code setup. It ports each rule to nPL from the source rule and a nano example, and you review it before you enable 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.