Read-only · open source · AWS · GCP · Azure

Find the money you're leaking in the cloud.

FeckBills scans your AWS, GCP, and Azure accounts for orphaned, idle, and over-provisioned resources — then hands you a ranked, plain-English action list with the exact fix and the £/mo you'll save.

£0/mo

of waste in the demo scan

0

findings, ranked by £

0 writes

read-only, always

zsh — feckbillsinteractive

↑ live, interactive demo — type a command and try it (mock data)

Your money, tracked — not just found once

The hosted console turns every scan into living history: savings reclaimed over time, waste broken down by category, and continuous monitoring across all your accounts.

app.feckbills.com/console

Console

3 projects connected

Reclaimable / mo

£0

Findings

0

Saved to date

£0

Savings reclaimed

last 8 months

By category

GKE over-provisioning£312/mo
requests ≫ usage across 6 workloads
Idle load balancers£128/mo
2 ALBs with no healthy targets
Orphaned disks & snapshots£96/mo
unattached for 30+ days
Unassociated static IPs£41/mo
reserved, billed, unused

Waste, found the world over

Across every region and every cloud — GCP, AWS, and Azure, each in its own colour. Bigger blob, bigger monthly leak.

GCP AWS Azure· illustrative data

Detectors for the waste the consoles bury

We stand on the cloud's own recommendation APIs, then add the "lost resource" detectors they miss — and rank everything by £ impact.

GKE requests ≫ usage

Pods reserving 4 vCPU and burning 0.15. The wedge — priced as reclaimable capacity.

Orphaned disks & snapshots

Volumes nobody deleted, still on the bill 30, 60, 90 days later.

Idle load balancers

ALB/NLB with no healthy targets and near-zero traffic.

Unassociated static IPs

Reserved public IPs, billed precisely because they're sitting idle.

Over-provisioned VMs

Cross-referenced with Compute Optimizer & Recommender — no guesswork.

Idle databases

RDS / Cloud SQL with no connections and a flatline CPU graph.

Commitment gaps

Steady on-demand spend that a Savings Plan or CUD would cut.

Off-hours & spot

Dev/test clusters running 24/7 that could downscale or go spot.

Connected in minutes. Read-only the whole way.

01

Connect read-only

Grant a least-privilege role or run the open-source agent in your own account. No write scopes, ever.

02

Scan

We pull the cloud's own metrics & recommendations, then run our detectors for the waste they miss.

03

Claw it back

A ranked, plain-English action list in £/mo — what to change, the saving, and the risk.

No secrets, no write scopes, no raw resource data leaves your account — only findings. The agent is open source so you can audit exactly what it reads before you connect it.

Find your leak in 60 seconds.

Run the free CLI against your own account, or connect read-only and let the console watch the waste for you.