Independent studio · Auckland, NZ

Custom software, drawn to spec and shipped on Azure.

Tell us what your business needs to run. We architect it, build it to order in .NET, and ship it to production on Microsoft Azure — then keep it running. You work with the two senior engineers writing the code.

Book a working call See the work 35+ years · Azure & .NET
system.drawing — sheet 01 · 2026
internet env: prod · australiaeast Front Door edge routing · WAF App Service runs your application Service Bus durable messaging Functions event-driven work Azure SQL consistent, backed-up data Key Vault secrets & keys
fig. 01 — reference architecturehover / focus a component →
Process

How an engagement runs

Every project is tracked like a drawing — from the first brief to issued-for-production.

RevDescriptionOwnerWhen
ABrief & constraints. We map what your business actually needs — the outcome, not a feature list.you + usWeek 0
BArchitecture drawing. The system on paper before a line of code — so you can see and approve the shape.usWeek 1
CBuild to spec. Shipped in working increments, with senior review on every change.usWeek 2+
DIssued for production. Live on Azure — and we stay on to operate, monitor and improve it.usShip →
Capabilities

What we build with

The whole stack, built and run by the same two people. No handoffs.

Azure cloud engineering

Architecture, hosting, networking and identity — designed for your load, not a template.

.NET / C#

The application itself, built to order — the APIs, services and product your business runs on.

Infrastructure as code

Reproducible environments. Nothing exists that wasn't written down and reviewed.

CI/CD

Automated build, test and deploy — so shipping is routine, not an event.

Observability

Logs, metrics and alerts in production — we see problems before you do.

Run & support

We operate what we ship. The people who built it are the people who keep it running.

The team

You hire the people who write the code

No account managers. No juniors learning on your project. Two senior engineers — the ones who design it, build it, and keep it running.

Robert O’Donnell

Principal Developer · 15+ yrs

Fifteen-plus years building enterprise software end to end on the Microsoft .NET and Azure stack — .NET (3.5 → .NET 10) and C#, with React and TypeScript up front, SQL Server and PostgreSQL behind, and containerised, event-driven microservices (Docker, AKS, Azure Container Apps) throughout.

Spent eight years in medical-device software for a healthcare-equipment manufacturer, building to IEC 62304, IEC 60601 and ISO 14971 — and personally presenting it to TÜV and FDA auditors with no findings raised. Conceived and delivered the cloud platform that became core to that company’s device-data integration strategy, then ran the team — grown to 13 developers — as development manager, with budget and delivery authority.

Since then, has shipped for clients in fintech (payroll), enterprise print & imaging (a Dynamics 365 migration, and recovering a sabotaged codebase), port logistics, and multi-site tourism operations — the work where you’re handed a tangled legacy system and asked to make it fast, secure and maintainable. One rewrite took a query that wouldn’t finish in four hours down to sub-second. Works close to the metal too — embedded on Arduino, Teensy and STM32 — which keeps the systems thinking honest.

Patrick O’Donnell

Solutions Architect · 20+ yrs

Twenty-plus years in IT, the last decade-plus designing and building secure, real-time systems on Azure — identity, messaging, container orchestration, and the Terraform to provision it all reproducibly: Auth0 and OpenID Connect, AKS / Kubernetes, Service Bus, SignalR, API Management, with Blazor and Angular on the front.

For a major New Zealand investment-administration firm, rebuilt the investor and adviser portals — migrating authentication to Auth0 behind a backend-for-frontend reverse proxy, containerising the services as microservices on AKS, and building a distributed reporting pipeline on Service Bus and SignalR. The systems have passed four penetration tests in three years, the latest with only low-severity findings.

Earlier, as technical lead then development manager for a primary-care network, drove the new platform that replaced a costly legacy system the network had outgrown — board-ratified as the way forward — and re-engineered the critical monthly funding run the whole practice network depended on. Founded Cloud Services and has traded under it since 2019.

One of us replies within a working day — Auckland (NZST), working worldwide.

35+
Years between us
7
Sites live, worldwide
13
Developers led on a regulated platform
4hr → <1s
A legacy query, rewritten
Selected work

The work, with the outcome beside it

Delivered by the two of us. We show client work by sector, never by name — a discretion your own project would get too. With Ease is our own product.

REC-01 · tourism & operations

Multi-site leisure operations platform

leisure & attractions · 7 sites worldwide

A cloud-first platform that replaced an underperforming ERP — tracking real-time ride counts and cart maintenance across seven sites worldwide.

real-time · 7 sitesAzure Functions · Event Hub · SignalR · AKS
REC-02 · financial services

Investor & adviser portals

investment administration · NZ

Secure portals giving investors and advisers a live view of performance — migrated to Auth0, containerised on AKS, hardened across four penetration tests.

4 pen-tests · low-severity onlyAuth0 · AKS · Service Bus · Terraform
REC-03 · healthcare

Primary-care platform

primary-care network · NZ

A hybrid-cloud platform to replace a costly legacy system across a primary-care network — board-ratified as the way forward, opening new shared services to practices across the region.

hybrid cloud · legacy replacement.NET · Azure SQL · AKS · Service Bus
REC-04 · our product

With Ease

SaaS · small trade businesses

Our own SaaS for small trade businesses — the whole operation in one place, on the same Azure foundations we ship for clients.

in build.NET · Azure · multi-tenant SaaS

Bring us the problem. You’ll leave with a plan.

A working call with the two engineers who’ll build it — not a pitch.

Book a working call