Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

Cloud practice

Cloud and platform engineering that ships, scales and pays for itself.

We build secure landing zones, migrate workloads off data centres and VMware, run Kubernetes upgrades on EKS, AKS, GKE and OKE, automate delivery with CI/CD and Terraform, and cut cloud bills with evidence instead of guesswork.

Services
5
Engagements
Fixed scope, fixed fee
Who does the work
Senior engineers
LANDING ZONE · POLICY AS CODEIdentityPolicyLoggingNetworkShared servicesProductionNon-productionKUBERNETES · ROLLING UPGRADEnode pool 1node pool 2node pool 3node pool 4ObservabilityFinOps

AWS, Azure, Google Cloud and OCI. Kubernetes, DevOps, Terraform, observability and FinOps.

All platforms
  • AWS
  • Azure
  • Google Cloud
  • OCI
  • Kubernetes
  • EKS
  • AKS
  • OKE
  • Terraform
  • OpenTofu
  • Argo CD
  • Helm
  • GitHub Actions
  • Prometheus
  • Grafana
  • OpenTelemetry
  • OpenCost
  • Karpenter

Point of view

A landing zone is a set of decisions about identity, network, policy and cost. We make them once, write them as code, and hand over a platform your own team can run without us.

5 services, each with a fixed-fee entry point.

AWS, Azure, Google Cloud and OCI. Kubernetes, DevOps, Terraform, observability and FinOps. Each is scoped after a free 30-minute review, and the assessment fee is credited to the project.

01 / 05

Cloud Landing Zones, Security & Governance

Most cloud problems start with a weak foundation: shared accounts, flat networks, admin keys on laptops and no audit trail. We design and build landing zones that let teams move fast inside guardrails, as code you own.

Sound familiar?

  • Everything runs in one or two accounts or subscriptions, and nobody is sure who can change what.
  • A security questionnaire or SOC 2 audit asked for logging, encryption and least-privilege evidence you cannot produce quickly.
  • You are adding a second cloud and want the same controls on both.

You receive

  • Current-state findings and target design
  • Terraform modules for the landing zone
  • Identity and guardrail policies

Landing Zones, Security & Governance Starts with: Cloud foundation review

02 / 05

Cloud Migration & VMware Exit

Licensing changes and hardware refresh cycles are forcing decisions about where workloads should live. We assess the portfolio honestly, model the run cost, then move applications in rehearsed waves to the cloud that fits each one.

Sound familiar?

  • A VMware renewal quote arrived and the board wants options before signing.
  • A data centre contract or hardware refresh date is forcing a decision.
  • A lift-and-shift was planned but nobody has modelled what the cloud bill will be.

You receive

  • Application portfolio with strategy and target
  • Run-cost model per target
  • Wave plan and dependency map

Cloud Migration & VMware Exit Starts with: Migration assessment

03 / 05

Kubernetes & Platform Engineering

Kubernetes ships a new minor version roughly every four months and managed services retire old ones on a fixed calendar. We keep clusters supported, build platforms developers actually like using and remove the toil around them.

Sound familiar?

  • EKS clusters are paying for extended support, or will be auto-upgraded when it ends.
  • AKS and GKE will upgrade clusters on their own schedule if you do not, and deprecated APIs will break on the way.
  • Every team built its own cluster and pipeline, and nobody can upgrade them all.

You receive

  • Cluster inventory with support dates
  • Deprecated API and add-on report
  • Upgrade runbooks and rehearsal results

Kubernetes & Platform Engineering Starts with: Cluster upgrade readiness review

04 / 05

DevOps, Infrastructure as Code & Observability

Manual deployments, drifted infrastructure and dashboards nobody trusts slow every team down. We automate delivery end to end, put infrastructure under version control and give you observability that answers questions during an incident.

Sound familiar?

  • Releases need a person, a checklist and a quiet afternoon.
  • Infrastructure was built by hand in the console and nobody can rebuild it.
  • Terraform state is fragile, modules are copied between repos and plans are scary.

You receive

  • Pipeline and IaC assessment
  • Reusable pipeline templates
  • Terraform/OpenTofu modules and state setup

DevOps, IaC & Observability Starts with: Delivery pipeline review

05 / 05

FinOps & Cloud Cost Optimization

Most cloud bills carry waste nobody has time to chase: idle resources, oversized databases, extended-support fees and AI experiments left running. We find it, fix it and set up the reporting so it stays fixed.

