Your region, your bill, your keys.
Deploy into your own account in an Australian region. The infrastructure is yours: you choose the region, you pay the provider directly, and your existing cloud controls apply to the log store.
nano is a SIEM you run in your own Australian cloud account, your data center or an air-gapped network. Your logs are collected, stored and analyzed there, AI (if you turn it on) calls your own model directly, and none of your log data ever reaches nano.
An Australian region answers the first question. It doesn't answer the second: who runs the system that holds your logs, and which laws can reach them.
| Question | Data residency | Data sovereignty |
|---|---|---|
| What it asks | Where is the data physically stored? | Whose laws can reach the data, and who can access or be compelled to hand it over? |
| nano in your AU cloud account | Yes: in the region you choose. | nano holds no copy and has no standing access to your install. Your cloud provider is the only other party. |
| nano in your data center or air-gapped | Yes: on hardware you own. | No third party holds or operates the log store. Air-gapped, nothing connects to nano at all. |
| A SaaS SIEM in a Sydney region | Yes: the logs are stored onshore. | The vendor holds a copy, runs the access path and answers to its own jurisdiction. |
You install nano on infrastructure you control, with Docker Compose or Kubernetes. Sources send logs to it over your network; it parses, stores, searches and runs detections on them there.
Your account in an Australian cloud region, your data center, or an air-gapped network
Never receives your logs.
Deploy into your own account in an Australian region. The infrastructure is yours: you choose the region, you pay the provider directly, and your existing cloud controls apply to the log store.
Run on your own servers, single node or multi-node with high availability. Logs and backups stay on storage you own, for as long as your retention policy says.
Included with every license, if your environment requires it: a signed image bundle, content and enrichment packs you import by hand, on-premises AI and an offline license you renew by hand. Air-gapped deployment
A connected install makes a few outbound HTTPS connections to nano. Here is each one, and what you can turn off.
| Exchange | What it contains | Direction | Can you turn it off? |
|---|---|---|---|
| License check-in, daily | Deployment ID, install ID, version, a nonce and the license token | To nano | Required when connected. Air-gapped installs use an offline license. |
| Usage, once per day | One number per completed UTC day: total GB ingested | To nano | Sent with the check-in when connected. |
| Content and enrichment feeds, hourly | Log-source catalog, detection rules and SOAR content; IPinfo Lite, ThreatFox and Tor exit node feeds. The poll carries no install data; nano sees the source IP. | Download | Yes. The default feeds are on by default and can be turned off. |
| Images and releases | nano container images at install and upgrade; on Kubernetes, a registry credential refreshed about every 20 minutes | Download | The Kubernetes credential refresh can be disabled. |
Several Australian regimes put a deadline on telling a regulator about an incident. Each one assumes you can already see what happened. As of November 2026:
| Regime | Trigger | Deadline | Report to |
|---|---|---|---|
| SOCI Act, Part 2Bcisc.gov.au · incident notification ↗ | Critical cyber security incident: significant impact on the availability of a critical infrastructure asset | 12 hours after becoming aware | ASD's ACSC |
| SOCI Act, Part 2Bcisc.gov.au · incident notification ↗ | Other cyber security incident: relevant impact on the asset | 72 hours after becoming aware | ASD's ACSC |
| APRA CPS 234, para 35apra.gov.au · CPS 234 ↗ | Material information security incident | As soon as possible, no later than 72 hours after becoming aware | APRA |
| Cyber Security Act 2024, s 27homeaffairs.gov.au · ransomware reporting ↗ | Ransomware or cyber extortion payment made | 72 hours after the payment, or after becoming aware of it | ASD, via the cyber.gov.au form |
| APRA CPS 234, para 36apra.gov.au · CPS 234 ↗ | Material control weakness you expect not to remediate in time | No later than 10 business days after becoming aware | APRA |
The Essential Eight adds that, from Maturity Level Two, incidents are reported to the CISO and to ASD "as soon as possible". nano keeps the alerts, evidence and case timeline these reports draw on. It does not report to any regulator for you.
ML2 and ML3 logging requirements, PSPF, and the move to ASD's Essentials.
Read Australia · ASDThe ISM security monitoring controls, control by control, including 12-month searchable retention.
Read Australia · CommonwealthWhat the Protective Security Policy Framework asks of Commonwealth entities' cyber security and logs.
Read Australia · ASDWhat an IRAP assessment is, why there is no IRAP certification, and where self-run software fits.
Read Australia · Critical infrastructure12-hour and 72-hour incident reporting, CIRMP, Systems of National Significance and ransomware payment reporting.
Read Australia · APRADetection and response, 72-hour notification to APRA, third parties, and how CPS 230 relates.
Readnano is licensed per GB/day of ingest, not per endpoint or per year of retention. You run, and pay for, the infrastructure in your own account or data center.
US$149/month at 5 GB/day and US$279/month at 10 GB/day, list price, invoiced in US dollars. Ask us for an indicative figure in Australian dollars. See pricing
Threatbear is our Australian partner, a cybersecurity firm in Queensland. Buy nano through them and work with them locally on incident response, threat intelligence, security architecture and engineering, and security assurance. About Threatbear
The ISM asks for event logs to be searchable for at least 12 months. Retention costs you storage you own, not license: keep what your policy needs and tier older events to your own object storage. ISM logging controls
Data sovereignty is the idea that data is subject to the laws, and the control, of the place and the organization it belongs to. In practice it asks two questions: which country's laws can reach the data, and who can actually access it or be compelled to hand it over. For security logs, that means knowing who stores them, who operates the systems that hold them, and which jurisdictions those parties answer to.
Data residency is about location: the data is stored in a particular country or region. Data sovereignty is about control and jurisdiction: whose laws apply and who can access the data. Data can be resident in Australia without being under your sole control, for example when a foreign-owned provider stores it in a Sydney region and runs the access path to it.
It gives you residency. Sovereignty also depends on who operates the service and which laws reach that operator. The Commonwealth's Protective Security Policy Framework (PSPF Release 2026, section 15.2.3) notes that foreign-owned service providers may be subject to extrajudicial control by a foreign entity, including being compelled to disclose customers' data. Running software yourself in your own Australian cloud account removes the software vendor from that picture; your cloud provider remains part of it. Your own data center or an air-gapped network removes both.
Not as a general rule. The Privacy Act does not ban sending personal information overseas; under APP 8 and section 16C, an organization that discloses personal information to an overseas recipient must take reasonable steps to make sure the recipient complies with the APPs, and is generally accountable if it doesn't. Specific rules can be stricter: for example, PSPF Release 2026 requires Commonwealth entities to host security classified information with providers certified under the Hosting Certification Framework. Sector rules and contracts can add more, so check the ones that apply to you.
No. nano is software you install and operate in your own environment. Your logs are collected, stored, searched and analyzed there, and nano has no copy of them and no standing access to your install. A connected install sends nano a daily license check-in (deployment ID, install ID, version and license token) and one usage number per day (total GB ingested), and polls nano hourly for content and enrichment feeds. Support works from what you choose to share with us.
Nowhere outside your environment unless you send them. Logs travel from your sources to the nano install you run, and are stored on disks and optional object storage you own, for the retention period you set. A connected install checks in its license daily, reports one usage number per day, polls nano hourly for content and enrichment feeds, and downloads images at install and upgrade. AI is off by default; when on, it calls your own model endpoint directly, never via nano.
Yes. Air-gapped operation is included with every license. In air-gapped mode there is no connection to nano at all: you install from a signed image bundle, import content and enrichment packs by hand, run AI against an on-premises model if you use it, and renew an offline license file by hand.
No. nano, LLC is a US company. Because you run nano yourself, nano never holds your log data, so there is no copy on nano's side for anyone to request. If you want to buy locally, you can buy nano through our Australian partner Threatbear.
No. nano is not IRAP-assessed and holds no ISO 27001, SOC 2 or other certification. It runs inside your own environment, including one you have had IRAP-assessed, and is assessed as part of your system by your assessor.
None of them is a data sovereignty law, but each makes where your security data lives and who can reach it part of your obligations. Under the SOCI Act, the enhanced risk management program rules list offshore or remote access to business critical data as a material risk. APRA's CPS 234 requires you to assess the information security of third parties that manage your information assets. The PSPF requires Commonwealth entities to use IRAP-assessed cloud providers and certified hosting for classified data. Keeping the SIEM in your own environment keeps those questions inside your own controls.
Last reviewed 13 November 2026. Regulations and guidance change, so read the current version at the source.
From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.