nano
Product
Overview: the self-hosted SIEMWhat it sends to nanoInstall with your coding agentFeaturesSOAR: response automationpivt AI on your own modelHunts: automated threat huntingLog managementOpenTelemetry (OTLP)Benchmarkspivt desktopOpen source
Compliance
All regulations
Australia Essential EightISM loggingIRAPSOCI ActCPS 234PSPF
Europe NIS2DORACyber Resilience ActGDPR
India CERT-InDPDP RulesSEBI CSCRFRBI and IRDAI
United States CMMCCJISHIPAANYDFS and financial services
United Kingdom NCSC CAF
Global frameworks PCI DSSSOC 2ISO 27001
Regions
Regional guides AustraliaEuropeIndiaUnited StatesUnited KingdomCanadaNew ZealandSingaporeMiddle East
More regions Switzerland
All regions: sold worldwide
Compare
SplunkSplunk Enterprise SecurityMicrosoft SentinelGoogle SecOpsCrowdStrike Next-Gen SIEMCortex XSIAM
Elastic SecurityIBM QRadarExabeam and LogRhythmSumo LogicGraylogWazuhOpen source SIEM
All comparisons
Pricing
Resources
DocsBlogChangelogWhat is a SIEM?Data flowsTrust & security
Sign in Buy nano
Effective 2026-11-10 · v1.4

nano Self-run Addendum

Effective: November 10, 2026 · Version 1.4 (last updated November 10, 2026). Version 1.4 narrows what support covers for a Self-run Deployment, states that support is asynchronous, and sets out when nano offers screen-shares and paid professional services (Section 5). It also corrects the cross-reference in Section 2(e). Those changes take effect immediately for anyone who accepts this Addendum at nano Self-run checkout, and for everyone else on December 10, 2026, 30 days after version 1.4 was posted. Until then, the version 1.3 text of Section 5 continues to apply. Version 1.3 corrects spelling to US English ("license" for "licence", including the defined term License Metadata), with no change in meaning. It also states in Section 6.1 that each Self-run license covers up to two (2) installs, and aligns the last sentence of Section 6.2 with it. Because that only clarifies and widens what you may run, it applies to everyone from the date it was posted. Version 1.3 also adds the install identifier to License Metadata (Sections 1, 6.2 and 10). That change takes effect immediately for anyone who accepts this Addendum at nano Self-run checkout, and for everyone else on December 10, 2026, 30 days after version 1.3 was posted. Until then, the version 1.2 text on License Metadata continues to apply. Version 1.2 widened the topologies in the definition of Supported Configuration (Section 1) to include multi-node deployments of any size. Because it only widens what nano supports, it applies to everyone from the date it was posted. Version 1.1 added the daily usage report to License Metadata (Sections 1, 6.2 and 10) and Section 6.4(b). Those changes take effect immediately for anyone who accepts this Addendum at nano Self-run checkout, and for everyone else on December 9, 2026, 30 days after version 1.1 was posted; for a prepaid annual term, Section 6.4(b) applies from your next renewal unless you accept it earlier. Until then, the version 1.0 text of those Sections continues to apply.

This nano Self-run Addendum ("Addendum") applies when you buy nano Self-run, whether online or under an Order Form. It forms part of, and is governed by, the agreement under which you bought it: the Terms of Service for an online purchase, or the Master Services Agreement and the Order Form for a sales-led purchase (in each case, the "Agreement"). nano, LLC ("nano", "we", "us") and the customer named at purchase ("Customer", "you") agree as follows. Where this Addendum conflicts with the Agreement on a Self-run Deployment, this Addendum governs. It does not apply to nano Hosted.