Sound familiar?

  • The cloud bill grew faster than revenue and nobody can say why.
  • You pay RDS, EKS or Cloud SQL extended-support charges for versions that should have been upgraded.
  • GenAI and GPU costs appeared on the bill without an owner.

You receive

  • Savings opportunities ranked by value and effort
  • Implemented changes with measured savings
  • Commitment purchase plan

FinOps & Cost Optimization Starts with: Cloud cost review

Cloud & Platform Engineering dates to plan around

Live day counts to published vendor dates. Full calendar Check your stack

  1.   days Amazon EKS Kubernetes 1.31 leaves EKS extended support; remaining clusters are auto-upgradedKubernetes & Platform Engineering
  2.   days Azure AKS Kubernetes 1.34 reaches end of life on AKS (community support)Kubernetes & Platform Engineering
  3.   days Amazon EKS Kubernetes 1.34 ends standard support on EKS; extended-support billing startsKubernetes & Platform Engineering
  4.   days Google GKE Kubernetes 1.34 ends standard support on GKEKubernetes & Platform Engineering

What is driving demand right now

Backed by public sources.

  1. Licence cost

    VMware and database licence exits

    Renewal shocks are pushing teams to move workloads and databases to cloud-native and open-source engines.

    Cloud Migration & VMware Exit Source: CloudBolt research

  2. Cost pressure

    Cloud and AI spend under review

    Workload optimization and waste reduction lead the State of FinOps 2026, and AI cost is now in scope for most FinOps teams.

    FinOps & Cost Optimization Source: FinOps Foundation

How we deliver Cloud & Platform Engineering work

The same five phases on every engagement in this practice, so you always know what happens next and what you hold at the end of each phase.

  1. 01

    Discover

    Accounts, subscriptions, clusters, pipelines and the bill, through read-only roles and billing exports.

  2. 02

    Assess

    Security baseline, reliability, cost drivers and support dates measured against well-architected practice.

  3. 03

    Design

    Target architecture and a backlog as Terraform, GitOps and pipeline changes, with a fixed quote.

  4. 04

    Build and migrate

    Delivered as pull requests in your repositories, reviewed and reversible.

  5. 05

    Operate and hand over

    Runbooks, dashboards and alerts your team can use, plus an optional managed reliability service.

Outcomes we measure

How we frame the business case. We agree the baseline and the measure in the statement of work and report against them. We never quote invented benchmarks or other clients' results. Building the business case

  1. Spend against baseline

    Monthly cloud spend by team or product against the baseline agreed at the start, from your billing export.

  2. Cost allocation

    The share of spend that is tagged and allocated to an owner.

  3. Delivery performance

    Deployment frequency, lead time, change failure rate and time to restore (the DORA measures), before and after.

  4. Support status

    Clusters, node images and managed services inside standard support, tracked against published dates.

  5. Security baseline

    Findings from the agreed baseline (for example CIS benchmarks) open at the start and closed at hand-over.

Proof by depth

Judge the depth before the first call.

No invented statistics or borrowed logos. Instead, the documents themselves: the same structure we deliver, filled in for fictional systems so you can judge the depth before you talk to us.

All samples and checklists Engagement examples

Platforms we work with

Independent and vendor-neutral. Names are trademarks of their owners; listing does not imply partnership. All platforms

Cloud platforms

  • AWS
  • Microsoft Azure
  • Google Cloud
  • Oracle Cloud (OCI)

Containers, DevOps & observability

  • EKS
  • AKS
  • GKE
  • OKE
  • Terraform
  • OpenTofu
  • GitHub Actions
  • GitLab CI
  • Argo CD
  • Helm
  • Prometheus
  • Grafana
  • OpenTelemetry

Questions about Cloud & Platform Engineering

Straight answers on scope, fees and how we work. Anything else, ask us.

Ask a question

Which clouds do you work with?

AWS, Microsoft Azure, Google Cloud and Oracle Cloud Infrastructure, plus Kubernetes on all of them and on premises.

Are you an AWS, Microsoft or Google partner?

No. We are independent and do not resell cloud capacity. That means we cannot offer provider funding programs that require partner status, but our advice is not tied to any provider.

Do you build with Terraform?

Yes, Terraform or OpenTofu by default, committed to your repository so you own and can change everything.

Can you help reduce our cloud bill?

Yes. The FinOps cost review is fixed fee, and we do not take a percentage of savings.

Start with a free 30-minute review.

Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.