Why we build with Azure
Microsoft's cloud, set up as code, so your site runs on infrastructure you own, can audit, and can rebuild.


What Azure gives us
The services we use on most builds.
Infrastructure as code
Every resource is Terraform in a repo. Changes are reviewed in a pull request and planned before anything is applied.
Front Door at the edge
One entry point for the site and the CMS, with caching, HTTPS and a web application firewall in front of both.
Static Web Apps
The front end ships as static files, with a preview site for every pull request.
Containers for the CMS
The CMS runs as a Docker image on App Service, so tst and production run the exact same build.
Private by default
The database and storage sit on a private network. The public can only reach the site through Front Door.
Secrets in Key Vault
Passwords and keys live in Key Vault, not in code or pipeline settings. Access goes through Entra ID groups.
Infrastructure as code
Every resource is Terraform in a repo. Changes are reviewed in a pull request and planned before anything is applied.
Front Door at the edge
One entry point for the site and the CMS, with caching, HTTPS and a web application firewall in front of both.
Static Web Apps
The front end ships as static files, with a preview site for every pull request.
Containers for the CMS
The CMS runs as a Docker image on App Service, so tst and production run the exact same build.
Private by default
The database and storage sit on a private network. The public can only reach the site through Front Door.
Secrets in Key Vault
Passwords and keys live in Key Vault, not in code or pipeline settings. Access goes through Entra ID groups.
Infrastructure as code
Every resource is Terraform in a repo. Changes are reviewed in a pull request and planned before anything is applied.
Front Door at the edge
One entry point for the site and the CMS, with caching, HTTPS and a web application firewall in front of both.
Static Web Apps
The front end ships as static files, with a preview site for every pull request.
Containers for the CMS
The CMS runs as a Docker image on App Service, so tst and production run the exact same build.
Private by default
The database and storage sit on a private network. The public can only reach the site through Front Door.
Secrets in Key Vault
Passwords and keys live in Key Vault, not in code or pipeline settings. Access goes through Entra ID groups.
A “processBlock” block hasn't been created
Thinking about Azure?
Tell us what you run today. We'll tell you what moving to Azure would take, and what it would cost to run.