FeckBills – Find the money you're leaking in the cloud

SteveChurch1 pts0 comments

feckbills.com — find the money you're leaking in the cloud

Mission Control/ waste-ops deck<br>statuslivemoderead-onlycloudgcp · gkeutc--:--:--

GKE rightsizing0<br>Idle VMs3<br>Orphaned disks1<br>Stale snapshots1<br>Stopped-VM disks2<br>Idle static IPs0<br>Least-privilege · no write scopes · open-source agent.

Live demo · mock data<br>Find the money you’re leaking in the cloud.<br>A read-only scan of your AWS, GCP & Azure accounts for orphaned, idle and over-provisioned resources — ranked, priced in £/mo, with the exact fix.

Reclaimable / mo<br>£1,186<br>scanning…

Findings

Write actions

Run a scanOpen consoleFree CLI

Command lineinteractive<br>$ ▋

snapshot-44d2749e£272/mo<br>Snapshot, source disk gone (264d)

api-vm-boot£13/mo<br>Disk on a TERMINATED VM

pvc-210bce88£273/mo<br>Unattached 50 GiB PD, 34d

vm-ingest-f33c£9/mo<br>Idle VM (e2-medium, peak 3% CPU)

ml-vm-boot£297/mo<br>Disk on a TERMINATED VM

vm-batch-116a£72/mo<br>Idle VM (e2-standard-4, peak 4% CPU)

vm-checkout-b18a£250/mo<br>Idle VM (n2-standard-4, peak 1% CPU)

Only findings leave your account — never raw data or secrets.

§ 01 / The Console

Your money, tracked — not just found once<br>Every scan becomes living history: savings reclaimed over time, waste by category, continuous watch across all your accounts.

app.feckbills.com/console

§ System / Overview

3 projects<br>Reclaimable / mo

£0

Findings

Saved to date

£0

Savings reclaimed<br>last 8 months

Latest scan<br>live<br>runway/api @ acme-prod£312/mo<br>GKE requests ≫ usage (9% CPU)

app/prod-alb/3f2a9c£128/mo<br>Idle load balancer, no healthy targets

vol-0a3f81d2£96/mo<br>Unattached 100 GiB volume, 34d

eipalloc-07f88f3c£41/mo<br>Unassociated Elastic IP, billed idle

db-ingest-8b7b£38/mo<br>RDS idle, 0 connections 14d

§ 02 / Namespace X-ray<br>See which namespaces actually earn their keep<br>For GKE we map every namespace's real activity — used CPU, network, and request traffic — into a heatmap. Spot the ones reserving compute but doing nothing, and claw the spend back. Flagged, never auto-killed: you decide.

Namespace activity · acme-prod<br>used CPU over 14d

api<br>live£412<br>web<br>live£286<br>workers<br>live£198<br>ingest<br>live£154<br>search-legacy<br>idle£182<br>billing-v1<br>idle£130<br>cert-manager<br>infra£28

2 idle namespaces · £312/mo reserved compute doing nothing.

§ 03 / Detector Array<br>Detectors for the waste the consoles bury<br>We stand on each cloud's own metrics & recommendation APIs, then add the "lost resource" detectors they miss — and rank everything by £ impact.<br>AWS · GCP · Azure

01<br>GKE requests ≫ usage<br>Pods reserving 4 vCPU and burning 0.15 at P95 — the wedge, priced as reclaimable capacity.

02<br>Unattached persistent disks<br>Disks nobody deleted — incl. leaked pvc-* volumes — still on the bill 30/60/90 days on.

03<br>Reserved-but-idle static IPs<br>External IPs you're billed for precisely because they sit unattached.

04<br>Orphaned & stale snapshots<br>Snapshots whose source disk is gone, or quietly ageing past 90 days.

05<br>Disks on stopped VMs<br>Persistent disks still billing on TERMINATED Compute Engine instances.

06<br>Idle Compute Engine VMs<br>Running VMs with near-zero CPU over the window (gke-* nodes excluded).

§ 04 / Global Sweep

Waste, found the world over<br>Every region, every cloud — GCP, AWS and Azure, each in its own colour. Bigger blob, bigger monthly leak.

GCP AWS Azure· illustrative data

§ 05 / Connect Sequence<br>Connected in minutes. Read-only the whole way.

01Connect read-only<br>Grant a least-privilege role or run the open-source agent in your own account. No write scopes, ever.

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

03Claw it back<br>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.<br>Run the free CLI against your own account, or connect read-only and let the console watch the waste for you.<br>Open the consoleRead the source

idle cloud waste source live find

Related Articles