Architecture for teamsthat can't afford to go down.
Independent cloud architect. I design and build on AWS, and off it when the case calls for it.
Fixed price, scope agreed before we start. You see the plan before you commit to building. No retainers.
- From $500 to $120 a month, without giving up redundancy
- Infrastructure that holds 3,000 concurrent users
- Costs attributed: which team spends what
Architecture, reliability, cost, and who can touch what.
Design and implementation, at a fixed price.
- 01
Cloud Architecture & Modernization
Moving from rigid systems to architectures that can change without ceremony. Phased, never big-bang.
- Cloud Migration
- Modernization
- Serverless
- 02
High-Availability Design
Resilience designed for the business cost of downtime. Multi-region, fault-tolerant, documented.
- High Availability
- Multi-Region
- Fault Tolerant
- 03
FinOps & Cost Optimization
Full spend analysis and resource inventory. Unused, idle and over-provisioned resources. Reserved Instance and Savings Plan modeling, tagging and cost allocation.
- FinOps
- Cost Optimization
- Savings Plans
- 04
Security & Compliance
IAM review, network exposure, encryption at rest and in transit, Well-Architected alignment.
- IAM
- Well-Architected
- Compliance
Where systems built to ship fast get stuck.
It doesn't hold up in production
It worked in staging. Under real traffic it times out, degrades under load, or goes down entirely — the architecture was never designed for what it now carries.
Nobody can change it safely
What you built to get here was built to ship, not to change. Every new feature costs more than the last, and nobody wants to touch what already works.
Nobody can say what it's spending
Cloud spend climbs every month with nothing to attribute it to. You can't decide what to cut when you can't see what's running.
Understand the objective. Design the path. Build it.
Every project works the same way.
The Objective
If something is already running: what you spend and on what, who can reach what, and what breaks if one piece fails. If you're starting fresh: what it has to do, and what it can cost.
The Path
The design and the steps to get there, written down: what changes, in what order, what it costs. Anything already broken gets listed by how urgent it is.
The Build
I build it, or your team does with the plan in hand. Fixed price either way. Never a retainer.
All of it yours.
Starting from scratch, migrating, or stuck with something that no longer holds up.
- 01
Where you are, and where you're going.
A short document you can act on. Plus what's wrong and how urgent, if something is already running.
- 02
The plan, step by step.
What to do, in what order, what it costs. We walk through it with your team.
- 03
Everything up and running.
Configured, documented, ready to operate.
- 04
The code that builds it.
In your repository. You can rebuild everything from it.
Real format, sample content. Every line of a real assessment carries the evidence and the fix, prioritised from critical to advisory. On AWS and off it.
For agencies & software factories
I work behind your brand — your client never sees a third party. Take on the work you would otherwise turn down. AWS, or Hetzner and Proxmox when the numbers say so. Same fixed price, no retainers.
Get in TouchReady when you are.
Tell me what you want to build, move, or fix.