Hi Hacker News,
Hiring the wrong developer can cost a company around 30% of that hire’s annual salary.
With IssuePay, companies can spend just a few less bucks on real open-source issues from their own repositories and get their work done.
Contributors get paid while proving their skills, and companies get a signal for who delivers high-quality work.
Most companies already run informal bounty systems, across Discord, forums, GitHub issues, etc. It works, but it’s fragmented and hard to scale.
So what we try to do is centralize that ecosystem, your bounties reach a much wider audience. Developers who don’t know your project yet, but contribute to similar ones, can discover your tasks alongside ones they already care about. That exposure brings in new contributors who might never have found you otherwise.
And here’s the next step, once a contributor has successfully completed tasks, we can match them to open roles at your company. With git history, contributions, and performance already visible, a small open-source contribution can turn into a full hiring, streamlining the process from task to job offer.
In short, IssuePay helps you amplify your existing workflow while creating a more reliable way to find and hire talent.
Hi Josh, sorry for the delay in responding and thanks for your comment. I realize the phrase "Limited visibility to hiring companies" might not have been the best way to put it. What I meant is that within the application’s Job Offers section, users with a premium plan will appear higher and more prominently in search results. It’s about priority placement in those job listings, not about your OSS contributions or your name being hidden.
Thank you! If you have any more suggestions, please don’t hesitate to share them.
Hi Komo,
You're correct that no tech companies are listed yet, so that claim has been removed for now. The footer links (including Terms of Service and Privacy Policy) are being finalized and will be working shortly.
As for the 50% fee, we understand that a 50% fee feels high, we're currently reevaluating our pricing to ensure it's fair and truly benefits our users.
Hi ezekg,
When we say “taxes,” we actually mean the platform’s cut or fee, not any government tax. We get that it sounds confusing and we’ll fix that wording, thanks.
The idea behind the platform is to help folks who might not code themselves, like companies or users, pay developers to improve the projects they care about. So if you use or rely on a project, you can create sponsor issues, and the devs get paid for their work.
It also gives companies a chance to see top talent in action by watching contributors work on real open-source projects before hiring them.
Sure, it doesn’t magically fix the whole “maintainers getting paid” problem, but it’s a way to get stuff done and reward contributors.
With IssuePay, companies can spend just a few less bucks on real open-source issues from their own repositories and get their work done. Contributors get paid while proving their skills, and companies get a signal for who delivers high-quality work.
Most companies already run informal bounty systems, across Discord, forums, GitHub issues, etc. It works, but it’s fragmented and hard to scale.
So what we try to do is centralize that ecosystem, your bounties reach a much wider audience. Developers who don’t know your project yet, but contribute to similar ones, can discover your tasks alongside ones they already care about. That exposure brings in new contributors who might never have found you otherwise.
And here’s the next step, once a contributor has successfully completed tasks, we can match them to open roles at your company. With git history, contributions, and performance already visible, a small open-source contribution can turn into a full hiring, streamlining the process from task to job offer.
In short, IssuePay helps you amplify your existing workflow while creating a more reliable way to find and hire talent.