Stored only where you run nano.
Collection, parsing, storage, search, detections and cases all run in your Canadian region, data center or air-gapped network. nano, LLC has no copy and no standing access to your install.
nano, LLC is a US company, so the answer has to be the architecture. You run nano yourself: in your own account in a Canadian cloud region, in your data center, or air-gapped. 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.
Canadian buyers ask whether a US vendor puts their data within reach of US process. With most cloud SIEMs, the vendor stores your logs. With nano, it does not.
Collection, parsing, storage, search, detections and cases all run in your Canadian region, data center or air-gapped network. nano, LLC has no copy and no standing access to your install.
A connected install sends a daily license check-in and the total GB ingested per day. No log content. Air-gapped installs send nothing. Every connection
AI is off by default. When on, it calls the model endpoint you configure directly, including one you host in Canada. Model prompts and log context go to that endpoint, not through nano. AI settings
What each asks of your security logs, and where a SIEM you run yourself fits, as of November 2026.
| Rule | Who it binds | What it asks of logs | How running nano yourself helps |
|---|---|---|---|
| Bill C-8: Critical Cyber Systems Protection Act (CCSPA)laws-lois.justice.gc.ca · CCSPA ↗canada.ca · Royal Assent ↗ | Designated operators in federally regulated finance, telecommunications, energy and transportation | A cyber security program (s.9). Report a cyber security incident to the Communications Security Establishment "within a period prescribed by the regulations, not to exceed 72 hours" (s.17), and notify the regulator "Immediately after reporting" (s.18). "The records must be kept in Canada by the designated operator at any place that is prescribed by the regulations" (s.30(2)).Royal Assent June 2026. Not yet in force, and no designated operators are named yet. | Logs and the evidence behind an incident report stay in the Canadian region or data center you choose. nano never receives them, so no copy sits with a vendor anywhere else. |
| OSFI Guideline B-13, section 3.3 Detectosfi-bsif.gc.ca · B-13 ↗ | Federally regulated financial institutions (FRFIs) | "FRFIs should ensure continuous security logging for technology assets and different layers of defence tools." They "should implement minimum security log retention periods and maintain cyber security event logs" to support forensic investigation. B-13 does not set a retention length.A supervisory expectation, effective 1 January 2024. | Collects logs continuously from the sources you choose, into one store you own. The retention period is yours to set, and a longer one costs you storage, not license. |
| Quebec Law 25: s.17 of the private sector privacy Act (P-39.1)legisquebec.gouv.qc.ca · P-39.1 ↗ | Private-sector enterprises | "Before communicating personal information outside Québec, a person carrying on an enterprise must conduct a privacy impact assessment." The information may go only if it "would receive adequate protection", under a written agreement. The same applies when an enterprise has someone outside Québec keep the information on its behalf. | Security logs carry personal information. Run nano in a Québec region or your own Québec data center and no SIEM vendor outside Québec keeps them for you. |
| Protected B: Directive on Service and Digital and ITSG-33tbs-sct.canada.ca · Directive ↗cyber.gc.ca · ITSG-33 Annex 3A ↗ | Federal departments and agencies | Computing facilities in Canada are to be "identified and evaluated as a principal delivery option" for information categorized Protected B, Protected C or classified (Directive, 4.3.24). ITSG-33 sets the security controls, including the Audit and Accountability (AU) family: AU-2 auditable events, AU-6 audit review, analysis and reporting, AU-9 protection of audit information, AU-11 audit record retention. | Runs inside your Protected B environment in a Canadian region or on your own servers, or air-gapped. The AU controls are assessed on your system; nano is the software that collects, protects and reviews the audit records there. |
You install nano with Docker Compose or with Helm on Kubernetes, on infrastructure you control. Sources send logs to it over your network; it parses, stores, searches and runs detections on them there.
Your account in a Canadian cloud region, your data center, or an air-gapped network
Never receives your logs.
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, or on Kubernetes with Helm. 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. |
nano 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 in US dollars. Pay monthly by card, or annually by card or invoice. See pricing
Buying through a procurement process, or need a vendor questionnaire answered? Email sales@nano.rs. nano, LLC is a US company. Every license includes every feature; only GB/day and support level vary.
Retention costs you storage you own, not license. It defaults to 365 days; set what your policy needs and tier older events to your own object storage. Storage and retention
nano never has your logs to give. You install and operate nano in your own environment, in a Canadian cloud region, in your own data center or air-gapped, and your logs are collected, stored and analyzed there. nano, LLC receives no log content: a connected install sends a daily license check-in and one usage number per day (total GB ingested), and air-gapped installs send nothing. nano has no standing access to your install. Support sees only what you choose to share. AI is off by default and, when on, calls your own model endpoint directly. Whatever legal process applies to your cloud provider or to you is unchanged; nano simply holds no copy.
Not yet. Bill C-8 received Royal Assent in June 2026 and enacts the Critical Cyber Systems Protection Act, but the CCSPA is not yet in force, and no designated operators have been named. Once it is in force, designated operators must run a cyber security program, report cyber security incidents to the Communications Security Establishment within a period set by regulation that may not exceed 72 hours, and keep records in Canada (s.30(2)).
Section 30(2) says "The records must be kept in Canada by the designated operator at any place that is prescribed by the regulations", or at the operator's place of business if no place is prescribed, in the manner and for the period the regulator sets. It is not yet in force, and the regulations will define the details. Running nano in a Canadian region or your own Canadian data center keeps your security logs in Canada either way.
B-13 does not set a length. It says FRFIs "should implement minimum security log retention periods and maintain cyber security event logs" to support forensic investigation, and "should ensure continuous security logging for technology assets and different layers of defence tools." The retention period is your institution's decision. In nano, retention defaults to 365 days and you set what your policy needs.
Not outright. Section 17 requires a privacy impact assessment before personal information is communicated outside Québec, or kept by someone outside Québec on your behalf, and the information may go only if it would receive adequate protection, under a written agreement. Security logs contain personal information such as user names and IP addresses. If you run nano in a Québec region or data center, the logs stay in Québec and no SIEM vendor keeps them for you.
You can run nano inside a Protected B environment you operate: in a Canadian cloud region, on your own servers, or air-gapped. nano, LLC holds no Protected B, ITSG-33 or Canadian Centre for Cyber Security assessment, and using nano does not make a system compliant. Your security assessment covers your system, including how nano is configured in it.
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. nano has no standing access to your install. Support sees only what you choose to share.
Anywhere you control: your own account in AWS ca-central-1 or ca-west-1, Azure Canada Central or Canada East, or Google Cloud Montréal or Toronto; your own servers; Kubernetes with Helm; or an air-gapped network. nano does not host anything for you.
Online, in US dollars, the same way as everywhere else. Pay monthly by card, or annually by card or invoice. Every license includes every feature, including air-gapped operation; only the GB/day and support level change the price. If your procurement team needs an order form, vendor forms or a security questionnaire, email sales.
Last reviewed 14 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.