Product Updates
v2.9.21: Local GPU and Kubernetes Waste Signals
GPU and Kubernetes waste is expensive, but the useful evidence is usually split between runtime tools, cluster objects, and the monthly bill.
Knowledge Hub
Cloud waste guides, product notes, and operating playbooks.
The current site carries 69 published articles with a simplified commercial product message and current navigation.
Product Guides 10Product Updates 10Whitepapers 18Industry Intelligence 10Incident Series 6Founder Notes 12Article 2Guide 1
Incident Series
The Boss Saw the Cloud Bill and Asked About Crypto Mining
Jack thought the bill was a reporting mistake until Rose pulled up the resources nobody had checked in weeks.
Incident Series
Ghost Resources Nobody Owned
The hardest waste to fix was not hidden by the cloud provider. It was hidden by missing ownership.
Product Guides
A Weekly Cloud Governance Rhythm That Holds
A weekly cloud review only works when the meeting starts with a short list of resources, owners, and decisions.
Product Guides
Taxonomy First, Trends API Second
Before dashboards help, teams need to agree on what each finding means and how it should be reported.
Incident Series
Three Expensive Cloud Waste Incidents
These three incidents were expensive because nobody saw the waste early enough, not because the fixes were complicated.
Product Guides
Accounts, Proxies, Notifications, and Scan Results
This part covers the setup details that usually break first: accounts, proxy routing, notifications, and scan result handling.
Product Guides
How to Choose the First Scan Target
The first scan should be small enough to finish and specific enough to teach the team what good evidence looks like.
Product Guides
Core Setup for a First Useful Scan
This is the shortest path from a fresh install to a first scan that your team can actually review.
Product Guides
How to Read the Main Product Views
The four main views answer different questions; reading them in the wrong order creates noise.
Article
AI Evidence Skills for Local Scan Reviews
These skills are meant to help teams explain scan evidence without sending cloud credentials or raw findings to a SaaS workflow.
Founder Notes
Operator Feedback That Changed Recent Releases
Recent releases changed because operators kept pointing at the same rough edges: proxy setup, diagnostics, and scan confidence.
Industry Intelligence
What a 30-Day Cloud Waste Turnaround Looks Like
Thirty days is enough time to find obvious waste, assign owners, and prove whether the cleanup habit will stick.
Founder Notes
Inside a $50k Cloud Leak
The leak was not one dramatic mistake. It was a pile of small resources that shallow scripts treated as harmless.
Founder Notes
Engineering Trust in Cloud Governance
Trust grows when engineering can show what changed, why it changed, and what evidence supports the decision.
Product Updates
Safer Cleanup Plans and Local API Review
This release moved cleanup planning closer to review: show the plan first, then decide what is safe to run.
Product Updates
v1.16.3: Policy, Monitor 2.0, and Smarter Scans
v1.16.3 tightened policy checks, monitoring, and scan flow so teams could review waste with fewer side conversations.
Product Guides
Your First Useful Cloud Scan in 15 Minutes
A useful first scan does not need a large rollout. It needs one account, read-only access, and a clear review target.
Product Updates
Azure and GCP Rightsizing Are Live
Rightsizing now covers Azure and Google Cloud, so oversized instances can be reviewed beside the rest of the waste backlog.
Product Updates
v3.1.0: Handoff Packages and Closure Tracking
v3.1.0 focuses on what happens after a finding is assigned: handoff, follow-up, closure, and reopening when ownership changes.
Founder Notes
Five Cloud Cost Leaks Monthly Reviews Miss
Monthly reviews miss waste when resources look ordinary in isolation but expensive in combination.
Industry Intelligence
CAST AI vs Cloud Waste Scanner
CAST AI and Cloud Waste Scanner solve different parts of the cost problem: automation inside Kubernetes versus local evidence across the estate.
Industry Intelligence
Cloud Custodian vs Cloud Waste Scanner
Cloud Custodian is strong when policy-as-code is already part of the operating model; CWS starts from evidence and triage.
Industry Intelligence
CloudHealth vs Cloud Waste Scanner
CloudHealth fits mature reporting programs; CWS is aimed at teams that need to inspect resources locally before they commit to action.
Industry Intelligence
CloudZero vs Cloud Waste Scanner
CloudZero explains spend through product and business context; CWS digs into the resources that might be cleaned up next.
Industry Intelligence
Harness FinOps vs Cloud Waste Scanner
Harness FinOps is built around platform workflows; CWS is built around local scans, resource evidence, and cleanup review.
Industry Intelligence
Kubecost vs Cloud Waste Scanner
Kubecost is the better starting point for Kubernetes allocation; CWS looks beyond container boundaries for unused cloud resources.
Industry Intelligence
ProsperOps vs Cloud Waste Scanner
ProsperOps works on commitment strategy; CWS looks for the resource hygiene problems that commitments do not fix.
Industry Intelligence
Spot.io vs Cloud Waste Scanner
Spot.io automates compute price decisions; CWS helps teams inspect waste before deciding what should change.
Industry Intelligence
Vantage vs Cloud Waste Scanner
Vantage gives teams spend visibility; CWS focuses on the local evidence needed to turn visibility into cleanup decisions.
Whitepapers
Appendix: Terms, Metrics, Templates, and Checklists
Use this appendix when the team needs shared terms, review templates, and metrics that survive the first rollout.
Whitepapers
Invisible Cloud Debt and Sovereign Governance
Cloud debt becomes invisible when finance sees the bill but engineering cannot tie it back to safe resource decisions.
Whitepapers
Change Review in Regulated Environments
In regulated environments, cleanup work only moves when evidence, approval, and rollback concerns are handled together.
Whitepapers
CI/CD and Runtime Guardrails for Cloud Governance
Cloud governance has to meet engineers where changes happen: code review, deployment, runtime checks, and incident follow-up.
Whitepapers
Playbooks for Finance, SaaS, and Platform Teams
Finance, SaaS, and platform teams all care about waste, but each group needs a different review rhythm.
Whitepapers
Rollout Roadmap, KPIs, and Executive Reporting
A rollout needs simple milestones and a few KPIs that leaders can read without joining every technical review.
Whitepapers
Security and Compliance Mapping for Local-First Governance
Security review gets easier when credential boundaries, export rules, and audit evidence are defined before rollout.
Whitepapers
Local-First vs SaaS: Procurement Selection Matrix
The right tool depends on what the buyer needs to control: credentials, workflow ownership, reporting depth, or automation.
Founder Notes
Why Cloud Waste Persists
Cloud waste persists because teams can see spend long before they know who can safely change it.
Founder Notes
Why Local-First Became the Trust Model
Local-first was a product decision about trust: cloud credentials should not move just to find obvious waste.
Founder Notes
Why One Scanner Needed Many Providers
Supporting many providers only matters if the findings still land in one reviewable backlog.
Founder Notes
Safe Automation Without Blind Deletion
Safe automation starts with saying no to blind deletion and yes to evidence, simulation, and review.
Founder Notes
Policies, Edge Cases, and Reporting
Policies are useful only when they survive the strange cases: shared resources, weak tags, exceptions, and partial ownership.
Founder Notes
The Operating Model Behind Durable Savings
Durable savings come from a boring rhythm: scan, review, assign, verify, and repeat.
Product Updates
v2.9.19: Kubernetes Scans Without a Cluster Agent
v2.9.19 added Kubernetes scanning without asking teams to install a cluster agent or hosted collector.
Founder Notes
Why Local-First Matters in FinOps
FinOps work starts with trust. This explains why Cloud Waste Scanner keeps credentials and scan output local by default.
Incident Series
March Rain and the Disappearing Coins
The second incident looked like a seasonal spike until the team found the same small leaks repeating every week.
Product Guides
Proxy Setup for Restricted Networks
Restricted networks do not have to block cloud cost review, but proxy setup needs to be explicit and testable.
Product Guides
From Notifications to Weekly Closures
Notifications are useful only when they lead to a decision, an owner, and a closed finding.
Product Updates
Rightsizing Without Breaking Workloads
Rightsizing is not just picking a smaller size. It is proving the workload can survive the change.
Product Guides
Turn Scan Results Into a Weekly Team Rhythm
A scan result becomes valuable when it turns into a weekly habit the team can repeat without chasing screenshots.
Whitepapers
Threat Model and Trust Boundary
This part defines what Cloud Waste Scanner touches, what stays local, and which assumptions matter for security review.
Whitepapers
Control Matrix and Operational Safeguards
Controls only help when operators can see how they map to credentials, exports, logs, and review steps.
Whitepapers
Verification Checklist and Incident Readiness
Use this checklist before rollout so verification and incident response are not invented during a bad week.
Whitepapers
Token Lifecycle and API Hardening
Tokens need a lifecycle: creation, storage, rotation, scope review, and removal when access is no longer needed.
Whitepapers
Transport Integrity and Operational Auditability
Transport and auditability matter most when scan evidence is exported, forwarded, or reviewed outside the operator machine.
Product Updates
v1.10: From Compute Cleanup to Storage Tiering
v1.10 expanded the cleanup conversation from compute to storage, where stale data often survives long after the workload ends.
Whitepapers
Engine Architecture and Component Boundaries
This part explains the main runtime boundaries: scanner core, provider adapters, desktop shell, local API, and reports.
Whitepapers
Findings Data Model and Policy Evaluation
A finding is useful only when it carries enough context for review: resource identity, evidence, confidence, and policy result.
Whitepapers
Performance, Reliability, and Rollout Patterns
Performance work is not only speed. It is making scans predictable enough for teams to trust the results.
Whitepapers
Quality Gates, Auditability, and Delivery Discipline
Quality gates protect the product from shipping findings that are fast, plausible, and wrong.
Whitepapers
Rust, Tauri, and the Platform Roadmap
Rust and Tauri were chosen for a desktop product that needs local control, predictable behavior, and a shared core.
Incident Series
The Christmas Gift in the Server Room
The fourth incident started with a holiday capacity request and ended with a review of what fear had overprovisioned.
Founder Notes
Why Fixed Idle Thresholds Miss Real Waste
A fixed idle threshold is easy to explain, but it misses the way real workloads pause, spike, and drift.
Product Updates
v1.0: What We Actually Shipped
The first release focused on a simple promise: scan major clouds locally and return findings people could review.
Product Updates
v1.10: 15 Providers Without 15 Tools
v1.10 expanded provider coverage, but the real goal was keeping the review workflow from splitting into fifteen tools.
Incident Series
The Night Cloud Prices Jumped
The price increase was real, but the margin problem came from resources the team could still clean up.
Article
Keeping the Product Easy to Start
The product should feel simple at the point where users are most cautious: download, install, and first run.
Guide
Pick the Right Package First
Pick the installer that matches the machine first, then verify it before you start connecting accounts.