Auditable detection logic.
Security teams can read every line of how alerts are generated, how data is parsed, and how the engine behaves under load. No black boxes between you and your data.
The core nano SIEM engine is published under AGPL-3.0. Run it free, or license the paid product on the same installer for the commercial modules. Either way it runs in your environment, and you can read what it does.
curl -fsSL https://get.nano.rs | bash A SIEM sits on the most sensitive data in your organization. We think the people running it should be able to see exactly what it does.
Security teams can read every line of how alerts are generated, how data is parsed, and how the engine behaves under load. No black boxes between you and your data.
If we ever stop being the right vendor for you, the engine keeps running. You can host it yourself under AGPL-3.0, the code doesn't disappear with the subscription.
Detection rules and parsers improve faster when they're open. Practitioners contribute the rules they actually use, and everyone benefits.
A SIEM is a security-critical piece of infrastructure. "Trust us" isn't a good answer. Reading the source is.
Free AGPL Open source, and paid nano with everything included. There is no Enterprise edition: every paid license gets every commercial module below, at every size. Only the price (per GB/day of ingest) and the support level change.
| Feature | Open-source engine | Paid nano |
|---|---|---|
| Core ingestion + storage engine (Rust + ClickHouse) | Open (AGPL-3.0) | Included |
| nPL search, dashboards, reports | Open (AGPL-3.0) | Included |
| Detection rules + lifecycle, alerts, retro hunt | Open (AGPL-3.0) | Included |
| Per-rule risk scores (risk command, global weight) | Open (AGPL-3.0) | Included |
| Parsers + log-source integrations | Open (AGPL-3.0) | Included |
| Lookup tables, prevalence, MITRE coverage | Open (AGPL-3.0) | Included |
| Local auth, MFA, RBAC, audit log | Open (AGPL-3.0) | Included |
| Cases: lifecycle, queues, routing, playbooks | Not included | Commercial |
| Incidents (multi-case correlation) | Not included | Commercial |
| pivt investigations + AI triage | Not included | Commercial |
| Investigation notebooks + chat | Not included | Commercial |
| Entity risk analytics, decay + risk notables | Not included | Commercial |
| AI detection tuning + proposals | Not included | Commercial |
| Custom + AI-agent enrichment (sandboxed) | Not included | Commercial |
| AI SIEM health analysis | Not included | Commercial |
| SSO (OIDC) + group mapping, SCIM | Not included | Commercial |
| Observability ↔ security convergence | Not included | Commercial |
| Air-gapped operation + offline content bundles | Not included | Commercial |
| pivt desktop (native desktop app) | Not included | Commercial |
| Kubernetes deployment + HA replicas | Not included | Commercial |
| Support (business hours; Dedicated by order form) | Community | Commercial |
If you're an enterprise legal team reading this, the short version is below.
The open-source nano repository is licensed under the GNU Affero General Public License v3.0. AGPL applies only to the engine code itself, on the infrastructure you control.
The commercial build of nano includes the commercial modules and support, and is separately licensed under our commercial Terms of Service and the Self-run Addendum. The commercial product is not AGPL-encumbered.
See Terms § 3.1 for the formal version. Questions about licensing for your specific deployment? Talk to us.
Both run on your infrastructure with the same installer and the same engine. The difference is the commercial modules, signed content and support, not who operates it: you run the servers either way.
Both paths run the same engine. Start with whichever fits, and switch when you outgrow it. Weighing other options? Compare open-source SIEMs.