A human proxy for leaving the cloud
Revival Engineer is a human proxy: a person you bring in to remove cloud computing where it is not justified. I do the work. Your name goes on it.
Like ghostwriting, for infrastructure
A ghostwriter writes the book, and the author is credited. Revival Engineer works the same way. I do the analysis, the planning, and the engineering, and you present the result to your team, your leadership, or your board as your own work.
There is no book. The product is the work itself: less cloud where it was not justified, delivered under your name.
Who uses a proxy
- Engineering leaders who have been asked to cut cloud spending.
- Infrastructure, platform, and site reliability engineers who know the bill is too high but can’t spare the time to fix it.
- CTOs who want the savings without a consultancy’s name on the slides.
What I do
- Map every line of the cloud bill to a workload and an owner.
- Run the five-question justification test on each workload.
- Plan the move: what leaves the cloud, where it goes, and in what order.
- Do the engineering to move it.
- Write up the before and after, in cost, performance, and risk, for you to present.
The contract sets out exactly which of these I do for you.
How it works
- You apply by email with a short note about you and what runs in your cloud.
- You submit proof of your annual compensation. The fee is calculated from it.
- We both sign the contract. No work is delivered before it is signed.
- I do the work as your proxy, with the access and information you provide.
- You deliver the result under your name.
Your name, not mine
The credit is yours. Revival Engineer is not named on the work, and the contract sets out confidentiality and ownership before any work is delivered.