1. Definitions

  • Self-run Deployment — an installation of the Software (an "install") that you run on hardware, cloud accounts, networks and operating environments that you own or control, and to which nano has no operational access. A deployment in your own cloud account to which nano has been granted operational access under an Order Form is a BYOC Deployment under the Master Services Agreement, not a Self-run Deployment.
  • Software — the commercial nano software that nano makes available for a Self-run Deployment: signed release bundles, container images, Helm charts, deployment tooling, license files, detection and parser content, and every update to them, including the Open Source Components incorporated into them.
  • Your Environment — everything on which a Self-run Deployment runs or depends other than the Software itself: hardware, virtualization, operating systems, container runtimes, Kubernetes, storage, backups, networks, firewalls, proxies, DNS, certificates, identity providers, log sources, and any AI provider or model you configure.
  • Licensed Capacity — the daily ingest volume in GB/day stated at purchase or on the Order Form.
  • Daily Ingest — the volume of data the Software receives for indexing in one UTC calendar day, as recorded by the Software's own usage counters (before compression).
  • Supported Version — the current release line of the Software and the release line immediately before it (N-1), as listed in the Documentation, in each case at its latest patch release and released within the previous twelve (12) months.
  • Supported Configuration — a Self-run Deployment that (a) runs a Supported Version, (b) uses a topology the Documentation supports for Self-run: a single node; a multi-node deployment of any size built with the nano installer (for example three-node high availability, or more ingest, ClickHouse and Keeper hosts as you scale), sized per the Documentation; or the nano Helm chart on Kubernetes; (c) meets the documented minimum requirements for its Licensed Capacity, and (d) runs the Software unmodified, other than through the configuration, detection content, parsers, dashboards and integrations the Documentation provides for.
  • Customer Data — the log, event, alert, case, configuration and other data processed or stored by a Self-run Deployment, and any output derived from it.
  • License Metadata — the data the Software sends to nano to check its license and measure capacity: the deployment identifier, the install identifier (a random identifier generated by each installation), the license token, the Software version, the time of the check-in, the network address it comes from, and the daily usage report described in Section 6.2.

2. What nano provides

For the term of your subscription, nano will:

a. make the Software available for download as signed release bundles and through a customer image registry, with checksums and signatures you can verify; b. issue license entitlements for your Licensed Capacity, either by online check-in or as a signed offline license file; c. publish updates, including security updates, with release notes, and notify the contacts on your account when a new release or a security advisory is published; d. publish Documentation for installing, upgrading, sizing, backing up and operating the supported topologies; and e. provide support for Supported Configurations as described in Section 5 of this Addendum and Section 11 of the Service Level Agreement.

nano does not install, host, operate, monitor, back up, upgrade or administer a Self-run Deployment, and does not provide a managed security service.

3. Shared responsibility

You run the Self-run Deployment. You are solely responsible for Your Environment and for how the Software is operated in it, including:

a. Infrastructure and capacity: providing and sizing hardware, storage, network and cloud resources for your Licensed Capacity and retention, and for monitoring their health; b. Security: securing Your Environment and access to it, including operating system and runtime patching, network exposure, TLS certificates, secrets, the credentials of your users, identity provider configuration, and access to the registry credentials and license files nano issues to you; c. Updates: deciding when to apply updates, applying them, and testing them in your environment; d. Availability: high availability, failover and disaster recovery, including whether to run replicas; e. Backups and retention: backing up Customer Data and configuration, testing restores, and setting retention. nano holds no copy of Customer Data and cannot restore it; f. Data and log sources: the completeness, accuracy, legality and timeliness of the data you send to the Software, and the configuration of your log sources; g. Detection and response: which detection content you enable, tune and maintain, and how you triage and respond to what the Software reports; and h. Third parties: your agreements with, and the conduct of, your infrastructure, cloud, network and AI providers.

nano is not responsible for, and has no liability for, any outage, degradation, data loss or corruption, security incident, missed detection or cost that is caused by Your Environment, by a configuration that is not a Supported Configuration, by your delay in applying an update, or by any other matter in this Section 3.

4. Updates and security fixes

4.1 Notice, not application. nano will make security fixes for Supported Versions available as updates and will publish an advisory for each vulnerability it fixes that it rates High or Critical. Applying an update is your decision and your responsibility, and you choose its timing at your own risk.

4.2 Unapplied updates. nano is not responsible for any loss or security incident to the extent it would have been prevented by an update, or a documented mitigation, that nano made available to you at least thirty (30) days earlier, or at least seven (7) days earlier for an update nano identified as fixing a Critical vulnerability.

4.3 Verifying what you install. Install only Software obtained from nano's distribution channels and verify the signatures and checksums nano publishes. nano has no responsibility for Software obtained from anywhere else, or that has been altered after nano published it.

4.4 No obligation to backport. nano fixes defects and vulnerabilities in Supported Versions only. A fix for an older version is at nano's discretion.

