Well-Architected

Cloud engineering thoughts, guides, and lessons learned

Product 13 min read

Cloud Migration Tracker: Licensing Model & Security Architecture

Overview

The Cloud Migration Tracker is a self-hosted platform deployed into the customer’s own AWS account. Unlike SaaS products where the vendor controls the runtime, our licensing system must enforce entitlements on infrastructure we don’t own or operate. This creates a unique challenge: how do you prevent tampering when the customer has root access to the machine?

This post covers the full licensing architecture - from cryptographic validation to frontend feature gating - and the security measures that protect both the license system and the customer’s AWS credentials.

Case Study 13 min read

How We Built a Newsletter System for 15p a Month

Most newsletter platforms charge £16 or more per month for a thousand subscribers. Ours costs about 15p. Here is how we built it, why we made the choices we did, and what it looks like under the hood.

TL;DR for non-techies

If you have subscribed to our blog (or are thinking about it), here is what happens behind the scenes. You enter your email, we send you a confirmation link, and once you click it you are on the list. When we publish a new post, you get an email with a summary and a link. That is it. No tracking pixels, no marketing funnels, no selling your data to advertisers.

Case Study 15 min read

How We Built This Website: Architecture, Security, and Cost

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?

Cloud Strategy 2 min read

What to Expect from a Well-Architected Review

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:

  1. Operational Excellence - how you run and monitor your workloads
  2. Security - protecting your data and systems
  3. Reliability - recovering from failures and meeting demand
  4. Performance Efficiency - using resources effectively
  5. Cost Optimisation - avoiding unnecessary spend
  6. 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.

Get notified of new posts

Enter your email to receive blog updates. No spam, no marketing - just new posts about cloud engineering and DevOps. Unsubscribe anytime.