Practice · Engineering

Azure and cloud engineering

Cloud migration, platform engineering, integration and DevOps across Microsoft Azure and AWS. Coder Trove builds and operates the cloud platforms that enterprise workloads run on, in Australian regions where data residency requires it.

Start a conversation See client work

The practice

Built to run, not just to launch.

The cloud practice covers the full arc: assessing an estate, designing the target platform, migrating workloads, and operating what lands. Our engineers work across Azure and AWS, in infrastructure as code, and hold the view that a migration is finished when the old environment is switched off, not when the new one is switched on.

The practice underpins our other work: Dynamics 365 integrations run through Azure services, AI systems run on cloud data platforms, and custom software ships onto infrastructure this practice designs.

What we deliver

Five lines of work.

MIGRATION

Cloud migration

Assessment, wave planning, migration and decommissioning for workloads moving from data centres and legacy hosting into Azure and AWS. Each workload gets an explicit disposition, rehost, replatform, refactor or retire, with the business case stated per workload rather than assumed for the estate.

Decommissioning is planned from the start, because the saving only exists once the old environment is gone.

PLATFORM

Platform engineering

Landing zones, network topology, identity and environment design, built as infrastructure as code in Terraform and Bicep. The platform is versioned, reviewable and reproducible: a new environment is a pipeline run, not a fortnight of tickets. Guardrails are policy-driven so teams can ship without waiting on a central queue.

INTEGRATION

Integration and serverless

APIs, event-driven messaging and serverless workloads on Azure Functions, Service Bus, API Management and their AWS counterparts. Integration is built as versioned, monitored components with defined ownership, the connective tissue between ERP, line-of-business systems and data platforms.

DEVOPS

DevOps and delivery engineering

CI/CD pipelines, automated testing, release management and observability across Azure DevOps and GitHub. The practice sets up the delivery machinery other teams run on, including the build and release pipelines that carry our Dynamics 365 and custom software programmes.

OPERATIONS

Operations and cost

Monitoring, alerting, patching cadence and cost management for live cloud estates. Cost work is treated as engineering rather than procurement: right-sizing, reservations, storage tiering and the architectural decisions that determine the bill. Reviews report in dollars against workloads, not percentages against budgets.

Delivery

How the work runs.

Everything as code

Infrastructure, policy and pipelines live in source control. Changes are reviewed, tested and deployed the same way application code is, which makes the platform auditable and makes recovery a rebuild rather than an archaeology project.

Security in the design

Identity, network segmentation, encryption and logging are platform decisions, not afterthoughts. The practice works with our cyber security practice on hardening, and platforms are designed with Essential Eight alignment and Australian data residency where clients require it.

Run it or hand it over

Some clients want the platform operated; others want their own engineers running it after handover. Both are supported, with documentation, runbooks and training treated as deliverables rather than leftovers.

Case study

Switch Automation

Engineers embedded in the product team of a US building analytics platform, shipping .NET services on Azure and the dashboards facilities teams run on.

READ THE CASE STUDY →

Common questions

Cloud, answered plainly.

Azure or AWS?
Both are capable platforms, and the practice works in both. Azure usually wins where the estate is Microsoft-centred: Dynamics 365, Microsoft 365 identity, .NET workloads. AWS often fits product companies and data-heavy platforms. The honest answer is that the choice matters less than the quality of the platform engineering on top of it, and we say which one fits your case rather than defaulting to a preference.
Lift-and-shift or re-architect?
Per workload, not per estate. Rehosting is right for stable systems near end of life; replatforming and refactoring pay off for systems under active change, where cloud-native services reduce operating cost and risk. We give each workload a disposition with the reasoning written down, so the migration plan survives scrutiny.
How long does a cloud migration take?
A small estate can move in a quarter. A large one moves in waves over six to eighteen months, ordered by dependency and risk rather than alphabetically. The schedule is driven by integration untangling and testing, not by the copying of virtual machines, which is the easy part.
How do we keep cloud costs under control?
By treating cost as an engineering property. The large levers are architecture: right-sizing, autoscaling, storage tiering, reservations and switching off what nothing uses. Tagging and per-workload reporting make the bill legible, and a monthly review in dollars against workloads keeps it that way. Most estates we review carry 20 to 30 per cent of avoidable spend.
Can our data stay in Australia?
Yes. Azure and AWS both operate Australian regions, and platforms are designed for data residency where clients require it, including backup and disaster recovery locations. Residency is a design decision made at landing-zone level, not a checkbox added later.
Do you operate the platform after it is built?
If wanted, yes: monitoring, patching, incident response and cost management under an ongoing arrangement, from Australia, our Vietnam delivery centre, or both. If the client's own team will run it, the handover includes runbooks, documentation and working sessions until the team is confident, and the engagement ends when they are.

Start here

Tell us what the platform needs to do.

A data centre exit, a platform that fights its engineers, an integration layer that will not hold, or a bill nobody can explain. A consultant who has done comparable work replies within one business day.

Start a conversation