Right after Launch Week 1, we wanted to keep the momentum going. We had just hit #1 on GitHub Trending, #1 on Product Hunt, and the community was buzzing. So we thought: why not channel all of that energy into something that actually makes InsForge better?
That is how the PR Hackathon was born.
The Plan
The idea was simple. We created 30 GitHub issues across different difficulty levels, from good first issues worth 1 point to high-impact SDK and infrastructure work worth 5 points. The hackathon would run for 10 days, from March 13 to March 22. Top contributors would win cash prizes, and everyone who participated would get 3 months of InsForge free.
We spent time carefully writing up each issue, making sure they were well-scoped and had clear acceptance criteria. We wanted people to be able to pick something up and start working on it right away.
We thought 30 issues would be enough for 10 days. We were very wrong.
Day One
All 30 issues were claimed within the first day.
We did not expect that at all. We woke up to a flood of notifications. People were jumping into the Discord, claiming issues, asking questions, and submitting PRs before we even had our morning coffee.
It was exciting, but also honestly overwhelming. We suddenly had dozens of PRs to review, and we wanted to be thoughtful and respectful with every single one. These people took time out of their day to contribute to our project, and we owed them real, sincere feedback.
Keeping Up
The review process was the hardest part. We tried to review every PR with care, leaving meaningful comments, suggesting improvements, and making sure nothing broke existing functionality. But the volume was relentless.
We had to quickly come up with more issues. We stayed up late writing new ones, trying to keep ahead of the demand. It felt like we were restocking shelves while people were grabbing things off of them.
But then something really cool started happening.
The Community Took Over
Contributors did not just work on the issues we created. They started proposing their own.
People were digging into InsForge, finding real bugs, and sending them our way. Security issues, rate limiting problems, mock data leaking to production. Real stuff.
And they did not just report them. They fixed them.
That was the moment it stopped feeling like an event we were running and started feeling like a community that was building with us. These were not people chasing prize money. They genuinely cared about making the platform better.
What It Built
To give you a sense of the caliber of work that came out of this, here are a few examples.
Abh1shxkk (Abhishek Chauhan) built bring-your-own-key support for OpenRouter (#928). That means users can now plug in their own OpenRouter API key, and the system handles credential precedence, encrypted storage, and billing logic automatically. That is not a small feature. That is production infrastructure.
benzaid32 (Ben Zaid) turned our edge functions page from a read-only view into a full management interface (#948). Inline code editing, file upload with validation, download and export, delete with confirmation. The kind of dashboard polish that makes developers actually want to use the tool.
Davidson3556 (Awokoya Olawale Davidson) added custom domain support for deployments (#914). Add your own domain, get DNS configuration hints, verify it, see status badges. Full end-to-end, from backend API routes to the frontend UI.
And beyond features, we saw a massive wave of integration testing across our SDKs. Contributors wrote tests that caught edge cases we had missed, covering the Python, JavaScript, and Go SDKs with real test coverage that makes us confident things actually work.
These are just a few highlights. The hackathon also produced bug fixes, documentation updates, new integrations, and dashboard UX improvements. The kind of broad, unglamorous work that makes a product actually solid.
Our leaderboard tells part of the story.
Contributors like davidson3556, junaiddshaukat, benzaid32, prakharsingh-74, and powxenv went above and beyond, each racking up double-digit point totals. But even the contributors with a single merged PR made InsForge more robust.
The platform is genuinely better because of this hackathon. Not in a marketing way. In a real, tangible, the-product-is-more-reliable way.
What Made Us Happy
The thing that made us happiest was not the number of PRs or the issues closed. It was that people stayed.
After the hackathon ended, many of these contributors stuck around in the Discord. They kept opening issues, kept submitting PRs, kept helping other people get started. They became part of the InsForge community.
That is worth more than any metric.
What We Learned
If we are being honest, we were not fully prepared for the response. We underestimated how quickly issues would get claimed, and we underestimated how much review bandwidth we would need. There were moments where we felt like we were drowning in PRs.
But we also learned that if you build something people care about, and you give them a way to contribute, they will show up harder than you ever expected. And if you treat their contributions with respect, they will stick around.
Thank You
To everyone who participated in the PR Hackathon: thank you. Sincerely. You made InsForge better, and you reminded us why we are building this in the first place.
If you missed this one, do not worry. This will not be our last community event. Join our Discord to hear about the next one.
See you in the next hackathon.