Features

A SIEM you can read. And one that runs.

Open-core engine in Rust. Sub-second search on ClickHouse, in one store and one language. Everything below is in nano and runs inside your environment; sections marked Open source are also in the free AGPL edition.

The engine

Fast on purpose. Reliable by design.

Rust at the core, ClickHouse for storage, Vector for ingest. No JVM warmups, no garbage-collection pauses, no surprise memory limits. The whole stack picked for one job, which is getting your team to an answer.

Small install
4vCPU · 16 GB
Up to 5 GB/day on one server, with a 750 GB SSD for a year of data.
Mid-size install
8vCPU · 32 GB
10 to 15 GB/day, with a 1.5 TB SSD. Size the host
One server
~100GB/day
Most installs fit on one server. Add servers for high availability, or Kubernetes above about 1 TB/day.
Rust Memory-safe core. Detection, query planner, ingest pipeline. All Rust.
ClickHouse Columnar storage. Sub-second search, compression baked in.
Vector High-throughput ingest. Parses, normalizes, and routes events at line rate.
Open source

Read the source. Run it yourself.

The core engine, the detection rules, the parsers and the docs are in the open: the engine is AGPL-3.0, free to audit, fork and self-host. The paid license adds the commercial modules (cases, pivt AI, entity risk analytics, SSO, HA, Kubernetes, air-gapped operation) on the same installer. Two editions, one installer.

Search · Open source

Queries that make sense.

Pipe-based, left-to-right, familiar if you've used a search-and-pipe SIEM. Stricter, faster, and the autocomplete actually knows your schema. It works on any logs, so ops teams use it for log management too.

Brute force detection
1class_uid=3002 activity_id=1 status_id=2
2| stats count as attempts by src_endpoint.ip, user.name
3| where attempts > 10
4| sort -attempts
5...
Rare domain hunting
1class_uid=4002 earliest=-7d
2| prevalence enrich=true window=7d
3| where host_count < 3 AND is_rare=true
4| table http_request.url.hostname, first_seen, host_count
5...
Process tree analysis
1class_uid=1007
2| prevalence enrich=true
3| tree process root="*powershell*"
4...
Beaconing detection
1class_uid=4002
2| bin span=10m
3| stats count by time_bucket, http_request.url.hostname
4| stats stdev(count) as jitter, avg(count) as avg_hits by http_request.url.hostname
5...
Detection · Open source

Rules in nPL. Not YAML hellscapes.

YAML frontmatter for metadata, pipe-language for the actual hunt. MITRE mapping, per-rule risk scores and prevalence enrichment are first-class, not glued on with a script.

beacon_interval.yml ···
1---
2title: regular_beacon_interval_detection
3severity: high
4mode: staging
5schedule: "*/10 * * * *"
6mitre_tactics: TA0011
7mitre_techniques: T1095
8---
9class_uid=4002
10| where NOT cidr_match("10.0.0.0/8", dst_endpoint.ip) AND NOT cidr_match("192.168.0.0/16", dst_endpoint.ip)
11| stats count, dc(time) as unique_times by src_endpoint.ip, http_request.url.hostname
12| where count > 20 AND unique_times > 15
13| prevalence enrich=true window=30d
14| risk score=70 entity=src_endpoint.ip factor="Regular beacon pattern"
15| table src_endpoint.ip, http_request.url.hostname, count, unique_times, host_count, risk_score
Investigation

From alert to closed ticket.

Cases bundle the alert, the evidence, the timeline, and the analyst's notes in one place. Notebooks for ad-hoc hunting, and scheduled hunts that send you only the findings that hold up. Process trees and identity resolution for the messy parts. And SOAR flows to contain, suspend and ticket, with a person approving the disruptive steps.

CASE-2026-0421 In progress
PowerShell process tree off jsmith-pc
SeverityHigh · 87/100 Assigneemira@acme.io Entityjsmith-pc · jsmith@acme.io Detectionsuspicious_powershell_chain
10:42AlertDetection fired, severity high
10:43pivtPulled process tree, identity, asset context
10:46Notemira: "looks like a phishing payload"
10:51ActionHost quarantined via EDR integration
Process tree · jsmith-pc
explorer.exe PID 1234
└ outlook.exe PID 2345
  └ powershell.exe PID 3456
    └ cmd.exe /c whoami PID 4567
      └ certutil.exe -decode PID 5678
        └ payload.exe PID 6789
Common Uncommon Rare
Identity resolution resolved in 84ms
192.168.1.50
───►
jsmith-pc
DHCP
EDR · Sysmon
Proxy logs
NAT detected 10.0.0.1 → 47 hosts/hour
AI agents

Agents that do the boring parts.

pivt, nano's AI assistant, triages alerts, drafts parsers, follows playbooks and writes case notes. Configurable, auditable, and never the one closing the ticket without you.

