Use case · Log management

Log management you run yourself. For ops teams, not just security.

Send your app, server and cloud logs to one place, search them fast, and keep them as long as you choose, on your own infrastructure. Teams leaving Splunk keep their HEC senders, and nothing is priced per seat or per query.

Try nano open source
Talk to sales
How it works

Every log in one place.

Use the senders you already run. nano parses what it recognizes, keeps every field of what it doesn't, and stores it all on your own disks.

Your infrastructure
01 · Your logs
  • nginx
  • Apache
  • journald
  • syslog
  • app JSON
  • OTLP
  • Kubernetes audit
  • CloudTrail
02 · Send
  • HEC
  • OTLP/HTTP
  • JSON over HTTPS
  • Syslog, Kafka, S3/SQS
03 · nano
  • ShapePipeline steps: filter, redact, dedupe, enrich
  • ParseA catalog parser, or Generic JSON with every field kept
  • StoreClickHouse on disks you own, retention you set
  • UsenPL search, dashboards, alerts
fig 01 · Logs in, parsed and searchable, on your infrastructure.
Pipelines

Shape your data as it arrives.

Every log source has a pipeline: ordered steps that run before events are parsed and stored. Clean out the noise, strip secrets, fix formats and add context on live data, and nothing changes in production until you publish.

Incoming
  • GET /healthz 200 1ms
  • {"user":"ana","msg":"login ok","password":"hunter2"}
  • ERROR db timeout after 30s host=pay-1
Pipeline
  1. Filter
  2. Redact
  3. Parse
  4. Dedupe
  5. Lookup
{"user":"ana","msg":"login ok","password":"hunter2""[REDACTED]"} Redact: password masked before storage
dropped 2 redacted 1 merged 2 stored 3
Stored
  • user=ana msg="login ok" password=[REDACTED] team=identity
  • level=ERROR msg="db timeout" host=pay-1 team=payments×3
  • app=sshd user=root src_ip=203.0.113.9 owner=platform
fig 02 · A pipeline at work: noise dropped, secrets redacted, lines parsed, repeats merged, context added.
01 · Live capture

See what's arriving

  • Tap one source as events come in
  • Up to 60 seconds or 1,000 events
  • Use them as input for your steps
02 · Steps, in order
  1. 1Filterdrop health checks
  2. 2Redactpassword, token
  3. 3ParseJSON in message
  4. 4Deduperepeated errors
  5. 5Lookupadd team from host
03 · Release
  • DraftProduction untouched
  • ReviewA validated snapshot
  • Publish v4Live in Vector
Roll back to v3
Steps ParseRenameRemoveSetRedactMask or hashFilterSampleSplitDedupeCombineRouteLookupVRL
fig 03 · Capture live events, build the steps, publish a version you can roll back.
Live data

Build against what's arriving.

Tap a source for up to 60 seconds or 1,000 events, before your steps run, and use those events as input while you build. Live capture

Releases

Drafts, versions, rollback.

Editing a draft doesn't touch production. Review a validated snapshot, publish it as a new version, and roll back to an earlier one if you need to. Build a pipeline

Less noise

Store what's worth keeping.

Drop health checks, dedupe repeated errors, sample chatty sources and redact secrets before anything reaches disk. Step reference

What you get

The logging platform, without the security homework.

nano
Collect HEC, OTLP/HTTP, JSON over HTTPS, syslog, Kafka, AWS S3/SQS and GCP Pub/Sub. Vector, Fluent Bit, Cribl and the OpenTelemetry Collector all forward to it.
Shape Pipelines clean and reshape events as they arrive, before storage: filter, sample, dedupe, split, redact, mask or hash, rename, route and enrich from lookups.
Parse Catalog parsers for nginx, Apache, systemd-journald, syslog, Kubernetes audit, AWS CloudTrail, ALB, S3 access and VPC Flow logs, GCP audit logs, OpenTelemetry logs and generic JSON. Anything else goes in as Generic JSON or syslog with every field kept, or you write a parser.
Search nPL search on ClickHouse, field stats, saved searches and lookups.
Visualize Dashboards and reports on any search.
Alert Scheduled rules on nPL searches.
Keep On disks you own, for the retention you set.
Pay Open source is free. nano Self-run is per GB/day of ingest, from US$149/month at 5 GB/day. Nothing per seat, host or query.
Why teams move

Priced on what you send.

Pricing

No seats, hosts or queries.

One number decides the price: GB/day of ingest. Add users, servers and searches without a new quote. Pricing

Room to grow

Security when you need it.

The same install runs detections today. nano Self-run adds cases, SOAR, hunts and pivt AI when a security team needs them.

FAQ

Questions we get asked.

Can I use nano just for logs?

Yes. Search, dashboards, saved searches and alert rules work on any logs you send, security or not. The security features stay out of your way until you want them.

Which logs can nano parse?

The catalog has parsers for nginx, Apache, systemd-journald, syslog, Kubernetes audit, AWS CloudTrail, ALB, S3 access and VPC Flow logs, GCP audit logs, OpenTelemetry logs and generic JSON, and it keeps growing. Every install starts with zero log sources, and you choose which parsers to install. For anything else, use Generic JSON or Generic syslog, or write your own parser.

What happens to logs without a parser?

Send them as Generic JSON or Generic syslog. nano stores them and keeps every field that doesn't map under unmapped, plus the original line in raw_data, so you can still search them by field.

Can I clean or change logs before they're stored?

Yes. Every log source has a pipeline: ordered steps that run as events arrive, before they're parsed and stored. Filter out noise, sample, dedupe, split, redact or hash fields, rename, route, and enrich from lookups, or write a step in VRL. Capture live events to build against, and publish each change as a version you can roll back. Pipelines are in both editions; pivt's suggested changes need nano Self-run.

Can I keep my existing HEC senders?

Yes. nano receives the HTTP Event Collector protocol, including the event, raw and acknowledgement endpoints, with a per-source ingest token. Point your HEC clients at nano and change the token.

How is it priced?

The open-source edition is free on one server. nano Self-run is licensed per GB/day of ingest, from US$149/month at 5 GB/day, with every feature at every size. There's no charge per seat, host or query.

How fast is search?

In our published benchmark at 100 GB/day, search p95 stayed between 253 and 318 ms on a small cluster while analysts, detections and dashboards all ran at once. The raw results are published with the benchmark.

Do I need Kubernetes?

No. nano installs with Docker Compose on one Linux server. nano Self-run adds high availability across several servers and Kubernetes when you need them.

Where do my logs go?

Nowhere but your own infrastructure. nano runs on your servers or in your cloud account, and log data is never sent to nano.

Sources

Read the details.

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