nano SIEM
Getting Started

Custom multi-node layouts

Supported in:Self-hosted

Split nano Self-run across Linux servers in a layout other than the standard three-node HA design, with a reviewed inventory.

Most multi-server installs should use the standard three-node layout in High availability. For more ingest servers, more ClickHouse shards or replicas, or dedicated Keepers, see Scaling past three nodes first. Use this page for any other split, such as a separate server for PostgreSQL.

What you can change

nano runs as five roles. Each server in your inventory runs one or more of them:

RoleWhat it runsHow many
appUI, API, search, detections, jobsOne or more. Two or more for failover (v2.0.7 and later)
postgresPostgreSQL (rules, alerts, cases, users)One, or three for automatic failover (v2.0.7 and later). Two also work with three Keeper servers as the tie-breaker
clickhouseEvent storageOne per shard and replica
keeperClickHouse coordinationThree with replicas or several shards, otherwise one
ingestVector and the ingest frontendOne or more

Before you start

Contact support with your deployment ID and intended layout. nano reviews the inventory with you before the first install, because server identities and roles can't change afterwards without a data migration.

Size each server from Server sizing. Every server that runs clickhouse or keeper needs a supported CPU; see The installer refuses the CPU. Get the bundle as in Get the bundle.

Install

The steps are the same as for High availability, with your own inventory:

  1. Set the host firewall rules on every server.
  2. Unpack the bundle on every server and log in to the registry.
  3. Install the reviewed inventory to /etc/nano/inventory.yaml and stage the private certificate on every server.
  4. Prepare on the app server and add your license values to .env. For a large install, also add your planned volume; see Prepare on nano-1.
  5. Copy .env to every other server. After any later installer run that changes .env (the first app server, or the postgres server that prints "The shared .env changed"), copy that server's .env everywhere again; see Copy .env to the other servers.
  6. Start the data roles first (postgres, keeper, clickhouse), then app, then ingest.

Each run names the server and its complete role list from the inventory:

NANO_HOST_NAME=<server name> ./install.sh --role <its roles> --inventory /etc/nano/inventory.yaml

Prefer to have a coding agent run the install? See Deploy with your AI agent.

Vector native (port 6000)

From v2.0.30, every ingest server accepts Vector's native protocol on port 6000 with mutual TLS only. Issue, renew and revoke sender certificates on the first app server, then copy .env to every server and update every ingest server. A revoke isn't effective on an ingest server until you update it. See Vector native for the steps, the firewall rules and the trade-offs.

Reference

The bundle includes the full inventory reference at docs/getting-started/self-hosting-multi-node.md. It covers every inventory field, private TLS, custom ports and bind addresses, several ingest servers and two-shard layouts. The firewall rules are on this site, in Host firewall.

On this page