India · Data localization

Your security logs stay in your Indian environment.

nano is a SIEM you run yourself: in your own account in an Indian 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.

Buy nano
Talk to sales
Indian rules for security logs

Five rulebooks. One place your logs live.

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
CERT-In Directions, 28 April 2022cert-in.org.in · Directions 2022 ↗ "service providers, intermediaries, data centres, body corporate and Government organisations" Enable logs of all ICT systems and keep them securely for a rolling 180 days, within the Indian jurisdiction. Provide them to CERT-In with an incident report or when directed. Report listed incidents within 6 hours. Sync clocks to NIC or NPL NTP servers. The log store runs in the Indian region or data center you choose, for the retention you set. You search and pull logs for CERT-In from your own instance, without asking a vendor.
DPDP Rules 2025egazette.gov.in · DPDP Rules 2025 ↗ Data Fiduciaries, including processing by their Data Processors From 13 May 2027: visibility on access to personal data through logs, monitoring and review; keep those logs for one year; report a personal data breach to the Board within 72 hours. One year of logs on storage you own. nano never receives the logs, so it is not processing that personal data for you.
RBIrbi.org.in · payment data ↗rbi.org.in · IT governance MD ↗ Payment system providers (2018 circular); commercial banks, NBFCs in the Top, Upper and Middle layers, CICs and AIFIs (2023 Master Direction) Payment system data is stored only in India (2018 circular). Banks and covered entities regularly monitor audit trails and system logs, and the CISO's office runs a SOC (2023 Master Direction). The 2023 Direction sets no log retention period. Gives a SOC one place to monitor audit trails and system logs, inside your own environment. If logs carry payment data, they stay where you run nano.
SEBI CSCRF, August 2024sebi.gov.in · CSCRF ↗sebi.gov.in · CIR/2025/119 ↗ SEBI-regulated entities, for systems used exclusively for SEBI-regulated activities A SOC for all regulated entities (except client-based stock brokers with fewer than 100 clients). User access logs for critical systems kept at least two years, at least 6 months of that online. CSCRF's data localization clause has been in abeyance since 31 December 2024. Keep recent logs searchable on fast disk and tier older ones to your own object storage, for as long as your policy says.
IRDAI Information and Cyber Security Guidelinesirdai.gov.in · Guidelines 2026 ↗ Insurers and other IRDAI-regulated entities ICT infrastructure logs kept for a rolling 180 days within the Indian jurisdiction, end-to-end monitoring of IT logs through a SIEM by a 24x7 SOC, and cyber incidents reported within 6 hours to CERT-In with a copy to IRDAI. Logs stay in your Indian environment and your SOC analyzes them there, with alerts and cases.
Where to run nano in India

Your account, your region, your hardware.

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 environment

Your account in an Indian cloud region, your data center, or an air-gapped network

01 · Sources
  • firewall
  • VPN
  • proxy
  • Windows
  • Linux / SSH
  • database
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano runs inside your environment. Log data is never sent to nano.
Your cloud account in India

The Indian region you pick.

  • AWS Asia Pacific (Mumbai) ap-south-1, Asia Pacific (Hyderabad) ap-south-2
  • Microsoft Azure Central India
  • Google Cloud Mumbai asia-south1, Delhi asia-south2

You pay the provider directly, and your existing cloud controls apply to the log store.

Your data center

On hardware you own.

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.

Air-gapped

No connection to nano at all.

Included with every license: 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

What a connected install exchanges with nano

Every connection. No log content in any of them.

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.
Pricing and buying from India

Buy online. The infrastructure stays yours.

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.

List price · US$

From US$149/month.

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

Procurement

Order forms and vendor paperwork.

Buying through a procurement process, or need a vendor questionnaire answered? Email sales@nano.rs. Every license includes every feature; only GB/day and support level vary.

Retention

180 days or a year, without a bigger license.

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

FAQ

Questions we get asked.

Does CERT-In require logs to stay in India?

Direction (iv) of the CERT-In Directions of 28 April 2022 says logs of all ICT systems "shall be maintained within the Indian jurisdiction" for a rolling 180 days. CERT-In's own FAQ (Q35) then says logs "may be stored outside India also as long as the obligation to produce logs to CERT-In is adhered to by the entities in a reasonable time", while Q36 says service providers serving users in India keep logs and records of financial transactions in the Indian jurisdiction. The FAQ states that it is not a legal document. Running nano in your own Indian cloud region or data center keeps the logs in India and under your control, which removes the jurisdiction question.

Is nano a CERT-In empanelled auditor?

No. nano is software, not an audit firm, and it is not on CERT-In's list of empanelled auditors. nano, LLC holds no Indian empanelment, certification or approval, and using nano does not make you compliant. It is the SIEM you run; your auditor assesses your environment, including how you use it.

Does nano store my logs?

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 and one usage number per day (total GB ingested), and downloads content and feeds. Air-gapped installs send nano nothing.

How do I size 180 days of retention?

Start from your daily ingest in GB. After a few days of real data, Settings → Storage & Retention shows the compressed and uncompressed size of your event store, which gives your own compression ratio. Disk needed is roughly daily ingest times 180 days, divided by that ratio, plus headroom. Retention defaults to 365 days and you can set it through the API; older data can be tiered to S3-compatible object storage you own and stays searchable. The license is priced per GB/day of ingest, so a longer retention costs you storage, not license.

Where in India can I run nano?

Anywhere you control: your own account in AWS Mumbai or Hyderabad, Azure Central India, or Google Cloud Mumbai or Delhi; your own servers in your data center; Kubernetes with Helm; or an air-gapped network. nano does not host anything for you in India or elsewhere.

Does the DPDP one-year log retention apply now?

Not yet. The DPDP Rules 2025 were notified on 13 November 2025, and the rules on security safeguards, logs, breach reporting and retention (Rules 3, 5 to 16, 22 and 23) commence on 13 May 2027. From then, Data Fiduciaries keep logs of personal data processing for at least one year and report breaches to the Board within 72 hours.

Does SEBI require security logs to stay in India?

Not at present. The CSCRF's data localization clause has been in abeyance since SEBI's circular of 31 December 2024. What the CSCRF does require is a SOC for regulated entities and at least two years of user access logs for critical systems, with at least 6 months kept online.

Is nano an Indian company?

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. Your logs stay in the Indian environment you choose.

How do I buy nano in India?

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.

Primary sources

Read the rules yourself.

Start with nano.

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.

Buy nano
Talk to sales