← cd ../services
07 / cloud/deploy● 26 migrations doneAWS · GCP · Azure

Infra that stops waking you up.

AWS, GCP and Azure done properly. Terraformed, CI/CD-piped, cost-tuned, monitored. Sydney-region data residency, IRAP-ready patterns, and a runbook your on-call actually reads.

AWSGCPAzureTerraformKubernetes
Uptime99.99%↑ 0.04
Deploy time4.2 min↓ 68%
$ what we ship

Six shapes of cloud engagement.

Whether you're going from laptop-to-prod for the first time or trimming a five-figure AWS bill, pick the shape that matches. Every engagement leaves you with Terraform, docs, and someone who can pick it up.

01
Greenfield cloud setupFresh AWS/GCP/Azure org — Landing Zone, SSO, guardrails, budget alerts, Terraform state, one production & one staging account before you deploy a thing.
02
Migrations from on-prem or HerokuHeroku, DigitalOcean, on-prem VMs → AWS/GCP with zero-downtime cutover, data reconciliation, and rollback in hand.
03
CI/CD pipelinesGitHub Actions, GitLab CI, or Azure DevOps. Preview environments per PR, gated production deploys, automated smoke tests, one-click rollback.
04
Kubernetes, done rightEKS/GKE/AKS with GitOps (ArgoCD or Flux), sensible RBAC, cluster autoscaler, cost limits, and pipelines that don't require a PhD to debug.
05
Cost optimisationRight-sizing, reserved / committed spend, unused resource sweep, egress redesign, budget alerts. Typical AWS bill reductions: 20–40%.
06
Compliance & hardeningIRAP-aligned AWS patterns, ISO 27001 controls, PCI-DSS scoping, SOC 2 readiness. We do the boring paperwork so your audit is quiet.
$ our process

From audit to autopilot — six phases.

Every engagement runs the same six phases, in the same order. Fixed scope, fixed timeline, fixed price — agreed before we touch your accounts.

  1. 01

    Audit & blueprint

    Week 1

    Read-only IAM access, full inventory, bill breakdown, risk register. You get a diagram of what you actually have — often the first honest one that's ever existed.

    • Read-only account audit + resource inventory
    • Bill deep-dive by service, tag & environment
    • Risk register (security, cost, availability, compliance)
    • Fixed-price proposal, week-by-week milestones
  2. 02

    Landing zone & guardrails

    Week 2 – 3

    Multi-account structure (dev / staging / prod / logs / audit), SSO wired to Google Workspace or Azure AD, budget alerts, SCPs, tagging policy — the boring 20% that saves the next 80%.

    • Multi-account structure with dedicated log & audit accounts
    • SSO + break-glass root credentials vaulted
    • Budget alerts per account + Slack notifications
    • Tagging policy + automated tag enforcement
  3. 03

    IaC & environments

    Week 3 – 5

    Terraform (or CDK, if you insist) modules for VPC, RDS, cache, queues, secrets. State in S3+DynamoDB or Terraform Cloud. Prod and staging identical, differ only in size.

    • Terraform modules covering VPC / RDS / cache / queues
    • Remote state with locking + drift detection
    • Secrets in AWS Secrets Manager / Vault, rotated
    • Staging environment identical to prod, shrunk
  4. 04

    CI/CD & deploys

    Week 5 – 7

    GitHub Actions or GitLab CI with preview environments per PR, gated production deploys, one-click rollback, automated smoke tests post-deploy. Deploy time under 10 minutes.

    • Preview environments spun up per PR, torn down on merge
    • Manual approval gate for production
    • Smoke tests + automated rollback on failure
    • Deploy metrics wired to Slack + Datadog
  5. 05

    Observability & SLOs

    Week 7 – 9

    OpenTelemetry across the stack, Datadog or Grafana Cloud dashboards, PagerDuty rotations, SLOs and error budgets your team can actually reason about.

    • OpenTelemetry traces, metrics, logs — one pipeline
    • Golden-signal dashboards per service
    • PagerDuty rotations + runbook links in alerts
    • SLO definitions + error budget tracking
  6. 06

    Cutover & 30-day support

    Week 9 → 13

    Cutover in a low-traffic window, rollback plan tested first. On-call with your team for 30 days: alert tuning, cost tuning, whatever the first month throws up.

    • Staged traffic shift + rollback plan tested pre-cutover
    • Pair on-call with your team for 30 days
    • Alert tuning + cost tuning week 3
    • Handover doc + recorded runbook walkthrough
$ what you own

What lands in your hands.

