Show HN: Burn, K8s cost CLI that pulls actual spot prices per instance type
Burn is a cost analysis tool for Kubernetes clusters that helps users identify and reduce unnecessary expenses. It requires no complex setup and provides real-time pricing information for various cloud services. The tool also offers AI-powered recommendations and integrates with Slack for easy access to cost reports.
- ▪Burn provides full cost coverage for compute, storage, load balancers, and GPU costs with real-time cloud pricing.
- ▪The tool works with major cloud providers including AWS EKS, Azure AKS, and GCP GKE, as well as on-premise clusters.
- ▪Users can ask questions in plain English and receive kubectl commands for cost analysis.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/tanrikuluozlem/burn |
| Publication time | Tue, 26 May 2026 06:15:07 +0000 |
| Retrieval time | 2026-05-26T06:37:45.433Z |
| Last seen | 2026-05-26T06:37:45.433Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | tixZOdXCCaRh |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
burn Your Kubernetes cluster is burning money. Find out where. No agent to deploy. No dashboard to maintain. No YAML to configure. Just install and run. Why burn Zero setup — brew install, run one command, get answers. No cluster agent, no persistent storage, no config files. Full cost coverage — Compute, storage, load balancers, and GPU costs with real-time cloud pricing. AI-powered — Ask questions in plain English, get kubectl commands you can copy-paste. Slack-native — /burn for instant cost reports. /burn ask "..." for AI analysis. Cloud + on-prem — Works with AWS EKS, Azure AKS, GCP GKE, and on-premise clusters. Spot readiness — Identifies which workloads can safely move to spot instances with real-time discount and interruption rate.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.