Capability

Cloud

We build and run cloud platforms that stay up under real load and stay inside the budget someone signed off.

Talk to the Cloud team See what we deliver

Cloud foundations for modern enterprise workloads

Cloud Engineering Practice

Most cloud estates we’re asked to look at grew one project at a time. Each decision made sense when it was made, and the result is an estate that’s hard to secure, hard to cost, and slow to change. We have spent more than a decade on AWS, Google Cloud, and Azure untangling that, and building new platforms that don’t end up the same way. Our engineers hold certifications across all three.

The work is usually some mix of migration, automation, and cost control. We define everything in code, put guardrails in at the organisation level, and make sure the people paying the bill can see where the money goes. The engineers who design the platform stay involved in securing and running it, so decisions don’t get lost between teams.

**Sakura Sky: Cloud Practice Introduction**AI-generated overview

What we deliver

What your team keeps when the work is finished. Each engagement is scoped, so you might only need some of these. They’re in order, because each area builds on the one before it, and AI comes last for that reason.

Foundation

Target architecture and migration plan

A design for where your workloads should run, whether that’s Kubernetes, serverless, or a mix across providers, and a plan for getting them there. We cover containers, virtual machines, and database moves, and plan the cutover so the business keeps running.

Built by Cloud

Read Multi-Cloud Versus Consolidation

Foundation

Residency and sovereignty design

Multi-region designs for data that has to stay in a particular country or jurisdiction. We meet the obligation without breaking the architecture that lets the platform scale, and we can tell you which rules actually apply to which data.

Built by Cloud Security

Read Sovereign Cloud Is an Architecture, Not a Procurement

Foundation

Landing zone in code

Your accounts, networks, permissions, and logging, set up in Terraform, Pulumi, or the provider’s own tooling. Guardrails sit at the top level, so new projects start out compliant and teams can move quickly without asking for sign-off on every change.

Built by Cloud Security Enclave

Read The Sovereign Cloud Question Inside a Bank

Delivery

Build and release pipelines

Pipelines that take code from commit to production the same way every time, with artifact repositories and GitOps behind them. Checks run early, so problems show up in a pull request rather than in production.

Built by Cloud

Read The Mythos Ledger, Part 5: The Resilient Cloud Manifesto

Delivery

Policy checks on every change

Rules for security, reliability, and cost written as code and checked every time something changes. A misconfigured storage bucket gets caught before it ships, instead of during an outage or high stress situation.

Built by Cloud Security

Read Multi-Tenant Agentic AI on Google Cloud: A Production Walkthrough

Delivery

Observability and runbooks

Logs, metrics, and traces wired into the platform from the first deployment, with alerts that mean something and runbooks your on-call team can follow at three in the morning.

Built by Cloud

Read Launch Day Is Every Day

Cost

Cost visibility and commitment plan

A clear view of what you spend on compute, storage, and data transfer, broken down by team and workload. From there we plan commitments and resize whatever is bigger than it needs to be.

Built by Cloud

Read Data Costs: Are You a Victim of Your Own Success?

Cost

Limits on AI and GPU spend

GPU time and per-token AI costs can grow faster than anything else on the bill. We put hard limits in place, so one runaway workload can’t use up a month’s budget in a weekend.

Built by Cloud

Read Tollgate: Open-Source Hard Limits for LLM Spend

Platform for data and AI

Data and AI platform integration

Warehouses, streaming, and managed AI services connected to the same foundation, with identity, network policy, and lineage already in place. The Data & AI team can start building straight away instead of waiting for infrastructure.

Built by Cloud Data & AI

Read Peak Load Is the Steady State

How we work

How each capability is designed, built, managed, and governed, and which of our service lines does each part. Most engagements start with a short assessment.

CapabilityDelivered through	DesignProfessional Services: Assessment & Roadmap	BuildProfessional Services: Delivery Engagement	ManageManaged Services: co-managed, hybrid, or fully managed	GovernManaged GRC: evidence for EU, US, and international frameworks
Foundation	Design Where you are, where you want to be, and a roadmap between the two. Or a sprint that ends with a working landing zone. Accelerate: Cloud Migration Kickstart	Build Architecture, migration, and landing zone. Modernisation & Migration	Manage We run it day to day, under SLAs. CloudOps & Cost Optimisation	Govern Controls mapped to a framework where that helps. INTLISO 27001USNIST CSF 2.0
Delivery	Design A look at how releases work today.	Build Infrastructure as code, pipelines, and policy checks. Cloud Architecture & Platform Engineering	Manage We keep pipelines and tooling current. Platform Engineering & DevOps Enablement	Govern Every change is logged and checked, which gives auditors a clear trail. Continuous Attestation & Audit Liaison
Cost	Design A spending baseline by team and workload.	Build Cost allocation, commitments, and rightsizing.	Manage Regular cost reviews and optimisation. CloudOps & Cost Optimisation	Govern
Platform for data and AI	Design A sprint that gets the data platform running. Accelerate: Data Platform Build	Build Built together with the Data & AI team. Data & AI	Manage We run the pipelines as a service. DataOps & Pipeline Orchestration	Govern Lineage and access records, shared with the Data & AI team.