FAQ
Browse by topic. The sidebar jumps to each category; the active section updates as you scroll.
About Kapua
What this site is, and who it is for.
Kapua is a New Zealand blog on the human side of cloud, AI, and DevOps — people, process, and journey, not vendor trivia. The tagline is "Big transformations, one deliberate step at a time."
Steve Rackham, a cloud architect and AI consultant based in Dunedin, Aotearoa New Zealand. The stories are composite and fictionalised where needed; the failure modes are not.
Cloud architects, DevOps engineers, platform teams, and delivery leads running or reviewing landing zone and platform programmes — especially in lean NZ organisations.
Series
How the multi-part arcs fit together.
Start with Before You Deploy if you want the cautionary map. Read Success Patterns for the chronological rebuild. In Production covers years two to four.
No. They are invented organisations used to tell realistic NZ platform stories. Any resemblance to a real war story is, unfortunately, the point.
Drafts are excluded from production listings, RSS, and the sitemap, and carry noindex. They are still built so you can review them before undrafting.
Landing zones
Common questions about Azure foundations in NZ.
No. It is not a residency law. Putting personal information in an overseas region is usually an offshore disclosure under IPP 12, so you need comparable safeguards. Contracts, NZISM, RBNZ expectations, and board appetite often pin location harder than the statute.
You need the parts your workloads depend on — identity, connectivity, subscription structure, and baseline guardrails. You do not need the complete reference before the first workload. Deploying everything before discovery is a failure mode this site covers at length.
It improves local residency and latency options. It does not fix a landing zone whose defaults were never mapped to your obligations. Residency and governance are separate decisions.
Engagements
Working together on a platform problem.
Browse /services/ for the problem that matches yours, then email [email protected] from the Contact page. Package details and pricing are TBA — contact for more on whether a fixed review or ongoing advisory fits.
Remote-first from Dunedin, with clients across New Zealand. On-site workshops are available when the problem needs a room full of stakeholders. The Dunedin cost base supports national work without Auckland overhead baked into every day.
Pricing and package details are TBA. Contact for more via the Contact page — fees depend on estate size, scope, and regulatory surface.
Exclusions are TBA on the service pages for now. In short: slideware without an implementation path, rubber-stamping accelerator defaults, chatbot demos with no owner or metric, and being a silent ticket queue or sole on-call. Contact for more if you are unsure whether the fit is right.