Tenzir gives security teams a programmable control point before storage: collect, parse, enrich, reduce, and route each stream. The security-ready path becomes OCSF before it reaches nano, so source-specific transformation stays upstream of the SIEM.
The open-core ocsf+tenzir profile bundles Tenzir 6.6.0 and writes OCSF directly into nano's ClickHouse OCSF store over the native protocol. nano turns those records into search, detections, investigations, and cases.
fig 01 · Tenzir pipelines feeding nano's ClickHouse in real time.
Tenzir owns everything upstream of storage: collection, parsing, OCSF normalization, in-stream enrichment, volume reduction, and routing. nano accepts OCSF first and owns search, detections, alert queues, triage, and cases. The two compose through one direct ClickHouse write.
On Tenzir 6.6.0 and newer, to_clickhouse sends event and source_type straight into nanosiem.ocsf_logs_raw. nano's materialized-view chain derives the searchable OCSF record in nanosiem.ocsf_logs.
fig 02 · One path. Source-specific parsing stays out of the database; ClickHouse stays fast.
Tenzir controls which telemetry enters nano. nano is licensed per GB/day of ingest, so reducing volume upstream in Tenzir lowers the nano license you need. Both run inside your environment: Tenzir writes directly to your nano ClickHouse, and nothing passes through nano. About nano
Tenzir deduplicates, filters, reduces, and routes upstream. Send the security-relevant OCSF stream to nano and direct other streams wherever your policy requires.
nano is priced per GB/day of ingest on a continuous curve, with nothing per seat, endpoint or query. Reducing average GB/day upstream lowers the license you need downstream.
Choose the open-core ocsf+tenzir profile to start a bundled Tenzir 6.6.0 node with the direct ClickHouse sink already wired to nano's OCSF store.
Because Tenzir keeps the data model stable upstream, nano's searches and detections operate on consistent OCSF fields even when source formats differ. Risk, evidence, and entity context stay connected to the same stored record.
OCSF-first storage means the normalized record Tenzir writes is the record nano searches, detects on, and carries into an investigation.
Read the full solution brief →Start the open-core ocsf+tenzir profile, map one source to OCSF, and write it directly into nano's ClickHouse store with Tenzir 6.6.0 or newer.
open-core ocsf+tenzir profile · Tenzir ≥ 6.6.0 · direct ClickHouse write · OCSF-first storage