Home / Services / Cloud, cost and accessibility

Sovereign cloud and data residency: your data in India, under your control

By Mirav Labs, led by Deepak MittalUpdated
Short answer

Sovereign cloud runs your workloads in India and leaves you, not a third party, in charge of operators, encryption keys and access. We plan and build it: Indian public cloud regions, private cloud or a mix, location rules enforced as code, keys in your custody, backup and disaster recovery inside India, and a file of evidence showing where every copy is kept.

Key takeaways

  • Residency is about every copy: logs, backups, DR replicas, analytics, support access and keys, not only the main database.
  • Indian public cloud regions, private cloud and hybrid each fit different needs; choose on requirements, cost and the team that will run it.
  • Whoever controls the keys controls who can read the data.
  • Backups and recovery sites need to stay in India too, and restores need testing.
  • Requirements come from sector regulators and customer contracts today; the DPDP Act has no general localisation rule.

For a bank, a broker or an insurer, keeping certain data in India is a regulatory condition. For a SaaS company selling to them, or bidding for public sector work, it turns up as a contract clause or a tender line. For everyone else it is increasingly a question on the security questionnaire. The trouble is that a database in an Indian region does not settle it. Backups replicate abroad, monitoring tools ship logs to another continent, and a vendor's support desk somewhere else can open a session on your servers.

We plan and build cloud estates where the right data stays in India, the keys stay with you, recovery happens in-country, and you can show all of it on demand.

What sovereignty means in engineering terms

The phrase is used loosely, and India has not defined it in law. For design purposes we break it into four questions:

  • Location. Where is the data stored and processed, counting every copy?
  • Operation. Who can run, change and support the environment, and from where?
  • Keys. Who holds the encryption keys, and who is able to use them?
  • Reach. Which people, vendors and legal systems could get to the data?

The answers point to one of a few patterns. A public cloud region in India, fenced so nothing can be created outside it, suits most workloads and keeps managed services available. A private cloud in Indian facilities hands you the hardware and the operator list, along with patching, capacity and on-call. Many organisations land on a mix: the regulated core on private infrastructure, the rest in an Indian public region. We compare the options on your requirements, cost and operating capacity, without steering you to a vendor. Our FinOps work can put numbers on each.

How we build it

We work through five steps, and we do not skip ahead: placing workloads before you know what is covered tends to move too much or too little.

How we keep data in India and prove itClassify to prove
Step 1Classify

Which data must stay in India

Step 2Place

Indian regions or private cloud

Step 3Encrypt

Keys you control

Step 4Back up

Backups and recovery in India too

Step 5Prove

Evidence of where data lives

Now:
  1. Classify. Your counsel tells us which data is covered and why; we write it into a register with sources. Then we trace where that data really goes, including the copies teams forget, such as debug logs, crash reports, product analytics, data warehouse extracts, staging restores and prompts sent to AI services. A privacy engineering inventory, if you have one, speeds this up.
  2. Place. We draw the target estate and move covered workloads into it. Location rules become code: account-wide policies that reject resources in unapproved regions, and deployment checks that stop a change before it lands. Anything with a global footprint, from CDN and DNS to email relays and observability, is either pinned to India or kept clear of covered fields.
  3. Encrypt. Keys are generated and held in India under your control, in a managed key service or an HSM. Key admins are separate from system admins, every use of a key is logged, and rotation is scheduled. Where analytics or support only need a reference, we swap covered values for tokens, which shrinks the regulated footprint.
  4. Back up. Recovery copies follow the same rule as the primary. We set up a second Indian site far enough from the first to survive a regional event, turn off any replication that leaves the country, keep backup keys local, and time a full restore.
  5. Prove. You get a file you can hand over: the register, the copy map, exported policies, key and backup locations, restore timings and a supplier list showing where each one stores and accesses data. Automated checks repeat the location tests on a schedule and raise an alert if anything moves.

People are a path too. Admin and vendor sessions are opened only for a named task, expire on their own, come from approved places and devices, and are recorded in logs kept in India.

Where the requirements come from

The DPDP Act is not the main driver here. It lets data go abroad unless the government blocks a destination by notification, and it has blocked none. Sector rules are stricter. RBI's 2018 direction on payment system data says operators must keep that data in systems located only in India, and SEBI's March 2023 framework for cloud adoption lays down conditions for regulated entities that use cloud services. Contracts and tenders add more. Which of these bind you is a call for your counsel; turning the answer into architecture is ours.

Staying in India is one part of being able to recover. Our cyber resilience service adds tamper-proof copies and rehearsed restores on top of the in-country design.

What you get

DeliverableContentsUse
Residency registerEach legal, regulatory or contract condition, the data in scope and where the condition comes fromThe yardstick for every design decision
Data flow and copy mapPrimary stores plus logs, backups, analytics, test copies and third-party toolsShows which routes leave India today
Target designPublic region, private cloud or mixed, with network and managed-service choicesThe blueprint your team builds from
Location policies in codeAccount policies and deployment checks for approved regionsBlocks new resources in the wrong place
Key custody planWhere keys live, who administers them, rotation and usage loggingDecides who can actually read the data
In-India recovery setupSecond site, replication settings and a timed restoreRecovery that never needs another country
Evidence filePolicy exports, test results, supplier storage and access countriesAnswers regulators, auditors and customer reviews

How to start

Collect the regulator circulars, contract clauses and tender conditions that mention where data must be kept, plus a list of your cloud accounts and main suppliers. In the first phase we turn those into a register and a copy map, and point out what is leaving India now. To set up that first phase, book a scoping call.

The DPDP side of this

Our DPDP practice, DPDP Ready, has a detailed guide on how this work maps to India's data protection law. Read it on DPDP Ready →

Frequently asked questions

Is a private cloud more secure than a public cloud region in India?

Not automatically. A private cloud gives you more control over hardware, operators and network, but you also take on patching, monitoring and capacity that a public cloud provider would otherwise run. Security depends on how well each is configured and operated. Many organisations keep a small regulated core private and run the rest in an Indian public region.

How do we move an existing application to an Indian cloud region?

Start by mapping every component and copy, including managed services that may be global by default. Then build the target in the Indian region, replicate data, test, and cut over in a planned window with a rollback route. Afterwards, confirm that old copies abroad are deleted and that region policies stop new resources being created outside India.

What does bring your own key mean for data residency?

It means the encryption keys protecting your data are created and controlled by you, usually in an India-based key management service or HSM, rather than managed entirely by the provider. You decide who can use them and can see every use in logs. It narrows who can read the data, though it does not by itself stop a provider operating the service.

Does keeping data in India increase cloud costs?

It can. Some services cost more or are not available in every Indian region, a second Indian region for recovery adds spend, and private cloud has its own fixed costs. Careful sizing and keeping only covered data under the strictest controls usually limit the increase.

Can we use global SaaS tools and still keep data in India?

Often, if covered data never reaches them. Common approaches are to choose an India data location where the tool offers one, to mask or tokenise covered fields before they are sent, or to keep regulated workflows in systems you host. Each tool and its sub-processors should be on your vendor location list.

Scope it with us

A 30-minute call to understand your systems and what good looks like. We aim to send a written, fixed-scope proposal within three working days.

Talk to us

Related services

This page describes engineering and security services. Where it mentions laws, rules or standards, it is general information, not legal advice.

Talk to us