Cloud engineering
Portable designs, builds, and runs cloud infrastructure across AWS, Azure, and on-premise environments, including the hosting behind the products we build for government, health, and justice services.
What we do
- Cloud architecture and migration
- Platform engineering
- Infrastructure as Code
- FinOps - cloud cost visibility and optimisation
- Security posture and automated compliance
- Environment provisioning and containerisation
- CI/CD and deployment automation
- Ongoing support services
AWS Rising Star Consulting Partner of the Year, ANZ 2026. Microsoft AI Cloud Partner. ISO 27001 certified.
Most organisations have made their platform decision years ago, and it's rarely a clean one. Portable’s platform engineers work across AWS, Azure and GCP, and into the on-premise environments still doing real work alongside them. Melbourne's tram network runs its real-time data platform on Azure, built on Event Hubs, Functions, and Data Factory. Spotlight Retail Group runs on AWS, where we strengthened governance and security posture through AWS Config. The certifications matter because they mean the engineering is assessed by the platform vendors, not just claimed by us.
You can't optimise what you can't see. Clarity and visibility combat cloud waste and streamline effort.
A digital energy management scale-up serving electricity and water retailers across Australia and New Zealand had a growing AWS bill and no clear view of what was driving it. A collaborative team of their engineers and ours stood up cost dashboards on the AWS Cloud Intelligence framework and had something usable inside a week. It immediately surfaced infrastructure that had been deprecated long ago and was still running, unseen and still charging, and removing that dropped 40% of monthly spend. The same principle governs security and reliability: the posture you can measure is the posture you can improve.
We work inside your team and structure. The engineers who own the platform afterwards are always in the room while it's built.
Portable co-sources teams. At the energy scale-up, lifting cloud cost literacy across their engineers was an explicit aim of the engagement, not a by-product. At Blinq, a co-sourced team worked using an SRE-as-a-coach model, with reliability held across the engineering group rather than owned by a specialist corner of it. We choose well-supported, widely used technology and define infrastructure in code so it stays legible to whoever inherits it. Where that work extends into running platforms day to day, our observability and reliability team leads.
Want to talk through how we might improve your cloud engineering?
