Solo-built a bug bounty tracker in 5 weeks — launching Tuesday on Vercel Day. What would you add?
Hey PH 👋
I'm a 19-year-old bug bounty hunter from India. Over the last 5 weeks I built BountyDesk solo — an open-source tracker + Markdown report builder for hunters who are tired of juggling spreadsheets, Notion, and 5 platform dashboards.
It launches here on Tuesday June 16 as part of Vercel Day.
Stack: Next.js 16 + Supabase (Postgres + RLS) + Paddle (Merchant of Record) + PostHog. Source: github.com/kushagra1607/bountydesk (AGPL-3.0).
Three honest questions before launch:
1. If you bug-hunt — what's your current workflow? Spreadsheets, Notion, custom DB, or nothing?
2. The Markdown report builder uses templates that triagers accept (summary → repro → impact → PoC → fix). What sections do YOUR best-accepted reports always include?
3. For PH veterans — what's one thing you wish you'd done differently before your first launch?
Live demo at bountydesk.vercel.app (free tier, no card). Brutal feedback welcome — I'd rather hear it now than at 1am PT Tuesday morning.
Thanks for any thoughts 🙏
— Kushagra
Replies
Building and open-sourcing something in 5 weeks at 19 is impressive 👏
I’m not a bug bounty hunter myself, but the reporting workflow definitely sounds like a pain point worth solving.
I’m fairly new to the Product Hunt community and preparing to launch a productivity tool soon, so I’m learning a lot from builders sharing their journey like this.
Good luck with the launch on Vercel Day! Feel free to follow me—I’d love to stay connected and support fellow makers. 🚀