nano · Self-hosted SIEM

The self-hosted SIEM that keeps your logs where they are.

nano is a full SIEM (collection, detections, search, cases and AI-assisted investigation) that you run on your own servers, in your own cloud account or on an air-gapped network. Sovereign by architecture: nano never receives your log data.

See pricing and buy online
Talk to sales
What nano is

One license. Your infrastructure. Our software.

You buy the license and run nano yourself. It uses the same installer as nano's free, open-source edition and unlocks the full product with your license values.

You run it

Your servers, your network, your retention.

Events are stored as OCSF in ClickHouse on disks you own, with optional tiering to your own S3-compatible storage. Retention is your setting, not a price tier.

nano ships it

Signed releases, content and support.

Signed, digest-verified releases, signed detection and parser content, and business-hours support by request and email for the nano software. What the plan includes

Everything in one product

Collect, detect, investigate, respond.

Ingest over HEC, HTTP, OTLP and cloud pull; real-time and scheduled detections; nPL search; cases, playbooks and risk analytics; pivt AI on your own model. Every install starts with zero log sources: you choose what to onboard from the catalog.

Deployment options

Pick a layout for availability, not capacity.

One server handles up to about 100 GB/day. Add servers when ingest and storage must survive the loss of one. A high-availability cluster counts as one install, and one license covers two installs: production plus one for dev, DR or backup.

LayoutUse it whenWhat you provide
One server Docker Compose One server is enough. Most installs up to about 100 GB/day. Linux VM or physical server; 8 vCPU and 32 GB RAM covers 10–15 GB/day
Three servers, HA Docker Compose Event storage, search and ingest must survive the loss of a server. Three or more servers; counts as one install
More servers Docker Compose More ingest, ClickHouse or Keeper servers as you grow. Custom multi-node layouts
Kubernetes Helm You already run Kubernetes, or ingest more than about 1 TB/day. Your cluster, in your cloud account or data center
Air-gapped Compose or Helm The servers can't reach the internet. Signed image, content and license bundles carried across the gap and imported by hand

Size the host

Daily volumevCPURAMDisk, 365 days
Up to 5 GB/day 4 16 GB 750 GB
10–15 GB/day 8 32 GB 1.5 TB
25–50 GB/day 16 64 GB 3–6 TB
50–100 GB/day 16–32 64–128 GB 6–12 TB
About 1 TB/day or more Use Kubernetes
Starting points from the install guide. SSD for data; plan for bursts of 3× your average rate.

Who installs it

Sovereignty by architecture

Not a promise about where we keep your logs. We never have them.

Data residency is a contract about where a vendor stores your data. Running nano yourself removes the vendor from the data path: logs are collected, stored and analyzed inside your environment, so your own controls, jurisdiction and assessments apply to them.

Your environment

Your data center, your cloud account in the region you choose, or an air-gapped network

01 · Sources
  • firewalls
  • Windows events
  • Entra ID
  • Okta
  • CloudTrail
  • EDR
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano inside your environment. nano, LLC (US) never receives log data.

Every connection a connected install makes, what it carries and how to switch it off: What your install sends to nano.

AI stays local

pivt AI uses your model, or none.

AI is off until you configure a provider. Your install has no nano-managed AI default and no shared nano model account.

Self-hosted models

Any OpenAI-compatible endpoint.

Point pivt at vLLM, Ollama, LM Studio, LiteLLM or your corporate gateway inside your network, and prompts never leave it.

Cloud models

Or the provider you already use.

Use the Claude (Anthropic Messages) API or any OpenAI-compatible API with your own key. Prompts go to that provider directly, not through nano. Data flows

Or no AI

The SIEM works without it.

Ingest, detections, search, alerting, dashboards and cases work with no model at all. Leave AI unconfigured if your policy says so.

Pricing and buying

Per GB/day of ingest. Nothing per seat, endpoint or query.

License, updates and business-hours support for the nano software. You run the infrastructure. Annual billing saves 10%. Above 100 GB/day, it is sized with you.

