Regions · Sold worldwide

nano runs wherever you do. Your logs stay there too.

nano is sold worldwide and bought online in US dollars. You run it on your own servers, in your own account in any cloud region, on Kubernetes with Helm, or air-gapped. Your logs never leave your environment, so where you are doesn't change the product: every license includes every feature, and only your daily volume and support level change the price.

Buy nano
See pricing
One product, any region

Your environment, wherever it is.

Each install is yours: on your hardware or in your cloud account, in the region you pick. nano, LLC sits outside all of them and never receives log data.

nano, LLC · the vendor
  • Connected A daily license check-in and one number per day: total GB ingested. Content and feed downloads.
  • Air-gapped Nothing at all. Offline license, content imported by hand.
Every connection an install makes
fig 01 · Ten regions, one product. Pick a region to jump to its notes.
Regional guides

Full guides for nine regions, from Australia to the Middle East.

Longer guides, with the local rules for security logs, primary sources and an FAQ.

Regional guide · Australia

Data sovereignty for security logs in Australia

Residency vs sovereignty, the PSPF, SOCI and CPS 234 reporting clocks, and buying through our Australian partner Threatbear.

Read
Regional guide · Europe

Digital sovereignty and the CLOUD Act

Why logs that never reach a US vendor change the sovereignty and GDPR questions, plus NIS2, DORA and the Cyber Resilience Act.

Read
Regional guide · India

Security logs that stay in India

CERT-In's 180-day logs and 6-hour reporting, the DPDP Rules, RBI, SEBI and IRDAI, and where to run nano in India.

Read
Regional guide · United States

Security logs inside your own boundary

CMMC and NIST SP 800-171, CJIS, HIPAA, NYDFS, the FTC Safeguards Rule, SEC and M-26-14, and where self-hosting changes your scope.

Read
Regional guide · United Kingdom

Control and evidence for UK security logs

NCSC CAF objective C outcome by outcome, the Cyber Security and Resilience Bill, the NHS DSPT and UK GDPR transfers.

Read
Regional guide · Canada

Canadian security logs, under Canadian control

Bill C-8 and the CCSPA, OSFI B-13, Quebec Law 25 and Protected B, and a US vendor that never holds your logs.

Read
Regional guide · New Zealand

Security logs for New Zealand agencies

NZISM event logging, the Cloud First RESTRICTED boundary and the Privacy Act 2020, and where to run nano in New Zealand.

Read
Regional guide · Singapore

Security logs for CII owners and financial institutions

The CSA Code of Practice's 12-month log rule, MAS TRM logging and the PDPA, and where to run nano in Singapore.

Read
Regional guide · Middle East

Security logs in Saudi Arabia and the UAE

NCA ECC 2-12 and its 12-month floor, SAMA's SIEM expectations, and the CBUAE's in-country rule for banks.

Read
More regions

Where you deploy, and the rules worth knowing.

A short note per region: where you can run nano, and the logging or residency rules buyers there ask about, as of November 2026.

US

United States

There is no US law on where security logs must live. What matters is keeping the logs, and the CUI, CJI or PHI inside them, in your own environment: out of a vendor's SaaS, out of your assessment scope and out of your vendor chains. nano never receives your logs, and nano has no standing access to your install.

Deploy in

Your own account in any US region of AWS, Azure or Google Cloud (including AWS GovCloud (US) or Azure Government), your own servers, Kubernetes, or an air-gapped network.

Rules to know
  • CMMC and NIST SP 800-171. Log files a security tool ingests are Security Protection Data (32 CFR 170.4), and an outside provider that stores them comes into your assessment scope as an External Service Provider. eCFR ↗
  • CJIS Security Policy v6.1. Weekly audit review, at least one year of retention, and fingerprint-based checks for anyone with access to unencrypted CJI, vendor staff included. FBI ↗
  • HIPAA, 45 CFR 164.312(b). Audit controls that record and examine activity in systems with ePHI. The Security Rule sets no log retention period; six years is for documentation. eCFR ↗
Read the US guide
UK

United Kingdom

No UK law requires security logs to stay in the UK, so the question is control and evidence rather than residency. With nano, the log store sits inside your own boundary, under your own access controls, and no third-party SIEM provider holds a copy.

Deploy in

Your own account in an AWS, Azure or Google Cloud region in the UK (AWS London, Azure UK South or Google Cloud London), your own servers, Kubernetes, or an air-gapped network.

Rules to know
  • NCSC Cyber Assessment Framework, objective C. Principle C1 (security monitoring) is what regulators assess NIS operators against; the NHS uses it through the CAF-aligned DSPT. NCSC ↗
  • Cyber Security and Resilience Bill. Not yet law as of November 2026. As proposed: an initial incident notification within 24 hours and a full report within 72 hours, with MSPs and data centers brought into scope. GOV.UK ↗
Read the UK guide
Canada

Canada

nano is a US company, so the answer is the architecture: you run nano in your own environment, and nano never receives or holds your logs. Your logs stay in the Canadian region or data center you choose.

Deploy in

