A://RUN09Sovereign Cloud
Data that stays
in New Zealand.
Cloud hosting on infrastructure physically located in New Zealand, for workloads where the location of the data is a contractual or regulatory question rather than a preference. It is for public sector suppliers, health, professional services, and any organisation with data residency obligations.
THE PROBLEM
Data residency is easy to promise in a tender and awkward to evidence afterwards.
The cost of leaving this alone is rarely one visible failure. It is the slow accumulation: the workaround that became the process, the thing only one person knows, the renewal nobody questioned.
Our starting point is always the same: establish what is actually true today, then decide what to change. Work scoped against an assumption tends to solve a problem you do not have.
- 01Nobody owns itIt sits with whoever touched it last, which is not the same as being managed.
- 02No current pictureWhat you have, what it costs, and who has access are all slightly out of date.
- 03Only handled when it breaksAttention arrives after the disruption rather than before it.
WHAT YOU GET
What the engagement covers
Scoped before it starts, so you know what is included and what is not.
- 01
Residency assessment
What your obligations actually are, separated from what people assume they are. The two are often quite different, and the difference is usually expensive.
- 02
Placement
Workloads hosted in country, with evidence of where the data sits, where it is backed up, and who is able to reach it.
- 03
Migration
Moved from offshore or on-premise with a rollback position at every stage.
- 04
Evidence pack
The documentation an auditor, an insurer, or a tender response actually asks for, written so you can hand it over without translating it first.
HOW WE WORK
Assess, deploy, operate, review
Four stages with a written output at each one. You always know which stage you are in and what comes next.
- 01Week 1
Assess
We document what exists today and what it needs to do, so the work is scoped against reality rather than assumption.
- 02Weeks 2 – 4
Deploy
Changes are made in a planned sequence, outside working hours where disruption would otherwise land on your staff.
- 03Ongoing
Operate
It is monitored and maintained as part of your agreement. Problems are ours to notice, not yours to report.
- 04Quarterly
Review
What it is costing, whether it still fits, and what should change before the next renewal.
WHAT CHANGES
What you should expect
- Someone other than you owns it, with that written down.
- The current state is documented and stays documented.
- Cost is planned ahead rather than discovered at renewal.
- Decisions are made against evidence rather than assumption.
FAQ
Questions we get asked
01What is sovereign cloud?
Cloud hosting on infrastructure physically located in New Zealand, for workloads where the location of the data is a contractual or regulatory question rather than a preference. It is for public sector suppliers, health, professional services, and any organisation with data residency obligations.
02What is sovereign cloud, and how is it different from normal cloud?
Sovereign cloud means the infrastructure your data sits on is physically located in New Zealand and operated under New Zealand jurisdiction, so the question of which country’s law applies to your data has a single clear answer. Mainstream public cloud may store your data in Australia, Singapore, or the United States depending on the service, and may replicate it across regions in ways that are documented but rarely read.
03Does New Zealand law require our data to be stored in New Zealand?
Generally no. The Privacy Act 2020 does not mandate onshore storage, but it does make you responsible for information you send overseas, requiring comparable safeguards wherever it lands. The stricter requirements usually come from elsewhere: government procurement rules, health sector expectations, professional obligations, or a clause in a customer contract that somebody signed. We start by establishing which of those actually apply to you.
04Is sovereign cloud more expensive than AWS or Azure?
Per unit of compute, usually yes, because it does not carry hyperscale economics. Against the total cost it is often closer than expected once you account for data transfer charges, the cost of demonstrating residency for an offshore platform, and the commercial value of being able to answer the question cleanly in a tender. We model both so the decision is made on numbers.
05How do we prove to a customer or an auditor that our data is held in New Zealand?
With documentation rather than assurance. That means naming the facility, evidencing its certifications, showing where backups and replicas live, and listing who has administrative access and from which jurisdiction. This is the part most organisations discover they cannot produce, generally two days before a tender closes.
06Can we move only some workloads to sovereign cloud?
Yes, and that is the common outcome. Usually the systems holding regulated or client-confidential information move, and general workloads stay where they are. The important thing is that the boundary is deliberate and written down, because a hybrid arrangement nobody documented is harder to evidence than either option on its own.
07How much does sovereign cloud cost in New Zealand?
We quote after scoping rather than before. Anyone pricing this work without looking at your environment is guessing, and the guess is rarely in your favour. Scoping itself is quick, and we tell you what it costs before we start it.
08How long does it take to get started with sovereign cloud?
A first conversation takes about half an hour and costs nothing. Scoping is usually a week or two of our time depending on the size of the environment, and we agree the delivery dates with you before anything is booked in.
09Can you deliver sovereign cloud alongside our existing IT team or provider?
Yes, and it is common. We are happy to work as an extra pair of hands under your internal team, or alongside an incumbent provider on a defined piece of work. We will set out in writing where the responsibilities split, so nothing falls between us.
10Do we have to move all of our IT to Atlas to get this?
No. This can be delivered as a standalone piece of work for an organisation we have never worked with before, or folded into a managed agreement if you already have one with us. Plenty of clients use us for one thing and keep everything else where it is.
11Do you only work with Auckland businesses?
Our team is based in Auckland and we attend sites across the wider region. Most of this work is delivered remotely, so we support organisations throughout New Zealand, and we will say up front where being on site genuinely matters.
12Who will we actually be dealing with day to day?
Named people, not a queue. You get a lead who knows your environment and stays with it, which is the difference between explaining your business once and explaining it every time you make contact.
13What happens if we want to leave?
You keep the documentation regardless, and anything registered in your name stays in your name. Whether we stay involved is your call. Some clients take it in house from there, others move it onto an ongoing agreement with us. We would rather you left cleanly than stayed because leaving was difficult.
Start with a conversation.
Tell us what you are dealing with and we will tell you whether this is the right service for it, and what it would take.
← All services