Final milestone paid, everything transfers. Terraform, cloud accounts, secrets, docs — no vendor lock-in, no rent-seeking.

Terraform monorepo

Every module we wrote, in your GitHub org, CI-linted and drift-detected on every push.

Cloud accounts under your billing

AWS Organizations / GCP org / Azure tenant registered under your business, your card, your admins.

Architecture diagrams

C4-model diagrams, network topology, data-flow diagrams — SVG source, checked into the repo.

Runbook & DR playbook

Deploy runbook, incident-response playbook, RTO/RPO targets, tested restore-from-backup drill.

Observability dashboards

Datadog / Grafana / CloudWatch dashboards, alert definitions, SLO tracking — as code, not clicked.

Cost report + tuning plan

Baseline bill, tuned bill, ongoing right-sizing recommendations. Typical savings called out with confidence.

$ tech stack

The stack we reach for.

Boring on purpose. Every tool here is battle-tested, actively maintained, and hire-able for anywhere in Brisbane, Sydney, Melbourne, Auckland or Wellington if you want to bring it in-house later.

Clouds
  • AWS
  • GCP
  • Azure
  • Cloudflare
  • Fly.io
IaC
  • Terraform
  • OpenTofu
  • Terragrunt
  • AWS CDK
  • Pulumi
Orchestration
  • Kubernetes (EKS/GKE/AKS)
  • ECS Fargate
  • Cloud Run
  • ArgoCD
CI/CD
  • GitHub Actions
  • GitLab CI
  • Azure DevOps
  • Buildkite
Observability
  • Datadog
  • Grafana Cloud
  • OpenTelemetry
  • Sentry
  • PagerDuty
Security
  • AWS Config
  • Prowler
  • Vault
  • Snyk
  • Trivy
$ timeline & investment

Rough shape of a cloud engagement.

Real numbers from the last two dozen migrations. Actual pricing lands after audit — but this is the sensible band to plan around.

Typical timeline
00 weeks
CI/CD pipeline only: 2–3 weeks. Landing zone + Terraform: 4–6 weeks. Full migration + K8s + observability: 10–14 weeks.
Investment (AUD)
$0k – $0k
Fixed price, three milestone payments. Retained on-call from $650/mo, or hand-back after 30-day support with runbook.
0
Migrations completed
0%
Avg deploy-time saved
0%
Post-migration uptime
0 min
Avg first reply
$ questions

The stuff every client asks first.

If your question isn't below, we'll answer it on the discovery call. No sales pitch — just an honest read on whether we're the right shop.

AWS, GCP or Azure — which should I choose?
AWS if you want the deepest catalogue and best AU regions. GCP if you're doing serious data/AI work — BigQuery + Vertex are hard to beat. Azure if your org already runs on Microsoft (Entra, Office 365, Dynamics). We'll tell you honestly which suits your team, and we won't lock you in to whichever we know best.
Do we need Kubernetes?
Probably not. K8s is worth it once you're running 5+ services, need fine-grained autoscaling, or have multi-team platform needs. For a single Node/Python API, ECS Fargate, Cloud Run, or Fly.io will save you months of complexity. We'll push back if you ask for K8s and you don't need it.
Can you reduce our AWS bill?
Usually yes — 20–40% is a normal first pass, from right-sizing, reserved/committed spend, deleting unused resources, redesigning egress, and switching to Graviton/ARM where sensible. We charge a fixed fee for the review, not a percentage of savings, so incentives stay clean.
Do you work with regulated data (IRAP, PCI, health)?
Yes — we've built IRAP-aligned patterns on AWS Sydney/Melbourne regions and Azure Australia Central. We don't self-certify your compliance — that's an auditor's job — but we build to the controls and hand you the evidence pack.
Who owns the AWS account?
You do, always. Registered under your business, billing on your card, root credentials in your vault. We're added as SSO users with time-bound admin. If you fire us tomorrow, revoking our access is one click.
What happens after the engagement ends?
Two options: hand-back (you get the Terraform, runbook, dashboards, and take over — we're on Slack for questions for 30 days) or a retained on-call plan from $650/mo covering alerts, dependency updates, cost reviews, and quarterly DR drills.
Do you work outside Brisbane?
Yes — every engagement runs remote-first from our Brisbane studio, with on-site availability across Sydney, Melbourne, Canberra, Perth, Adelaide, Auckland and Wellington. For enterprise or gov engagements we run embedded weeks on-site during audit and cutover.

Ready to stop firefighting?

Free 30-minute discovery call. We'll reply within 1 business day.