Cloud platforms

Most of our work runs on one of the three major clouds. We design landing zones, networks, identity and cost controls on AWS, Azure and Google Cloud, and we help teams decide which platform fits a workload instead of defaulting to whichever one they already know.

The pages below explain how we approach each platform: what we build first, which managed services we lean on, where each one tends to surprise teams on cost or security, and when a different platform would be the better choice.

Book a working session Request a quote

Technologies in this category

AWS

AWS is Amazon's cloud platform, with the broadest catalogue of managed services of the three major clouds. We design AWS landing zones, multi-account structure, identity, networking and cost controls, then provision everything through Terraform so it is reviewable, repeatable and cheap to operate.

Microsoft Azure

Microsoft Azure is Microsoft's cloud platform, closely integrated with Entra ID, Microsoft 365 and the Windows ecosystem. We design Azure landing zones with management groups, subscriptions, policy, identity and network topology, then build them with Terraform so governance and cost control are part of the platform from day one.

Google Cloud

Google Cloud is Google's cloud platform, known for BigQuery, managed Kubernetes on GKE and a clean project-based resource model. We design Google Cloud organisations, folders, projects, IAM, networking and billing controls, and provision them with Terraform so data and container platforms run securely and cost stays explainable.

Frequently asked questions

Which cloud platform should a startup choose?

Choose the one your team can operate well and that matches your customers and compliance needs. AWS has the broadest service catalogue, Azure fits Microsoft-centred organisations, and Google Cloud is strong for data and Kubernetes. Switching later is possible but costly, so decide deliberately.

Do you support multi-cloud?

Yes, but we only recommend it when there is a clear reason such as customer requirements, acquisitions or resilience goals. Running two clouds doubles operational surface area, so most teams are better served by one cloud done well.

Can you work inside our existing cloud accounts?

Yes. We start with a read-only audit, agree changes in writing, and apply them through code and pull requests so everything is reviewable and reversible.