WideOps designed Routines’ target architecture, delivered a Terraform landing zone and GKE setup for the AWS to GCP migration, and stayed on with hands-on support as the team moved workloads off EKS.

The Challenge

Routines needed to leave AWS EKS for Google Cloud without interrupting enterprise orchestration. To move fast without diverting R&D from the product, the team needed a partner to map the Kubernetes estate, design a governed landing zone, turn it into Terraform they could run, and support them through cutover.

The Solution

WideOps designed the architecture and implemented it in Terraform: projects, VPC, IAM, and regional GKE with Workload Identity. We helped adapt workloads from EKS and supported Routines hands on as they executed the migration.

The Result

Routines now run on a Terraform managed GCP landing zone and regional GKE instead of AWS EKS. Development and production projects are live, images flow through Artifact Registry, and the team has an architecture they can operate and extend. WideOps has continued to support Routines through the move.

“Our customers rely on Routines to run their critical workflows on time, every time, so moving off AWS EKS had to be seamless. WideOps gave us a clean, Terraform-based GCP foundation and stayed hands-on with our team through cutover. We now run on an architecture we fully own, understand, and can scale with confidence”

— Yoav Melamed, Co-Founder & CTO, Routines