5. Support boundary

5.1 What support covers. Support for a Self-run Deployment covers the Software in a Supported Configuration, and is limited to: (a) using the documented installer, Helm chart and upgrade procedures; (b) licensing; (c) configuring the Software; and (d) diagnosing and fixing defects in the Software.

5.2 What support does not cover. Support does not include administering or troubleshooting Your Environment, even when Your Environment is what prevents an install or upgrade from completing. This includes hardware, operating systems and their patching, container runtimes, Docker networking, Kubernetes, storage and disk mounts, networks, firewalls, proxies, DNS, TLS certificates, identity providers, backups, cloud accounts, Your AI Provider, and recovery of Customer Data. Support also does not cover versions that are not Supported Versions, modified Software, unsupported topologies, or writing custom detection content, parsers or integrations.

5.3 Causes in Your Environment. When nano finds that the cause of a request is in Your Environment, nano will tell you so, point you to the relevant Documentation where it exists, and may close the request. Hands-on help with Your Environment is available only as paid professional services under a separate Order Form, which nano may offer or decline at its discretion.

5.4 Unsupported configurations. nano will make reasonable efforts to answer a request about a configuration that is not supported, but no response target applies, and nano may ask you to move to a Supported Configuration first.

5.5 Channels. Support is asynchronous: you open a support request on app.nano.rs or by email to , and nano responds during the coverage window and against the response targets in Section 11 of the Service Level Agreement. nano does not provide phone support, on-call support, 24×7 coverage or shared chat channels for a Self-run Deployment unless an Order Form says otherwise. nano's community channels, such as Discord, are community help only and carry no response target.

5.6 No access; screen-shares. nano does not receive remote or administrative access to a Self-run Deployment. Support works from information you choose to give us, such as logs and diagnostic bundles. nano may offer a screen-share at its discretion. A screen-share is scheduled in advance, limited to an agreed length of time, and run by you. Remove credentials and personal data you do not want nano to receive. Diagnostic material you send is handled under Section 10.

6. License, check-in and capacity

6.1 License grant. Subject to the Agreement and payment of the fees, nano grants you, for the subscription term, a non-exclusive, non-transferable, non-sublicensable license to install and run the Software in up to two (2) Self-run Deployments for each Self-run license (each subscription is one license), or more if the Order Form allows, and to keep reasonable backup copies, solely for your and your Affiliates' internal security operations up to the Licensed Capacity. Under each license:

(a) one Self-run Deployment may be used for production, and one for development, testing, disaster recovery or backup;

(b) a high-availability cluster, meaning one installation whose hosts share one database, counts as one (1) Self-run Deployment, however many hosts it has;

(c) the Daily Ingest of every Self-run Deployment under the license counts toward that license's Licensed Capacity; and

(d) running more Self-run Deployments than the license covers needs another license. nano may notify you when more Self-run Deployments are checking in under one license than it covers, and nano support can retire a Self-run Deployment you no longer run so that it no longer counts.

6.2 License controls. The Software contains license controls. With online licensing, the Software checks in with app.nano.rs periodically and sends only License Metadata. The daily usage report is one number per completed UTC calendar day: the aggregate volume of Daily Ingest for that day in GB, tied to the deployment identifier, used for capacity and billing (Sections 6.4 and 6.5). From Software version 2.0.10, each check-in and each daily usage report also carries the install identifier, which nano uses to count the Self-run Deployments under each license (Section 6.1). Nothing else about the data you ingest is sent: no content, source names, hosts, IP addresses, users, event types, per-source breakdowns or event rates. With an offline license file, no check-in occurs, nothing is reported automatically, and the file sets the license term; the Software keeps the same daily record locally, and you will provide it to nano on renewal and when nano asks under Section 6.5. You will not disable, bypass, tamper with or emulate the license controls, alter the system clock to extend a license term, or use a license file or token in more Self-run Deployments than Section 6.1 allows.