Daily ingestList price per monthBilled annually, per month
5 GB/day US$149 US$134
10 GB/day US$279 US$251
25 GB/day US$599 US$539
50 GB/day US$1,099 US$989
100 GB/day US$2,100 US$1,890
List prices in US dollars, excluding taxes. Between these points the price moves smoothly with volume; see the pricing page.
01

Sign in and register a deployment

At app.nano.rs, choose your daily volume.

02

Pay by card or invoice

Monthly by card, or annually by card or by invoice (bank transfer or card). Trials are reviewed by our team first.

03

Install with your license values

Your license and installer unlock as soon as payment arrives. Install on your servers or let your agent do it.

FAQ

Questions we get asked.

What is a self-hosted SIEM?

A self-hosted (on-premise) SIEM is security information and event management software you install and run on infrastructure you control: your own servers, your data center or your own cloud account. Logs are collected, stored, searched and analyzed there, instead of being shipped to a vendor's cloud. nano is a self-hosted SIEM: nano licenses the software, ships updates and gives business-hours support; you run the servers.

Is on-premise or cloud SIEM more secure?

Neither is automatically more secure. A cloud SIEM moves operations to the vendor but puts your logs, and the people and jurisdictions with access to them, outside your control. A self-hosted SIEM keeps logs inside your own boundary and controls, but you carry the operating work: servers, patching, backups and capacity. Choose by who you want holding your security data and who you want running the platform.

Does nano ever see my log data?

No. nano keeps log data in your environment. A connected install sends nano a daily license check-in and one number per completed UTC day, the total GB ingested, and downloads signed content and enrichment updates you can mirror or turn off. Air-gapped installs make no connection to nano at all. The full list is on the data flows page.

Is there a free or open-source version?

Yes. nano's engine is open source under AGPL-3.0 and free to self-host on one server with Docker Compose: ingest, parsing, search, detections and alerting, with community support. nano's paid license runs on the same installer and adds cases, notebooks, pivt AI, risk analytics, SSO, playbooks, custom enrichments, high availability, Kubernetes, air-gapped operation and support.

What hardware does a self-hosted SIEM need?

For nano, one Linux server with 8 vCPU, 32 GB RAM and a 1.5 TB SSD holds about 10–15 GB/day for a year. Up to 5 GB/day needs 4 vCPU and 16 GB RAM; 50–100 GB/day needs 16–32 vCPU and 64–128 GB RAM. One server handles up to about 100 GB/day; above about 1 TB/day, use Kubernetes. Plan for bursts of three times your average rate.

How much does nano cost?

nano is licensed per GB/day of ingest: from US$149/month at 5 GB/day, US$279/month at 10 GB/day, list price, with 10% off billed annually. There are no per-user, per-endpoint or per-query fees. The license covers the software, updates and business-hours support; you pay for your own infrastructure. Above 100 GB/day, it is sized with you.

Can I buy nano online?

Yes. Sign in, register your deployment and pay monthly by card, or annually by card or by invoice (bank transfer or card). Your license and installer unlock as soon as payment arrives. Trials are reviewed by our team first.

Can a self-hosted SIEM run air-gapped?

nano can. Air-gapped operation is included with every license: no outbound connections, a signed offline license renewed by hand, and signed image, content and enrichment bundles you carry across the gap and import yourself. It is more work to run than a connected install, so use it if your environment requires it. AI features, if you want them, use a model endpoint inside your boundary.

Who installs and operates it?

You do, or your partner. The installer checks prerequisites and sizes containers from the server it runs on, and the nano-deploy agent skill lets Claude Code, Codex or another coding agent size, preflight, install, verify and upgrade an install, asking before every change. nano's support covers the installer, Helm chart, upgrades, licensing, configuration and defects in nano, not your own infrastructure.

Is nano certified or IRAP-assessed?

No. nano, LLC is a US company and holds no certification such as ISO 27001, SOC 2 or an IRAP assessment, and using nano does not make you compliant. Because nano runs inside your environment, it sits within your own controls and assessments rather than asking you to trust a vendor-hosted service.

Start with nano.

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.

Buy nano
Talk to sales