This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
kavach-engine
Zero double-sells. The Go engine for flash-sale inventory.
An open-source Go inventory-reservation engine for ANY flash sale: e-commerce drops, tickets, hotels, events. Millions of requests, zero double-sells, no crashes, no hangs. - l72683876-beep/kavach-...
I built Kavach after watching too many flash sales go sideways: two people getting the same ticket, seat maps drifting out of sync, and servers freezing the moment a drop opens. Kavach is the open-source Go engine I wrote to fix that. It guards inventory at the request level: atomic reservations, TTL-backed holds, waitlists, and replay-safe idempotency, so the seat a buyer sees is the seat they get.
Numbers from our benchmark runs: 473,000+ requests at a peak of ~4,000 req/s with zero oversells and zero errors, on a single node.
There's a live demo linked on this page: a 3D seat map for a fake event (Aurora Nights) running the engine for real. Grab a seat, refresh fast, try to oversell it. Good luck.
Feedback that would help most: where you'd trust it and where you wouldn't, what your stack needs from it (API shape, integrations), and what's missing before you'd drop it into production. Cluster mode is next on the roadmap. Thanks for taking a look!
About kavach-engine on Product Hunt
“Zero double-sells. The Go engine for flash-sale inventory.”
kavach-engine was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #349 on the daily leaderboard. An open-source Go inventory-reservation engine for ANY flash sale: e-commerce drops, tickets, hotels, events. Millions of requests, zero double-sells, no crashes, no hangs. - l72683876-beep/kavach-...
On the analytics side, kavach-engine competes within Open Source, Developer Tools, GitHub and E-Commerce — topics that collectively have 675.9k followers on Product Hunt. The dashboard above tracks how kavach-engine performed against the three products that launched closest to it on the same day.
Who hunted kavach-engine?
kavach-engine was hunted by Nayak. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of kavach-engine including community comment highlights and product details, visit the product overview.
Hey PH! I'm Lucky, the maker of Kavach.
I built Kavach after watching too many flash sales go sideways: two people getting the same ticket, seat maps drifting out of sync, and servers freezing the moment a drop opens. Kavach is the open-source Go engine I wrote to fix that. It guards inventory at the request level: atomic reservations, TTL-backed holds, waitlists, and replay-safe idempotency, so the seat a buyer sees is the seat they get.
Numbers from our benchmark runs: 473,000+ requests at a peak of ~4,000 req/s with zero oversells and zero errors, on a single node.
There's a live demo linked on this page: a 3D seat map for a fake event (Aurora Nights) running the engine for real. Grab a seat, refresh fast, try to oversell it. Good luck.
Feedback that would help most: where you'd trust it and where you wouldn't, what your stack needs from it (API shape, integrations), and what's missing before you'd drop it into production. Cluster mode is next on the roadmap. Thanks for taking a look!