For Brisbane resources, logistics, and digital teams that want a cloud and AI pod on a clock that stays put all year.
Brisbane buyers in resources, logistics, and state digital programs need platform engineers more than a general app shop. The pod is full-time cloud, DevOps, and AI engineers in Vietnam, Australian-managed through Cipher Projects.
Read the DevOps and SRE guide and the AI engineering guide. The operating model sits in the complete guide.
Brisbane stays on AEST (UTC+10) all year. Vietnam is UTC+7. The gap is 3 hours in January and in July.
Sydney and Melbourne lose an extra hour when they move to AEDT. Brisbane does not. If your on-call roster is written for Queensland, say that in the brief so the pod is not staffed for a daylight-saving shift you do not observe.
Industrial and logistics platforms, state service delivery, and the cloud accounts around them. DevOps work is pipelines and environments. Cloud engineering is the account and network design. AI engineering shows up as document and operations workflows, not as a consumer chat product.
Staff the pod for those systems. A mobile feature team is a different hire.
A Brisbane afternoon is a Vietnam late morning all year. Incident bridges and release windows do not need a summer rewrite.
That stability is the practical reason a Brisbane buyer can run SRE follow-the-sun inside the same pod without a seasonal roster change.
The local senior cloud pool is smaller than Sydney or Melbourne. Interview the Vietnam engineers yourself, keep your cloud tenancy, and let Cipher handle employment in Da Nang.
Delivery stays with Cipher Projects.
Brisbane's advantage is a fixed AEST offset to Vietnam, which makes DevOps and SRE rosters easier to write.
Three hours to Vietnam in every month, because Queensland does not use daylight saving.
Cloud and DevOps seats for logistics, resources, and digital services that already have a production account.
Engineers for internal retrieval and workflow automation, scoped to the data you are allowed to use.
Write the roster in AEST once. Do not copy a Sydney AEDT on-call template.
If the Brisbane team does not observe daylight saving, the pod's overlap hours should not change in October. Put that in the operating agreement so nobody 'corrects' the roster to AEDT.
Resources and logistics buyers should name which accounts the pod may touch. Cloud engineering for the corporate platform is in scope. Direct access to operational technology is a separate decision and should not be assumed.
Use Cipher's published starting rates as floors, then price the Brisbane mix: cloud, DevOps or SRE, and AI only if that seat is real. There is no standard savings percentage.
Tell us which Brisbane platform should sit with the pod, and whether the roster is AEST only.
Get a detailed cost estimate for your Brisbane team
30 min with our senior consultants