Open source

Open and auditable by design.

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
Self-host Open source in minutes: Docker, one command. Quickstart guide
Why open

Security tools should be readable.

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.

01 · Auditable

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.

02 · No lock-in

No vendor lock-in on your data plane.

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.

03 · Community

Community-driven detections.

Detection rules and parsers improve faster when they're open. Practitioners contribute the rules they actually use, and everyone benefits.

04 · Transparency

Trust through transparency.

A SIEM is a security-critical piece of infrastructure. "Trust us" isn't a good answer. Reading the source is.

What's open

Two editions. That's all.

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
Licensing

Two licenses, clearly separated.

If you're an enterprise legal team reading this, the short version is below.

When you run the engine yourself

AGPL-3.0

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.

When you choose paid nano

Commercial

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.

Which one

Open source, or paid nano.

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.

Self-host (AGPL)

You run the engine.

  • Full control of data plane, retention, and tuning
  • No usage limits from nano
  • You operate Postgres, ClickHouse, ingestion, upgrades, and detection content
  • Community support via the repo
  • Commercial modules (Cases, pivt, entity risk analytics, notebooks, playbooks, AI tuning, SSO, air-gap) not included
nano (Commercial)

The whole product, still yours to run.

  • Same engine and installer, with every commercial module unlocked by your license
  • Your servers or your cloud account; air-gapped if your environment requires it
  • Kubernetes, HA replicas and air-gapped operation included at every size
  • Signed, digest-verified releases and detection content, updated for you
  • Business-hours support for the nano software; you still operate the infrastructure
  • Your logs stay in your environment: what your install sends to nano

Read the source. Then decide.

Both paths run the same engine. Start with whichever fits, and switch when you outgrow it. Weighing other options? Compare open-source SIEMs.

Read the source on GitHub See the product