6.3 Grace and lock. If a subscription payment fails, the Software continues to run for a grace period (currently seven (7) days) before it locks. If an online deployment cannot reach the license service for fourteen (14) consecutive days, it locks until a check-in succeeds. An offline license file stops being valid after its stated term plus its grace period (currently seventy-two (72) hours). When the Software is locked, its user interface and API are unavailable apart from sign-in and license administration. A lock does not delete, encrypt or alter Customer Data, which stays in Your Environment. A lock that results from non-payment, an expired license, a network or proxy configuration in Your Environment, or a breach of this Section 6 is not a breach of the Agreement by nano and does not entitle you to a refund or credit. nano will tell you in the Documentation how to restore a check-in, renew or import a license, and recover from a clock error.

6.4 Capacity. (a) The Software records Daily Ingest and warns as it approaches the Licensed Capacity. It does not stop ingesting above it. If your Daily Ingest, averaged over any thirty (30) consecutive days, exceeds the Licensed Capacity by more than ten percent (10%), nano may notify you, and you will within thirty (30) days either reduce your ingest or move to a Licensed Capacity that covers it, with the higher fees applying from the date of nano's notice, pro-rated for the rest of the current term. There is no other metered overage charge.

(b) If you do neither within that period, nano may (i) move your subscription to the Licensed Capacity tier that covers your average Daily Ingest and invoice the difference from the date of nano's notice, or (ii) after a further fifteen (15) days' written notice, treat the excess as a material breach and suspend or terminate the subscription. Suspension never deletes or alters Customer Data.

6.5 Verification. Once in any twelve (12) month period, on thirty (30) days' written notice (or sooner on reasonable suspicion of a breach of this Section 6), you will give nano a usage report produced by the Software covering the period nano reasonably asks for, and a written statement that you are using the Software only in the authorized installations. For offline licenses this report is the means of verifying capacity. If it shows Daily Ingest above the Licensed Capacity, Section 6.4 applies from the start of the excess period. If it shows an underpayment of more than ten percent (10%), you will also reimburse nano's reasonable costs of the verification. nano will treat these reports as your Confidential Information.

7. AI providers and models

7.1 nano Self-run does not include nano AI credits. AI features work only with a model provider, gateway or self-hosted model that you configure ("Your AI Provider"). Your AI Provider is a third party, or is part of Your Environment, and not a sub-processor of nano.

7.2 When you enable AI features, the Software sends prompts, which may include excerpts of Customer Data, to Your AI Provider and receives its responses. You are responsible for choosing Your AI Provider, for your agreement with it and its terms of use, for what it does with that data (including any training, retention, or location of processing), and for its availability, cost and model behavior.

7.3 AI output is advisory only, as stated in the Agreement. nano does not warrant the accuracy, completeness or suitability of any output from Your AI Provider, and nano has no liability for any act or omission of Your AI Provider.

8. Open source and third-party components

8.1 The Software incorporates Open Source Components, which are governed by their own licenses. nano lists them, with their licenses and any required notices, in the third-party notices it ships with each release. Where an Open Source Component's license conflicts with the Agreement, that license governs that component.

8.2 nano separately publishes the open-source nano engine under the GNU Affero General Public License v3.0 ("AGPL-3.0"). nano owns the copyright in the nano-authored code in that engine (including contributions licensed to nano under its contributor license agreement) and licenses that code to you within the Software under the Agreement, not under the AGPL-3.0. Your use of the Software under the Agreement does not create AGPL-3.0 obligations for you. Nothing in the Agreement limits any right you have under the AGPL-3.0 to the open-source engine when you obtain it from its public repository and use it apart from the Software.

8.3 The commercial modules of the Software are proprietary to nano and are licensed only under the Agreement.

8.4 Data feeds and content that the Software downloads, such as IP geolocation, threat intelligence and community detection content, may be published by third parties under their own terms, which the Documentation identifies. nano does not warrant the accuracy of third-party feeds.

9. No guarantee of detection or security outcome

The Software helps you detect and investigate security events. It does not guarantee that any threat, intrusion, compromise or data loss will be detected, reported or prevented. Detection depends on Your Environment, your data and your configuration. nano has no liability for a security incident, breach or regulatory consequence suffered by you or a third party, whether or not the Software detected or could have detected it, except to the extent the Agreement expressly provides otherwise.

10. Data, privacy and location

10.1 No access. Customer Data stays in Your Environment. nano has no access to it and does not receive it, except: (a) License Metadata; and (b) material you choose to send to nano for support. nano Self-run never routes AI prompts or responses through nano; they go only to Your AI Provider (Section 7).

