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.8

Service Level Agreement

Effective: November 10, 2026 · Version 1.8 (last updated November 14, 2026). Version 1.8 (November 14, 2026) shortens the nano Self-run Sev 1 response target in Section 11.3 from 2 business days to 1 business day. Because it only improves a target, it applies from the date it was posted to everyone on version 1.7, and the version 1.7 changes below otherwise take effect as stated. Version 1.7 narrows what nano Self-run support covers (Section 11.2), makes support asynchronous and sets out the support channels and screen-shares (Sections 2 and 11.2), and lengthens the nano Self-run response targets (Section 11.3). The response targets for nano Hosted and for Partners (Sections 3 and 10.3) are unchanged. Those changes take effect immediately for anyone who accepts the updated Terms of Service, either in the in-app prompt or at nano Self-run checkout, and for everyone else on December 10, 2026, 30 days after version 1.7 was posted. Until then, the version 1.6.1 text continues to apply. Version 1.6.1 uses US spelling ("license"), with no substantive change. Version 1.6 aligns the supported Self-run topologies in Section 11.2 with version 1.2 of the nano Self-run Addendum and applies to everyone from the date it was posted, because it only widens what nano supports. The changes made in version 1.5 take effect immediately for anyone who accepts the updated Terms of Service, either in the in-app prompt or at nano Self-run checkout, and for everyone else on December 9, 2026, 30 days after version 1.5 was posted.

This Service Level Agreement ("SLA") describes the availability targets, support channels, and response time commitments for the nano SIEM platform ("Service").

Which sections apply. Sections 1, 4, 5 and 6 describe services that nano operates and apply to nano Hosted only. For nano Self-run, where you run the software on infrastructure you control, nano makes no availability commitment, and the support terms in Section 11 apply.

1. Platform Availability (nano Hosted)

We target 99% monthly uptime for the Nano platform, measured as the percentage of minutes in a calendar month during which the Service is available.

Availability is calculated as:

(Total minutes in month - Downtime minutes) / Total minutes in month × 100

Exclusions

The following are not counted as downtime:

  • Scheduled maintenance — announced at least 24 hours in advance via email or in-app notification, typically performed during low-usage hours (weekends, early morning UTC).
  • Third-party outages — downtime caused by cloud infrastructure providers, DNS providers, or other upstream services outside our control.
  • Force majeure — natural disasters, government actions, or other events beyond reasonable control.
  • Customer-caused issues — misconfigured log sources, exceeded plan limits, or actions taken by the customer that impact their own service.

2. Support Channels

Support is asynchronous. Open a support request in one of these channels:

Channel Use Response target
Support request on app.nano.rs Support requests (Report an issue, when logged in) Section 3, or Section 11.3 for nano Self-run
Email Support requests to Section 3, or Section 11.3 for nano Self-run
Feedback portal Feature requests and feedback (in-app, when logged in) None
Discord Community help from other users and the nano team None
Status page Platform status and incident updates for nano-operated services Section 4

A response target runs from when nano receives a support request in the app or by email. Discord is community help only: it is not a support channel and carries no response target.

nano does not provide phone support, on-call support, 24×7 coverage or shared chat channels, except as this SLA states for the Dedicated support level (Section 3) and for Partners (Section 10.4), or as an Order Form provides. A screen-share is offered at nano's discretion. It is scheduled in advance and limited to an agreed length of time.

3. Support Response Times

Response times are measured from when a support request is received to when a member of the nano team first responds to it. A response target is a time to first human response. It is not a time to resolution. Each plan maps to a support level:

  • Standard — self-serve hosted plans, at any committed size
  • Self-run — nano Self-run subscriptions, as set out in Section 11
  • Dedicated — Enterprise. An Order Form may improve on these terms but never reduces them below this level.
  • Priority — every tenant of an MSSP partner (see Section 10)

Human response targets are measured against the coverage window for your support level — unless otherwise agreed in an Order Form, business hours (Monday–Friday, 9am–6pm ET, excluding US federal holidays); time outside the coverage window does not accrue toward a target.

Severity Description Standard Priority Dedicated
Sev 1 — Service down Platform unreachable or data ingestion fully stopped 12 hours 4 hours 4 hours
Sev 2 — Major degradation Significant feature unavailable or severe performance issues 24 hours 8 hours 8 hours
Sev 3 — Minor issue Non-critical bug, UI issue, or general question 48 hours 24 hours 2 business days
Sev 4 — Feature request Enhancement suggestions or feedback Feedback portal Feedback portal Feedback portal

