We practice what we preach. This website is built and deployed using the same principles, tools, and frameworks we recommend to our clients. Here’s a complete breakdown of how kaizenconsultancy.io is architected, secured, deployed, and what it actually costs to run.
TL;DR for non-techies
This website costs about a pound a month to run. It’s hosted on Amazon’s cloud infrastructure, loads fast anywhere in the world, is secured to enterprise standards, and can be rebuilt from scratch in 10 minutes. Every part of it is automated - no manual steps, no clicking through dashboards, no room for human error. We built it this way because it’s exactly how we’d build cloud infrastructure for a client. If we can’t do it for our own site, why would you trust us to do it for yours?
If you’re still provisioning cloud resources by clicking through the AWS console or Azure portal, you’re building on sand. Every manual step is a risk - unrepeatable, undocumented, and impossible to audit.
The problem with manual provisioning
We’ve seen it dozens of times across a decade of cloud engineering. An engineer builds a VPC by hand, configures security groups from memory, and deploys an application with a series of CLI commands they half-remember. It works. Until it doesn’t.
A Well-Architected Review isn’t an audit. It’s not a pass/fail exam. It’s a structured conversation about your cloud workloads that identifies risks, highlights improvements, and gives you a clear plan to make things better.
How it works
The review is built around six pillars:
Operational Excellence - how you run and monitor your workloads
Security - protecting your data and systems
Reliability - recovering from failures and meeting demand
Performance Efficiency - using resources effectively
Cost Optimisation - avoiding unnecessary spend
Sustainability - minimising environmental impact
For each pillar, we work through a series of questions about your architecture, processes, and practices. It’s collaborative - we’re not there to judge, we’re there to find opportunities.
One of the first questions we get asked is “how much will it cost to move to the cloud?” The honest answer is: it depends. But that’s not very helpful, so here’s a more practical breakdown.
The three types of cost
Cloud migration costs fall into three buckets:
1. The migration itself - the work to plan, build, and move your workloads. This includes architecture design, landing zone setup, application assessment, and the actual migration execution. For most organisations, this is the biggest upfront cost.