Your own account in an AWS, Azure or Google Cloud region in Canada (AWS ca-central-1 or ca-west-1, Azure Canada Central or Canada East, Google Cloud Montréal or Toronto), your own servers, or an air-gapped network.

Rules to know
  • Critical Cyber Systems Protection Act (Bill C-8). Royal Assent June 2026, not yet in force. Once in force, designated operators must keep records in Canada (s.30(2)) and report incidents within a period set by regulation, not to exceed 72 hours. Justice Laws ↗
  • OSFI Guideline B-13. Expects federally regulated financial institutions to log security events continuously and to set minimum log retention periods. It does not set a length. OSFI ↗
Read the Canada guide
India

India

CERT-In's 2022 Directions ask organizations to keep logs of all their ICT systems within the Indian jurisdiction. Running nano in your own Indian cloud region or data center keeps those logs in India, under your control, which removes the jurisdiction question.

Deploy in

Your own account in an AWS, Azure or Google Cloud region in India (for example AWS Mumbai or Hyderabad, Azure Central India, Google Cloud Mumbai or Delhi), or your own data center.

Rules to know
  • CERT-In Directions (April 2022). Enable logs of all ICT systems, keep them securely for a rolling 180 days within the Indian jurisdiction, produce them to CERT-In on request, and report listed incidents within 6 hours. CERT-In ↗
  • DPDP Rules 2025. From 13 May 2027, data fiduciaries keep logs of personal-data processing for at least one year and report breaches to the Board within 72 hours. eGazette ↗
Read the India guide
New Zealand

New Zealand

For government agencies, the NZISM sets the logging rules, and Cloud First policy keeps data classified above RESTRICTED out of public cloud. A SIEM you run on your own servers, or air-gapped, fits there. Our partner Threatbear covers Australia; in New Zealand you buy from nano directly.

Deploy in

Your own servers or an air-gapped network in New Zealand, or your own account in AWS Asia Pacific (New Zealand) or Azure New Zealand North.

Rules to know
  • NZISM, section 16.6. Agencies must archive event logs and protect them from modification and unauthorized access; the NZISM recommends keeping DNS, proxy and event logs for at least 12 months. GCSB ↗
  • Cloud First and jurisdictional risk guidance. Public cloud only for data classified RESTRICTED and below. digital.govt.nz ↗
Read the New Zealand guide
Singapore

Singapore

Owners of critical information infrastructure (CII) have a binding 12-month log retention rule. nano keeps those logs on storage you own, for the retention you set, and nano never holds a copy.

Deploy in

Your own account in an AWS, Azure or Google Cloud region in Singapore (AWS ap-southeast-1, Azure Southeast Asia or Google Cloud asia-southeast1), or your own data center.

Rules to know
  • Cybersecurity Code of Practice for CII (2026). In effect from 29 July 2026. CII owners keep logs protected against unauthorized access, modification and deletion, and stored for at least 12 months. CSA ↗
  • MAS Technology Risk Management Guidelines. Ask financial institutions to collect, review and retain system logs and protect them from unauthorized access. They set no retention period. MAS ↗
Read the Singapore guide
Middle East

Middle East: Saudi Arabia and UAE

In Saudi Arabia, the NCA's controls name SIEM directly and set a 12-month floor for event logs. In the UAE, banks keep their confidential data in the country. With nano, your logs stay in the environment you run.

Deploy in

Your own data center, or your own cloud account in Google Cloud Dammam (Saudi Arabia), AWS Middle East (UAE) or Azure UAE North.

Rules to know
  • NCA Essential Cybersecurity Controls (ECC-2:2024), 2-12-3. Saudi government entities and critical national infrastructure operators: SIEM-based monitoring, and cybersecurity event logs kept for at least 12 months. NCA ↗
  • CBUAE Outsourcing Regulation, Article 6. UAE banks keep their Master System of Record, including all confidential data, stored within the UAE. CBUAE ↗
Read the Middle East guide
Anywhere

Everywhere else

nano is sold the same way everywhere: online, in US dollars, with every feature in every license. If your country or sector has rules about where security logs live, running nano in your own environment means you decide where they are and who can reach them. If you need help working through procurement, email us.

Deploy in

Any cloud region your provider offers, your own servers anywhere, Kubernetes with Helm, or air-gapped.

Buying from anywhere

Buy online. Talk to us when you need paperwork.

nano, LLC is a US company. It sells directly, worldwide, with list prices in US dollars.

Online · US$

From US$149/month.

Licensed per GB/day of ingest: US$149/month at 5 GB/day and US$279/month at 10 GB/day, list price. Pay monthly by card, or annually by card or invoice. See pricing

Same product everywhere

Every feature, every license.

There are no regional editions and no feature tiers. Air-gapped operation is included with every license, if your environment requires it. Air-gapped deployment

Partners and procurement

Order forms, partners, questions.

Buying through procurement, want to resell or deliver nano, or need a vendor questionnaire answered? Email sales@nano.rs. In Australia, you can also buy through our partner Threatbear.

Wherever you are. Your logs stay with you.

Buy online in US dollars from US$149/month at 5 GB/day. License, updates and business-hours support for the nano software. You run the infrastructure.

Buy nano See pricing

Partners and procurement: sales@nano.rs