An Order Form may improve these targets.

Dedicated Support (Enterprise)

On the Dedicated support level, in addition to the human response targets in the table above:

  • Automated AI triage acknowledgment within 15 minutes, 24/7. Every support request, at every severity, receives an automated acknowledgment and triage — severity classification and a diagnostic summary produced by our AI triage — within 15 minutes, at any hour, including outside the coverage window. This 15-minute commitment covers the automated acknowledgment and triage only; it is not a human response.
  • Automatic escalation to on-call engineers for Sev 1 and Sev 2. A request triaged as Sev 1 or Sev 2 is escalated automatically to our on-call engineers at any hour.
  • Human response targets are those in the Dedicated column above, measured against the coverage window, unless the Order Form or the extended coverage add-on below provides better terms.

Extended Coverage (Add-On)

For Enterprise customers on the Dedicated support level, extended coverage is available as a paid add-on and, where purchased, is stated in the Order Form: a wider coverage window (for example, extended regional hours) and 24/7 paged Sev 1 response, with a 4-hour human target inside the coverage window and 8 hours outside it.

Severity Classification

nano sets the severity of each support request using the descriptions in this SLA, and may adjust it as it learns more about the cause and impact. If you believe a severity should be escalated, note this in your support request and we will review promptly.

4. Incident Communication

When we identify a platform incident:

  • Within 1 hour — Initial acknowledgment posted to our status page.
  • Every 2 hours — Progress updates during active incidents.
  • Within 24 hours of resolution — Post-incident summary describing root cause, impact, and preventive measures.

For Sev 1 incidents, we will additionally send email notifications to affected customers on every support level (Standard, Priority, and Dedicated).

5. Data Durability (nano Hosted)

  • Log data is stored redundantly and encrypted at rest. On high-availability deployments each unit of data is held in more than one copy on separate infrastructure; on Enterprise deployments on AWS those copies sit in separate availability zones.
  • Retention periods are set by your plan: the retention shown for your self-serve plan, or the retention in your Order Form.
  • Redundancy protects against infrastructure failure — a lost node, disk, or availability zone — and we rebuild the affected copy from its peer.
  • Redundancy does not protect against deletion or corruption of the data itself, which applies to every copy. We do not take backups of log data and do not offer point-in-time restore of it. Tiering to object storage moves data rather than copying it, so it is not a second copy either. Where log data is destroyed, recovery is by re-ingestion from your own source systems.
  • The relational database holding your configuration, rules, and alerts is backed up daily with a rolling 7-day retention.
  • On customer-hosted (BYOC) deployments the storage lives in your cloud account, so you may apply your own snapshot and backup policy to it and restore independently of us.
  • On nano Self-run, nano holds no copy of your data and takes no backups of it, including of the relational database. Backup, restore, replication and retention are yours to configure.

6. Planned Maintenance

  • Maintenance windows are scheduled during low-traffic periods when possible.
  • We provide at least 24 hours advance notice for planned maintenance.
  • Emergency maintenance (security patches, critical fixes) may occur with shorter notice.

7. What This SLA Does Not Cover

This SLA describes our operational targets and support commitments. It does not constitute a guarantee of specific performance levels or include financial remedies (service credits) unless otherwise agreed in an Order Form or master agreement.

8. Changes to This SLA

We may update this SLA from time to time. Material changes will be communicated via email or in-app notification at least 30 days before they take effect. A modified version takes effect earlier for you if you accept it earlier, for example by accepting updated Terms of Service in the app or at checkout.

9. Contact

For support inquiries: For SLA-related questions:

10. Partners (MSSP)

This section applies to managed security service providers that have accepted the Nano Partner Agreement ("Partners") and to the tenants they run for their own customers ("End Customers"). Where it differs from the rest of this SLA, this section governs for Partners.

