Top all-time · #5567
Nanit Engineering
Company blog · engineering.nanit.comprogrammingsystems
Nanit Engineering is the company blog at engineering.nanit.com, writing about programming and systems. Since 2016, 14 different Hacker News readers have linked it 27 times, most often “We saved $500k per year by rolling our own "S3"”. It is still writing: the last post was on 2026-01-22, and you can follow it by feed.
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
Linked for a post about cutting MongoDB costs by 90% by moving to Hetzner. The one comment does not judge the writing; it questions the trend of cost-saving stories on HN.
Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- We saved $500k per year by rolling our own "S3"4 people · 4 mentions · first linked 2025-10-21
- Six Years of Professional Clojure3 people · 3 mentions · first linked 2021-07-31
- Hand-Crafting Domain-Specific Compression with an LLM2 people · 2 mentions · first linked 2026-01-25
What Hacker News says?
"I cut my healthcare costs by 90% by canceling insurance and doctor visits." In all seriousness, this is a recurring pattern on HN and it sends the wrong message. It's almost as bad as vibecoding a paid service and losing private customer data. There was a thread here awhile ago, 'How We Saved $500,000 Per Year by Rolling Our Own “S3' [1]. Then they promptly got hacked. [2] [1] https://engineering.nanit.com/how-we-s…
Comment linking /how-we-saved-500-000-per-year-by-rolling-our-own-s3-6caec1ee1143
on “We cut our Mongo DB costs by 90% by moving to Hetzner”Submitted We saved $500k per year by rolling our own "S3" as a story · 328 points
HN discussionSubmitted Six Years of Professional Clojure as a story · 223 points
HN discussionSubmitted We Saved $500k per Year by Rolling Our Own S3 as a story · 15 points
HN discussionSubmitted Nanit’s AI Development Process as a story · 9 points
HN discussionSubmitted Using a serverless dead man's switch to monitor our monitoring as a story · 9 points
HN discussionSubmitted We saved $500k per year by rolling our own "S3" as a story · 8 points
HN discussionSubmitted How Your Recruitment Process Is Driving Candidates Away as a story · 8 points
HN discussionSubmitted Tips for Productive Testing as a story · 8 points
HN discussionSubmitted Kubernetes 1.2 Features as a story · 8 points
HN discussionSubmitted Six years of professional Clojure as a story · 7 points
HN discussionSubmitted Current state of EKS as a story · 7 points
HN discussionSubmitted Customizing Kubernetes DNS Using Consul as a story · 7 points
HN discussionSubmitted MLOps – Why You’d Want It in Your Company Today as a story · 6 points
HN discussionSubmitted An Index Gone Rogue as a story · 6 points
HN discussionSubmitted Good algorithms developer, bad algorithms developer as a story · 6 points
HN discussionSubmitted Why Should You Care About Elixir? as a story · 4 points
HN discussionSubmitted Mobile Multi-Platform to a Native Pod as a story · 4 points
HN discussionSubmitted Writing Elixir Plug library from the ground up as a story · 4 points
HN discussionSubmitted How We Monitor Our Kubernetes Cluster as a story · 4 points
HN discussionSubmitted Who watches the watchers?. Using a Dead Man Switch to monitor our monitoring as a story · 3 points
HN discussionSubmitted An Index Gone Rogue as a story · 3 points
HN discussionSubmitted 6 Years of Professional Clojure as a story · 3 points
HN discussionSubmitted Why Should You Care About Elixir? as a story · 2 points
HN discussionSubmitted Hand-Crafting Domain-Specific Compression with an LLM as a story · 1 points
HN discussionSubmitted Hand-Crafting Domain-Specific Compression with an LLM as a story · 1 points
HN discussionSubmitted TDD (Test) Your NGINX API Gateway as a story · 1 points
HN discussion