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, 6:34:31 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

1 sources
wozzio·Jan 8, 2026Submission

Show HN: Wozz – open-source Kubernetes cost linter and cluster auditor

URL: https://github.com/WozzHQ/wozz Hi HN, I built Wozz, an open-source CLI and GitHub Action to catch expensive Kubernetes configs before they merge. The Motivation I noticed that most cloud cost tools (like Kubecost) only show you the bill 30 days later. By then, the over-provisioned sidecar or massive Java heap is already in production. I wanted something that acts like a unit test for resource requests blocking fat finger mistakes in the PR rather than waiting for the bill. How it works Wozz runs in two modes: In CI/CD (The Linter): It parses the git diff of your manifests (deployment.yaml, etc.), calculates the cost delta (requests × replicas), and posts a comment if the change exceeds a threshold (e.g., +$50/mo). It also checks HorizontalPodAutoscaler limits to flag worst-case scaling risks. Locally (The Auditor): It scans your curr
Read the rest
ent kubecontext to compare reserved requests vs. actual live usage (kubectl top). This helps find the "Sleep Insurance" gap—where devs request 4GB RAM just to be safe, but the app only uses 200MB. Implementation Details Stack: TypeScript/Node.js. Math: Instead of querying AWS Cost APIs (which requires sensitive creds and is slow), it uses a configurable Blended Rate (e.g., $0.04/GB/hr) to estimate costs deterministically. Privacy: It runs 100% locally or in your runner. No manifests or secrets are sent to any external server. Repo https://github.com/WozzHQ/wozz Feedback I’m currently using a static Blended Rate for the cost math to keep the tool fast and stateless. I’m curious if this approximation is accurate enough for your team's guardrails, or if you strictly require real-time Spot Instance pricing to trust a tool like this?
2 points · Open discussion

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.