Off by default. Point pivt at any OpenAI-compatible endpoint, including self-hosted models, or the Anthropic Messages API with your own key. Model calls go straight to that endpoint, never through nano. More about pivt AI

01 Detection Alert fires
02 pivt Auto-triage & pull context
03 pivt Run playbook steps
04 pivt Draft case summary
05 Analyst Review & close
01 · Workflows

Full agent workflows.

Define steps in YAML. pivt runs them on the alerts you choose: pull EDR context, check threat intel, query identity, draft a summary. Stop a step for human approval whenever you want.

02 · Parsers

AI-built parsers.

Drop a sample log, get a working parser. pivt reads the format, drafts the parser, validates it against your data. The 80% case in two minutes, not two days.

03 · Playbooks

Playbooks agents follow.

Write incident response runbooks once. pivt executes them on the right alerts, asking for human confirmation on the steps that need it. Auditable trail of every action.

Enrichment & content

Context without the clicks.

By default, events are enriched on your servers at ingest from one signed feed bundle: IPinfo Lite (IP country, continent and network owner), ThreatFox indicators and the Tor exit-node list. The bundle updates hourly; turn it off or mirror it. Everything else, from asset context to lookups with your own API keys, is yours to configure. What the feeds send (nothing)

IPinfo Lite
ip 185.220.101.1
country DE
continent EU
Default · on ingest✓ local
Network owner
asn AS12345
as_name Example Hosting
as_domain example.net
Default · IPinfo Lite✓ local
ThreatFox
ioc evil-c2.example
threat botnet_cc
source abuse.ch
Default · on ingest✓ local
Tor exit nodes
ip 185.220.101.1
tor_exit true
source Tor Project
Default · on ingest✓ local
Your lookups
provider URLhaus, VirusTotal…
key yours
goes to that provider
Opt-in · your API keyoff by default
Your own data
owner J. Smith
dept Finance
source your CMDB
Custom · licensedyou configure
Content catalog

You choose every source.

Every install starts with zero log sources. The catalog of parsers, detection rules and enrichments syncs from nano as signed, versioned content, and you choose what to onboard. Or fork them and make them yours. Already run OpenTelemetry? Send it over OTLP.

The catalog lives inside nano. Browse and choose without leaving the product. Every artifact is open source, so fork and contribute through GitHub.

Entity · jsmith@acme.io Risk score
87 / 100
High
Failed logins · 3 in 24h+24
Suspicious download · cobalt-strike beacon+38
Off-hours activity · 03:14 local+15
Rare process · certutil decode+10
Entity risk & prevalence

Risk that gets the right number.

Risk scores stack across signals. Rules contribute weighted factors, prevalence baselines tell you what's actually rare, and the score updates in real time as more events land.

  • Configurable weights per detection rule and entity type
  • Prevalence baselines built from 365+ days of your data
  • Decay curves so old signals fade, fresh ones dominate
  • Entity types you define · users, hosts, services, apps
Operations

Your SIEM checks its own pulse.

Dashboards that compose. A health page that watches the pipeline, with pivt's health analysis every 12 hours once you configure a model. And settings deep enough to make every team's nano feel custom, without a fork.

SIEM health · acme-prod Last scan 4h 12m ago by pivt
Ingestion 8.4 GB/d Healthy
Detection 142 rules Healthy
Search Normal Healthy
Storage 82% used Warning
AI Your model Healthy
pivt Storage at 82% of disk capacity, projected to fill in ~18 days at current ingest. The Sysmon source from fleet-2 increased 40% over the last week, likely a new EDR rollout. Consider archiving older partitions or enabling object-storage tiering.
SOC analyst home Last 24h
Open cases
14
-3 vs yesterday
High-risk entities
7
+2 vs yesterday
Alerts 7-day avg
Settings ⌘K · Search 240 settings
General 18 settings
Data sources 32 settings
Detection 47 settings
AI & agents 28 settings
Integrations 61 settings
Team & access 22 settings
Billing 12 settings
Getting started

From install to first detection.

Five steps. No services engagement. No "professional services" line item on the invoice. Most teams hit step 5 the same afternoon.

1
Deploy
Install on your servers, your cloud account or your Kubernetes: Open source free, or the whole product with your license. Air-gapped too, if you need it.
2
Connect a source
Start from zero and choose from the catalog: cloud audit, EDR, firewall. Drop a sample for the rest.
3
Run a search
Pipe-language query bar. Autocomplete knows your schema. Sub-second answers.
4
Enable detections
Choose detection packs from the catalog, or write your own in nPL.
5
Get alerted
Alerts land in cases. With pivt on your model, its triage is already there. You take it from there.

Full walkthrough in the install guide, or let your coding agent do it with the nano-deploy skill. Deployment options in the nano overview.

Stop avoiding the search bar. Start using one.

Buy nano online, run the demo, or install Open source and ingest something this afternoon.

Buy nano Install Open source

Open source free under the AGPL · One license, every feature at every size · Read the docs