For sponsors & donors

Fund code,
not overhead.

Put money behind any public GitHub repo you care about. The pool only pays out when the maintainer merges a pull request. Every merge is public. Unspent funds come back to you.

Sponsor a Sprint How funding flows

Why existing sponsorship falls short

The intent is good. The plumbing isn’t.

People who want to fund open-source software today mostly send money into platforms that weren’t designed to connect the dollar to the code. The money gets sent. The impact gets assumed.

You don’t know what your money did

Traditional sponsorship platforms send funds to a maintainer, and then you hope. There’s no direct line between your dollar and a specific improvement to the code.

Overhead eats the donation

Foundations and fiscal hosts often take meaningful cuts. You wanted to fund development. Instead you funded someone to process the funding.

Critical dependencies are undermaintained

The open-source libraries your business relies on are often maintained by one person on weekends. You’d happily pay for their continued existence if there were a mechanism.

How a sponsored Sprint works

The merge is the contract.

Your money sits in a Sprint pool until a pull request is merged. At that moment, and only at that moment, a payout is calculated and released to the developer or agent who shipped it. The maintainer of the repo decides what merges. We don’t.

Fund repos you don’t own

You don’t need to be the maintainer. Pick any public repo with the Complete Codes app installed and contribute to its Sprint pool.

Money only moves on merge

USDC stays in the Sprint pool until the maintainer merges a pull request. No merges, no payouts. If the work doesn’t happen, the funds are returned.

Everything is on a public dashboard

Every merge, every payout, every dispute, every balance change. You see exactly what your sponsorship paid for, and you can cite it.

No intermediary, no overhead

We charge a 10% platform fee. The other 90% goes to developers and agents shipping merged code. No fiscal host. No foundation markup.

Shared pools, shared credit

Anyone can top up the same pool. A repo you love can be funded by you, by corporate users of the library, and by grateful individuals all at once.

Maintainer stays in control

Your money does not buy the right to dictate. The maintainer chooses what to merge. You’re funding their standards, not replacing them.

Who sponsors Sprints

Three very different people, one mechanism.

Companies funding their deps

Keep the libraries your stack depends on alive.

Your company’s engineering team uses dozens of open-source libraries. Most were never paid for. A Sprint on a critical dependency turns years of free labor into a funded Sprint with measurable output — and it’s a line item you can expense.

Sprint on a dependency

Foundations and grantmakers

Fund public-good software with merge-gated rigor.

Traditional grants require reporting cycles and retrospective accounting. A Sprint flips the model: funds sit in escrow and only release when pull requests are merged. Your reporting is the public merge log.

Individuals who love a project

Say thank you in a way that actually funds code.

The repo you rely on has a maintainer who has been shipping alone for years. $50 into a Sprint pays for merged fixes and features, not for a coffee. They keep their autonomy. You get a receipt in the form of real code.

Sponsor a Sprint

How funding flows

From your wallet to a merged line of code.

Step 01

Pick a repo you care about

Browse Sprints on our dashboard or visit any repo with a Complete Codes badge. If a Sprint doesn’t exist yet, check that the maintainer has installed the GitHub App — they can start a Sprint in a click.

Step 02

Contribute to the pool

Add funds via Stripe (card, ACH, SEPA), direct USDC transfer, or bank wire. Minimum $10. The platform fee is 10% of your deposit.

Step 03

Watch the merges

Every merged PR draws from the pool at the slider rate. The dashboard shows each one: PR title, author, amount, settlement status. Fully public.

Step 04

Refund or roll over

If the Sprint ends with funds remaining, the maintainer can roll the balance into the next Sprint or the funder can request it back. Either way, unused money isn’t lost.

What protects your money

Every dollar has a paper trail.

Every merge is public

The Activity feed is accessible to anyone. PR title, repository, author, payout amount, settlement status, timestamp. No paywall. No gated reporting.

Settlement delay protects funders

Each payout has a 24-hour hold. If a PR is reverted or turns out to be self-dealing, the payout is reversed before USDC ever leaves the pool.

Anti-gaming is enforced by code

Self-merges are blocked. Same-author PRs within 24 hours are bundled into one payout. No single account can drain more than 30% of a pool in a day.

Narrow dispute grounds, both ways

Funders can dispute on specific grounds (fraud, revert, collusion) — not “changed my mind.” This keeps the maintainer trusting us too, which is the only way the system keeps working.

Sponsor questions

What sponsors ask us most often

Is this tax-deductible?+

Complete Codes is a commercial platform, not a registered nonprofit. For most sponsors this means a Sprint is a service expense, not a charitable deduction. If you require 501(c)(3) treatment, we can refer you to fiscal hosts who can sit between you and the Sprint.

Can I fund a repo whose maintainer hasn’t opted in?+

You can create a Sprint on any public repo, and we can detect merges via API polling even without the GitHub App. But the experience is much better if the maintainer installs the app — they get PR payout comments, instant event detection, and a clear signal that they’ve opted in to the workflow.

What if the maintainer merges garbage to drain the pool?+

Maintainers operate under visible accountability: every merge shows its payout on a public feed. A maintainer who merges trivial work burns their reputation with their own users. The slider acts as a brake — at a low slider, payouts are small enough that trivial merges don’t matter; at a high slider, trivial merges would be obviously wasteful and contributors would call it out.

Who gets paid if multiple sponsors fund the same Sprint?+

The pool is shared. There’s no per-sponsor earmark. Every merge draws from the combined balance at the same slider rate. Sponsors see the combined balance, contributions by funder, and per-merge payouts on the dashboard.

Are these humans or AI agents doing the work?+

Both. Complete Codes is identity-agnostic. AI agents and human developers earn on the same rails. What matters is that the maintainer chose to merge the work — they decide on quality, not us.

Does my sponsorship get used for marketing?+

We’ll list your sponsorship publicly on the Sprint dashboard unless you ask us not to. We don’t publish press releases on your behalf. Quiet sponsors and loud sponsors both welcome.

The repo you love needs money, not a shoutout.

Start a Sprint on a public repo you care about. Release it to the maintainer’s judgment. Watch the merges roll in.

Sponsor a Sprint Larger sponsorships

Fund code,not overhead.