Your issues drag on.
Sponsor them.
Post a bounty on a GitHub issue, credits are escrowed. A talent claims it, opens a PR, it merges: automatic payout. Zero contract, zero hiring, no invoice to validate.
Why.
Four reasons.
Bounties cover a category of work freelancing and hiring miss: tech debt, edge-case bugs, side-project features.
Speed.
An interested dev can claim in 5 minutes. No recruitment, no screening, no contract.
Variable cost.
You pay only when the PR merges. No pending invoice, no monthly commitment.
Proven quality.
Each talent shows their history of solved challenges, progression, badges. You know who you trust the issue to.
Zero HR.
No onboarding, no access to grant, no internal review. Code arrives via a standard GitHub PR.
Escrow.
Merge. Payout.
The mechanism is automatic end-to-end, via a GitHub webhook that detects the merge.
You post.
GitHub issue URL, context, required skills, reward. Credits are debited and escrowed immediately.
A talent claims.
A qualified talent claims it. They have 7 days to open a PR on your repo.
You merge.
You review the PR like any other contribution. Merge is your call.
Automatic payout.
The GitHub webhook detects the merge. Escrowed credits are converted into fragments for the talent, bounty is marked paid.
Bounty vs.
your other options.
– Search, screening, interview
– Contract, invoices, VAT
– Repo access onboarding
– You pay even if the work doesn't merge
– 3-6 month cycle
– Payroll taxes, fixed salary
– Permanent HR overhead
– Overkill for an isolated issue
+ Publish in 3 minutes
+ Payout on merge, guaranteed escrow
+ No repo access needed (standard PR)
+ Proven talent profile (public challenges)
Use cases.
These work categories are poorly served by freelancing and hiring.
The migrations, refactors, dependency upgrades that have been sitting for 6 months. Your devs have other things to do, but the work must be done.
ex: Rails 6 → 7 · Node 16 → 20 · Vue 2 → 3
The bug one customer in fifty hits. Reproducible but time-consuming to investigate. A specialist talent solves it in an evening.
ex: async race condition · memory leak · broken Safari render
Useful but non-priority features: CSV export, webhook integration, dark theme. Moderate value, fixed cost if internalized.
ex: SAML SSO · dark mode · embed widget · cursor pagination API
Common
questions.
What if nobody merges the PR? +
Escrowed credits are refunded to you on bounty expiration (30 days default, configurable). You only pay if the PR is merged by your team.
Is code quality guaranteed? +
Quality is validated by your review — you're free to reject the PR. The talent is incentivized to deliver clean work because their public profile records the acceptance rate.
Who owns the produced code? +
Your company. A bounty is a work-for-hire contract: the contribution is incorporated into your repo under your license, like any merged PR.
How do we identify the talent? +
Each talent has a public profile with their solved challenge history by domain, badges, streak, merged PRs. You choose who to trust the issue with.
How much does the service cost? +
No subscription, no fixed cost. Skilluv takes a 15% commission on the reward at merge — visible in the simulation before publication.
That issue.
Does it deserve a bounty?
3 minutes to publish. No fixed fee. You only pay on merge.