Scope, fee and working days are published on every engagement
An engineer reads one month of your cloud bill and names the five most questionable charges with estimated savings, so waste is cut quickly.
01 Overview
This is a quick read on whether your cloud spend makes sense for what you run. Export one month of billing data, describe the workload briefly, and an engineer picks out the lines that do not fit: an oversized database, cross-zone data transfer, storage left on a default tier, an environment nobody switched off. It is a skim rather than an audit, so it will not catch everything, but it surfaces the obvious waste and tells you whether a deeper review would be worth paying for.
02 Deliverables
6 items03 Outcomes
04 Process
05 Fit & inputs
These inputs are collected through the technical brief in your dashboard after payment. The duration is counted from when they arrive.
06 Answers
The audit analyses three months against live utilisation and models commitments. This check reads one month by eye and reports the headlines.
We tell you so. That is a legitimate result, and it saves you paying for an audit you do not need.
Yes, as well as DigitalOcean and Hetzner.
REL Related
Half a day reading your repository, then a short candid report on its condition and top three risks, before you hire, buy or rewrite.
Written report of 3 to 4 pages, without padding
Fixed fee · GST incl.
₹1,999
Duration
4 working days
One technical question answered in writing with a direct answer and the reasoning, usually within two working days, before you commit money.
One written answer of 300 to 600 words
Fixed fee · GST incl.
₹499
Duration
2 working days
One pull request of up to 400 changed lines reviewed with line-level comments and a merge verdict, so a risky change gets a proper check.
Line-level comments on one pull request of up to 400 changed lines
Fixed fee · GST incl.
₹400
Duration
2 working days
GST included
₹999
Next step