10.2 Roles. nano does not process Customer Data held in a Self-run Deployment on your behalf, and the Data Processing Agreement applies to a Self-run Deployment only for (i) the account data of your users on app.nano.rs and (ii) personal data in support material you send to nano. nano processes License Metadata to operate licensing, measure capacity and bill for it, count the Self-run Deployments under each license, prevent misuse and send update notices, as described in the Privacy Policy.

10.3 Location. You decide where a Self-run Deployment and Customer Data are located. nano makes no data residency commitment for them and is not responsible for whether that location meets your legal or contractual requirements.

11. Preview features

nano may make features available labeled preview, beta, experimental or similar ("Preview Features"). Preview Features are optional, are provided "as is" without warranty, support targets or indemnity, may change or be withdrawn at any time, and should not be relied on for production detection. nano's total liability arising from Preview Features is limited to one hundred US dollars (US $100).

12. Export control and sanctions

The Software is subject to U.S. export control and sanctions laws. You will not export, re-export, transfer or deploy the Software, or make it available, in an embargoed or comprehensively sanctioned country or region, to a restricted party, or for a prohibited end use. You represent that you are not a restricted party, and are not owned or controlled by one. nano may refuse to issue or renew a license where doing so would breach those laws.

13. Liability

13.1 The limitations and exclusions of liability in the Agreement apply to this Addendum and to every Self-run Deployment. Without limiting them, nano is not liable for: loss, corruption or unavailability of Customer Data; the cost of restoring or re-ingesting it; outages of a Self-run Deployment; or the costs of Your Environment or Your AI Provider.

13.2 nano's total aggregate liability arising out of or related to a Self-run subscription will not exceed the fees paid or payable by you for that subscription in the twelve (12) months before the event giving rise to the liability. This does not limit your obligation to pay fees, or liability that cannot be limited by law.

14. Indemnity

In addition to your obligations under the Agreement, you will defend and indemnify nano against any third-party claim arising from Your Environment, Your AI Provider, a breach of Section 6 or Section 12, or a security incident in a Self-run Deployment, except to the extent the claim is caused by an infringement for which nano indemnifies you under the Agreement.

15. Term, termination and your data

15.1 When a Self-run subscription ends: (a) the license in Section 6.1 ends and the Software locks under Section 6.3; (b) nano will not delete, disable or alter Customer Data or Your Environment; (c) you will stop using the Software and, within thirty (30) days, remove the Software, license files and registry credentials from your systems, and certify this on request; and (d) your Customer Data remains yours.

15.2 Export. Customer Data is held in standard database formats in Your Environment and you can export it with the tools and procedures in the Documentation at any time, including after the Software locks. On request made before your subscription ends, nano will give reasonable guidance on exporting Customer Data.

15.3 Sections 3, 4.2, 6.5 (for the period of use), 7.3, 8, 9, 10, 13, 14 and 15 survive the end of the subscription.

16. Contact

Questions about this Addendum: .

nano

The self-hosted SIEM. Your environment, your logs.

Product

  • Overview
  • Data flows
  • Install with your agent
  • Features
  • SOAR
  • pivt AI
  • Hunts
  • Log management
  • OpenTelemetry
  • Benchmarks
  • pivt desktop
  • Pricing
  • Buying nano
  • Open source
  • Changelog

Compliance

  • Essential Eight
  • ISM logging
  • NIS2
  • DORA
  • CERT-In
  • DPDP Rules
  • CMMC
  • HIPAA
  • All regulations

Compare

  • Splunk
  • Splunk ES
  • Sentinel
  • Google SecOps
  • CrowdStrike
  • Cortex XSIAM
  • Elastic
  • QRadar
  • All comparisons

Regions

  • Australia
  • Europe
  • India
  • United States
  • United Kingdom
  • Canada
  • All regions

For

  • Startups
  • Enterprises
  • Home labs
  • All solutions

Resources

  • Docs
  • Blog
  • What is a SIEM?
  • GitHub
  • Discord

Company

  • About
  • Trust
  • Partners
  • Contact
© 2026 nano, LLC · a US company
Privacy Terms DPA SLA

We use essential cookies to make the site work. No tracking, no ads. Learn more