The short answer
LDelight sets up and runs DevOps platforms for Sydney and Australian businesses on AWS and Azure. We build pipelines, infrastructure as code and monitoring that live entirely in your accounts, so a provider change is a handover rather than a rebuild — which is what APRA's CPS 230 now expects of material service providers. Evening change windows fall in our working day.
Key takeaways
-
Everything we build lives in your repositories and cloud accounts, making exit straightforward
-
In-country disaster recovery is defined in code across Sydney and Melbourne
-
Production personal data stays out of reach of our offshore engineers by design
-
Australian evening change windows sit inside our normal working hours
A common Australian pattern is a platform built by one provider in a way only that provider can run. It works until the contract changes. Since July 2025, APRA-regulated entities have had to treat material service providers under CPS 230, including documented arrangements and exit plans that are actually tested. Non-regulated firms face the same commercial risk without the rulebook.
Our setups are designed so leaving us is uneventful. Pipelines run on your CI service, infrastructure code sits in your repositories, secrets are in your vault, and runbooks describe how to operate everything without us. The exit plan is a document we deliver, not one you have to write once relations sour.
Disaster recovery you can rebuild from a repository
AWS has two Australian regions with availability zones, Sydney and Melbourne. Azure has Australia East, with availability zones, paired with Australia Southeast. That makes fully in-country recovery possible on either cloud, but only if the second region can be stood up reliably. We define networks, identity, data replication and application deployment as code, then rehearse recovery on a schedule. A recovery plan that has never been run is an assumption; one that has been rebuilt from the repository is a capability you can show a board or an auditor.
Pipelines that keep personal data out of reach
Under the Privacy Act, sending personal information to an overseas recipient keeps you accountable for how it is handled. The simplest way to manage that with an offshore team is for the team never to need it. Deployments run through pipeline identities; test environments use synthetic or masked data; production access is requested per incident, time-limited and logged. We document this in the engagement so your privacy officer can assess it, rather than relying on reassurance.
Working with Sydney hours
We share two and a half to three and a half hours with Sydney every afternoon — enough for daily stand-ups and reviews. Our day then continues into your evening, which is when most Australian change windows sit. Releases and infrastructure changes scheduled after 18:00 AEST are carried out by our working team, with a summary waiting the next morning.
Most engagements start with a two-week assessment of one or two representative services. You receive a target design, a gap list against what you run today and a sequenced plan — whether or not we go on to build it. From there, the setup is phased service by service, and you decide at the end whether to operate it yourselves or keep us on a monthly retainer.
Page reviewed Nov 14, 2026. Region and regulatory facts for Australia checked Nov 14, 2026. Rules change — confirm current obligations with your adviser.