Price your exit from the bill you already have.
A free AI skill that turns your AWS, Azure, Google Cloud, Oracle or IBM Cloud bill into an indicative bare-metal plan: which servers would replace your workloads, what they would cost each month, the saving after operations effort, and what should stay in the cloud.
- Cost
- Free
- Time
- Minutes
- Your bill
- Stays with you
- AWS. Cost and Usage Report, legacy or CUR 2.0, or the bill by service from the console.
- Azure. A cost details export, amortised if you have it.
- Google Cloud. A billing export as CSV.
- Oracle Cloud. An OCI cost report, or OCI's FOCUS report.
- IBM Cloud. A usage export as CSV.
- FOCUS. Any export in the FinOps Open Cost and Usage Specification. Alibaba Cloud's carries no usage quantities, so it is sized like an invoice.
- PDF invoices. Read by the assistant rather than parsed, so the estimate is rougher. One full month of usage-level data is enough; three months is better.
- 01The short answer. Your bill today, the bare-metal range, and the saving with and without the cost of running the servers yourself.
- 02Named servers. Server models, counts and monthly prices on Hetzner, OVHcloud and Scaleway, like-for-like and right-sized. Six more providers on request.
- 03One-off costs. Setup fees, two months of running both estates, and what moving your data out would cost.
- 04What stays. CDN, DNS, archive storage, data warehouses, proprietary databases and licences, kept at today's cost.
Delivered as a report in Markdown and as a branded web page you can share or print.
-
Step 1
Download the skill
One zip file: Python scripts and a dated price list. It runs offline.
-
Step 2
Add it to your assistant
Upload it as a skill in the Claude apps. In Claude Code, run /plugin marketplace add unicornops/counterweight-skills instead. Any assistant that supports Agent Skills and can run Python works.
-
Step 3
Give it your bill
Attach the export and ask what it would cost on bare metal. It never asks for cloud credentials.
-
Step 4
Read the estimate
A range, not a quote, with every assumption listed and a confidence grade.
Honest about what a bill can't tell you.
An estimate that overstates the saving is worth less than none. So the skill shows the range, counts the cost of running your own servers, and says plainly when bare metal does not pay.
- Two scenarios
- Like-for-like buys a server thread for every cloud vCPU. Right-sized assumes typical utilisation and newer CPUs.
- Operations effort
- At least a quarter of an engineer, at €110,000 a year, scaled to the fleet. Shown with and without, plus a full-engineer case.
- Redundancy
- A spare application server and a replica for every database, in one region, with backups in a second location.
- Contingency
- 10% on bare-metal costs. A warm disaster-recovery site is not priced.
- Prices
- Hetzner and OVHcloud list prices as of 19 October 2026 and Scaleway's as of 24 October, excluding VAT, converted at the ECB rate. The skill runs offline on this bundled list, and refreshes prices only if your assistant has web access.
- What it can't know
- Utilisation, architecture and growth plans. That is what a Teardown measures.
Before you run it
- Do you see my bill?
- No. The skill runs in the assistant you choose, so the bill and the report go nowhere near us unless you send them. Your assistant's provider handles the files under your agreement with them, as it does anything else you give it.
- Is this a quote?
- No. It is an indicative estimate from billing data alone. Provider prices change and must be confirmed at order, and it is not what Counterweight would charge.
- What if bare metal doesn't pay for us?
- It says so. Small or spiky estates, heavy use of proprietary managed services and large spot discounts can all mean little or no saving. A costed exit is still useful at renewal.
- Can we change it?
- Yes. The source is on GitHub under the Apache License 2.0; the Counterweight name and logo are not licensed. Assumptions such as utilisation, operations effort and what stays in the cloud can be set when you run it.
The estimate reads your bill. A Teardown reads your estate.
Two weeks, run by your team with our skills on read-only exports you control. Measured utilisation instead of assumptions, and a costed plan with our signed review that you can take to procurement.