HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
WozzHQ
wozz
Shell2025–2026
WozzHQ / wozz

wozz

Kubernetes cost optimization - catch expensive resource changes before they merge

3Distinct people
11Mentions
0Explicit recommenders
164GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Kubernetes cost optimization - catch expensive resource changes before they merge

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:57:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week11 dated mentions

Observed mentions: 2025-11-12 18:20:32 UTC to 2026-01-08 15:56:56 UTC. Weeks start Monday, UTC.

01232025-11-10 00:00:00 UTC to 2025-11-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 102025-11-17 00:00:00 UTC to 2025-11-24 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-11-24 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-12-01 00:00:00 UTC to 2025-12-08 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-12-08 00:00:00 UTC to 2025-12-15 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsDec 82025-12-15 00:00:00 UTC to 2025-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-22 00:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 00:00:00 UTC to 2026-01-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-05 00:00:00 UTC to 2026-01-12 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 5

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 102025-11-10 00:00:00 UTC2025-11-17 00:00:00 UTC101
Nov 172025-11-17 00:00:00 UTC2025-11-24 00:00:00 UTC211
Nov 242025-11-24 00:00:00 UTC2025-12-01 00:00:00 UTC211
Dec 12025-12-01 00:00:00 UTC2025-12-08 00:00:00 UTC211
Dec 82025-12-08 00:00:00 UTC2025-12-15 00:00:00 UTC312
Dec 152025-12-15 00:00:00 UTC2025-12-22 00:00:00 UTC000
Dec 222025-12-22 00:00:00 UTC2025-12-29 00:00:00 UTC000
Dec 292025-12-29 00:00:00 UTC2026-01-05 00:00:00 UTC000
Jan 52026-01-05 00:00:00 UTC2026-01-12 00:00:00 UTC110

What Hacker News says

2 sources
Hi HN, I'm the creator of Wozz. I've been doing K8s consulting for Series B startups and kept seeing the same pattern: massive over-provisioning (like 8GB RAM limits on apps using 500MB), but no easy way to audit it without installing agents like Kubecost or CAST AI. The problem: Security teams block agent installs for 3-6 months. The waste just sits there burning money. So I built this. It's a bash script that runs locally using your existing kubectl context. It: - Compares resource requests vs actual usage (kubectl top) - Finds orphaned load balancers, unused storage, missing requests - Anonymizes pod names locally (SHA256 hashes) before exporting - Generates a report you can share It's ~300 lines of bash + Python, MIT licensed. You can audit the code before running. Try it: ```bash curl -sL https://raw.githubusercontent.com/WozzHQ/wozz
Read the rest
/main/scripts/w... | bash ``` Or clone first if you don't trust curl | bash: ```bash git clone https://github.com/WozzHQ/wozz.git cd wozz bash scripts/wozz-audit.sh ``` Most common finding: "AI-generated YAML" with overly generous limits. ChatGPT/Copilot tends to suggest 8GB when 1GB would work. I'm doing free analysis for the first 50 clusters (email output to audit@wozz.io). Would love feedback on: 1. Is the anonymization approach sufficient for your security team? 2. What other cost patterns should I detect? 3. Would a GitHub Action version be useful? Code: https://github.com/WozzHQ/wozz Website: https://wozz.io Happy to answer questions!
In Show HN: Wozz – Find Kubernetes waste without installing agents Bash script MIT

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.