Technical architecture audit for teams about to scale, migrate, or rewrite.
A five-day review of your API, data, auth, deploy path, and cloud bill. You get a ranked fix list and a walkthrough. I do not change production during the audit.
When to book
- The product works, but p95, error rate, or the invoice is the problem
- You are choosing Cloudflare Workers vs AWS Lambda and need a decision record
- A rewrite has been proposed and nobody has proven the current system cannot be saved
- You want a senior engineer to own the first 90 days of fixes after the report
What I review
- Request paths, latency, and error-prone endpoints
- Auth boundaries and write-path validation
- Data stores, queues, and search ownership
- Deploy, rollback, and observability
- Which work belongs on Cloudflare Workers vs AWS
- Cloud bill items that are drift vs real load
What you get
- Written report with severity tags: fix now, this quarter, or leave it
- One diagram of the current request path and the first change to make
- Decision record: Workers, AWS, or hybrid
- 90-minute walkthrough
- Follow-on build quote at $4,500 or more if implementation is the next step
Not in scope
I do not rewrite the codebase during the audit. I do not need admin on production. I will say if the right move is to stay on AWS. DNS, WAF, WordPress CDN setup, and single Worker scripts are not this engagement.
Questions
Do you only recommend Cloudflare?
No. Hybrid is common: Workers in front for request shaping, validation, caching, or webhooks, with regional data and heavy jobs on AWS.
Will you change production during the audit?
No. I do not rewrite the codebase during the audit. A read-only repo, architecture notes, and a traffic or cost snapshot are enough.
Is this a $750 checklist audit?
No. The audit is $5,000 because it is meant to open a $4,500+ implementation, not to race independents on a cheap PDF.
How fast can this start?
Five business days after access. Remote, with US, EU, and UK hours.
Next step
Email [email protected] or book a call with the stack, the failure mode, and the deadline.