Home › Free tools › Godwit Scan
Free Cloud Cost and Network Assessment DemoGodwit Scan
Our assessment engine for cloud cost reviews, network audits and migrations, running here on an estate we made up. Choose what it is allowed to read, press Run, and watch which answers that access does and does not buy you.
- Costs
- Nothing
- Runs in
- Your browser
- Analytics
- None
- Covers
- Cloud, network
The estate is invented. Everything else is not. The scanner, the checks, the rate cards and the arithmetic are the ones we would run on yours, and the permission list it asks for is generated from the scanner's own manifest rather than written by hand for a slide.
Nothing has run yet, and that is deliberate. Pick a provider and an estate, choose what the scanner may read, and press Run the assessment.
It reads only what the switches allow. Take a switch away and it will not guess at what it can no longer see: it will tell you which answers that access would have bought.
What it is costing, and what to do
What to do, in order
Every finding
What you have
Collected read-only. Nothing was changed, and nothing here is a recommendation yet: this is only the shape of the estate.
Cloud infrastructure
Network
How it is joined up
Offices, the links between them, and the cloud. Drawn from what was collected rather than from a diagram somebody maintained by hand, so if this looks wrong, that is itself a finding.
The equipment behind it
How it is being used
Each mark is one server, disk or link. This is the evidence behind the word "idle": you can see where every threshold was drawn and judge whether it is fair.
And on the network
What it could not see
What it was allowed to do
It read your configuration. It could not read your data, and it could not change anything. Every step below is a switch in the bar at the top of the page: change one and the numbers will not move until you press Run.
The exact permissions
What it never asks for.
| Not requested | Why not |
|---|
The estate is synthetic. The scanner, the checks, the rates and the arithmetic are real.
- Take access away, one switch at a time. Remove metrics and watch it stop claiming anything is idle. It says what it can no longer tell you instead of guessing, which is the only reason to believe the figures it does report.
- Switch to the well-run estate. Same size of company, run properly. Every check runs and it reports nothing. A tool that cannot say “leave this alone” will always find you work.
- Switch between cloud providers. Different checks, different rate card, different vocabulary. The storage advice deliberately runs the opposite way on each, because the two providers price disks in opposite directions.
- Open “How it joins up”. Every finding there needs a fact from the cloud and a fact from the network at the same time, which a cloud-only or network-only review would miss.
What it reads, and what it refuses to
On a real engagement the cloud half is a read-only role covering configuration and metrics. It never asks for object contents, table rows, queue messages or secrets, and the report lists the specific permissions we decline to request alongside the ones we do. The network half reads exported device configurations and an export from whatever already polls your network. No device credentials, no SSH, no agent, nothing installed.
We do not ask for the cloud provider's own blanket read-only role. It would cover everything in one click and would also permit reading your storage objects and database rows. A tool that needs a disk's type has no business reading its contents.
Where this sits in the work
It is the first artefact of three different engagements, and it is the same tool in each.
- A cloud cost review. The findings, and the order to do them in. The cloud checks are the ones published in our cloud bill checklist, priced from a dated rate card.
- A network assessment. Circuits against measured utilisation at the ninety-fifth percentile, default services still listening, and hardware and firmware past support.
- A migration, before and after. Before, it sizes what you are about to move. Afterwards it catches what the move left behind: a circuit still provisioned for traffic that no longer runs over it.
What the real thing gives you
A report in the shape you just read: what it is costing, what to do in order, the evidence behind every figure, and an explicit list of what the tool could not see. Every rupee traces to a dated rate. Anything we cannot source is marked unsourced rather than dressed up, and the findings we would leave alone are listed as such.
What you walk away with
Yours to keep, and to hand to anyone else, including a provider that isn't us.
Talk to us about thisEvery change with its rupee figure, the effort, the risk, and whether it needs a maintenance window.
What we would leave alone, and why. Usually the more useful half.
The call we made, the value we saw, and the dated rate we priced it at.
What the tool could not see, stated rather than left out. Silence would read as a clean bill of health.
Asked before you ask
The ones that come up on nearly every first call.
Talk to us about thisIs this the real scanner or a mock-up?
The real one. The page is generated by the same code that produces a client report, running the same checks against a synthetic estate, and every figure on it was computed rather than typed. What is invented is the estate.
Why can I not copy or print the report?
Because the assessment is the thing we sell, and a page that invites you to lift the whole report has given the product away. We would rather be straight about that than pretend it is a technical limitation. View-source still works, and so does a camera. If you want these findings for your own estate, that is an engagement, and you keep the report. The rest of this page copies normally.
Does it send my data anywhere?
There is nothing to send. Every scenario on the page was computed in advance and shipped with it, so the report makes no network requests at all and holds no client data of any kind. Like our other free tools, the page carries no analytics.
Our estate is bigger and messier than that. Would it cope?
The synthetic estate is deliberately mid-market: around sixty servers, four sites, thirty network devices. Larger estates mostly produce longer lists rather than different findings. Where it would struggle is many accounts or many regions, and we would tell you that before quoting rather than after.
Can we run it ourselves?
Not today. In an engagement we run it against read-only access you grant and can revoke, and the report is yours. Self-service is on the roadmap and we are not going to pretend it is ready.
Not sure this is the one you need?
Tell us the symptom, not the service, and we'll say which of these applies, or that none of them do. A reply within one working day, from someone technical.
The rest of what we do
Most engagements start with one of these and grow into another.