10.1 Support Model

  • First line: the Partner. The Partner supports its End Customers: onboarding, user questions, data source setup, detection tuning and triage.
  • Second line: Nano. We support the Partner. Support requests come from Partner staff (members of the Partner's organization), not from End Customers. If an End Customer contacts us directly, we refer them to their Partner, unless the Partner asks us to join a case.

10.2 Support Level and Tenant Mapping

Partners receive the Priority support level in Section 3. Every tenant a Partner runs gets the Partner's support level, regardless of the tenant's committed size or the plan it would otherwise map to.

10.3 Response Targets and Hours

Partner requests use the Priority targets in Section 3, measured against the business-hours coverage window in Section 3 (Monday–Friday, 9am–6pm ET, excluding US federal holidays):

Severity Partner
Sev 1 — Service down 4 hours
Sev 2 — Major degradation 8 hours
Sev 3 — Minor issue 24 hours
Sev 4 — Feature request Feedback portal

Severity is classified as described in Section 3.

10.4 Contact Channel

Partner staff contact us at , naming the affected tenant or tenants. Partners also have a shared Slack channel with us for partner staff. Slack is for coordination; open Sev 1 and Sev 2 requests through , because the response target is measured from when that request is received. Platform incidents are posted to the status page, and Sev 1 email notifications under Section 4 go to the Partner. The Partner informs its End Customers.

Partners do not receive the Dedicated level's 24/7 automated AI triage, which is for Enterprise customers.

10.5 Availability

Each Partner tenant has the availability target, measurement and exclusions in Section 1. For Partner tenants, "customer-caused issues" includes the actions of the Partner and of its End Customers.

10.6 Service Credits

As stated in Section 7, this SLA does not provide service credits unless they are agreed in writing. Where credits are agreed for a Partner, they are applied to the Partner's monthly partner invoice. They are never paid or credited to End Customers; whether to pass a credit on is a matter for the Partner's own contract with its End Customer.

11. nano Self-run

This section applies to nano Self-run subscriptions, together with the nano Self-run Addendum. Where it differs from the rest of this SLA, this section governs for nano Self-run.

11.1 No Availability Commitment

You operate the deployment, so its availability depends on infrastructure, networks and operations that nano does not control. nano makes no uptime commitment for a Self-run deployment, and Sections 1, 4, 5 and 6 do not apply to it. The status page covers nano-operated services, such as license check-in at app.nano.rs, the release registry and content feeds.

11.2 What Support Covers

Support covers the nano software in a Supported Configuration, as defined in the Addendum: a supported version (the current release line and the one before it), a supported topology (a single node, a multi-node deployment of any size built with the nano installer and sized per the documentation, or the nano Helm chart), the documented minimum requirements, and unmodified software. Support is limited to:

  • using the documented installer, Helm chart and upgrade procedures;
  • licensing;
  • configuring the nano software; and
  • diagnosing and fixing defects in the nano software.

Support does not include administering or troubleshooting Your Environment, as defined in the Addendum, even when Your Environment is what prevents an install or upgrade from completing. That includes your hardware, operating systems and their patching, container runtime, Docker networking, Kubernetes, storage and disk mounts, network, firewalls, proxies, DNS, TLS certificates, identity provider, backups, cloud accounts, AI provider, and recovery of data. When 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, at nano's discretion.

For a configuration that is not a Supported Configuration, nano makes reasonable efforts with no response target and may ask you to upgrade or move to a supported topology first.

Support is asynchronous, through the channels in Section 2. nano does not provide phone support, on-call support, 24×7 coverage or shared chat channels for nano Self-run unless an Order Form says otherwise. nano does not receive remote access to your deployment. Support works from the logs and diagnostic bundles you choose to provide. A screen-share is offered at nano's discretion; it is scheduled in advance, limited to an agreed length of time, and run by you.

11.3 Response Targets

Response targets apply only to a deployment in a Supported Configuration. They are measured against the business-hours coverage window in Section 3, unless an Order Form states otherwise. An Order Form may improve them.

Severity Description Self-run
Sev 1 — Production down A production deployment in a Supported Configuration cannot ingest or search, with no workaround, and the cause is in the nano software 1 business day
Sev 2 — Major degradation A significant feature is unavailable or severely degraded in a Supported Configuration 3 business days
Sev 3 — Minor issue A non-critical defect, a question, or help with the documented install, upgrade or licensing procedures 5 business days
Sev 4 — Feature request Enhancement suggestions or feedback Feedback portal

A response target is a time to first human response. It is not a time to resolution. nano sets the severity of each request using the descriptions above, as described in Section 3, and may lower it when the cause turns out to be in Your Environment.

11.4 Updates and Security Advisories

nano publishes signed releases and notifies your account contacts of new releases and of security advisories rated High or Critical. You decide when to apply them. Fixes are made in supported versions only.

11.5 No Service Credits

As stated in Section 7, this SLA does not provide service credits unless they are agreed in writing in an Order Form.

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