Microcredit is lending very small amounts, usually short term and usually without collateral, to people that ordinary banks will not serve. CGAP, the World Bank-hosted research group on financial inclusion, describes it as "small amounts of short-term capital" for poor households and tiny businesses. In 2018, the last year with a global count, microfinance institutions lent to 139.9 million borrowers and held about $124.1 billion in loans (Convergences, Microfinance Barometer 2019).

The idea matters to software for a simple reason. Most open-source maintainers face the same problem as a small trader with no collateral: real, useful work, and no lender, investor or employer who will fund it in the small amounts it needs. This guide explains how microcredit works, what the research says about it, and how the same pattern of small, trust-based money now reaches developers. It is part of our series on social business.

What is microcredit?

A microcredit is a loan small enough that a normal bank would lose money processing it. The size depends on where you are.

  • In the EU, the EaSI programme that ran from 2014 to 2020 defined a microcredit as "a loan of up to EUR 25 000" (Regulation (EU) No 1296/2013, Art. 2). The European Investment Fund's current microfinance guarantee covers loans of up to €50,000 per borrower (EIF term sheet, May 2026).
  • In the US, the Small Business Administration's microloan programme lends up to $50,000, and the average microloan is about $13,000. The money goes through nonprofit, community-based intermediary lenders, with terms of up to seven years (SBA).

The modern model was pioneered in Bangladesh in the 1970s by the economist Muhammad Yunus and what became Grameen Bank. Since then it has been copied, adapted and argued over by thousands of lenders on every continent, and that wider story is what this guide is about.

How does microcredit work?

Microlenders replace collateral with other ways of building trust. The main ones are:

  1. Small first loans. A borrower starts with a small amount and qualifies for more after repaying it.
  2. Frequent, small repayments. Weekly or monthly instalments keep each payment manageable and show the lender early if something is wrong.
  3. Group lending. Many lenders ask borrowers to form groups. In the classic version, members choose each other and all of them are liable for each other's loans, so the group screens and supports its own members (Ghatak and Guinnane, Journal of Development Economics, 1999).
  4. Crowdfunded capital. Platforms such as Kiva let anyone lend from $25, with no interest paid back to the lender. Kiva U.S. still offers 0% loans of $1,000 to $15,000 to American small businesses, with no fees and no collateral (Kiva).

Notice what these share. None of them asks "what do you own?" They ask "what have you done so far, and who will vouch for you?" That question is the bridge to open source.

Does microcredit work?

It helps, but less than its early promoters claimed. In 2015 Abhijit Banerjee, Dean Karlan and Jonathan Zinman summed up six randomised trials of microcredit in six countries. They found "a consistent pattern of modestly positive, but not transformative, effects" (American Economic Journal: Applied Economics). Credit tended to help most where borrowers already ran a business.

That result is a useful warning for anyone designing funding for developers. Small money works best when it supports work that is already happening. It rarely creates the work from nothing.

Microcredit, micropayments, microgrants and API credits

The word "micro" gets attached to several different things, and search results mix them up.

Term What it is Paid back?
Microcredit or microloan A small loan, often without collateral Yes, usually with interest
Microgrant A small grant for a defined piece of work No
Micropayment A very small payment for a single use, like one page or one API call It is the payment
Micro-credential A short certificate of a skill Not money at all
API credits Prepaid balance at a paid API Spent, not repaid

Developers mostly meet the last three. If you are juggling prepaid credit at several AI and data APIs, mr-usage, a free and open-source desktop app by Mr Pirate, shows what is left at 44 of them in one window. TigerOCR, Mr Pirate's PDF-to-Markdown service, is an example of micropayments done honestly: you add credit from $5, each job costs a few cents per page of GPU time, and failed jobs are refunded. Neither is microcredit, but both come from the same instinct to keep amounts small and visible.

Why open source has a microfinance problem

Open-source software is worth far more than anyone pays for it. A Harvard Business School working paper estimated that firms would spend 3.5 times more on software if open source did not exist (HBS, 2024). Little of that reaches the people who maintain it. In Tidelift's 2024 survey of 437 maintainers, 60% described themselves as "unpaid hobbyists" (Tidelift 2024 Maintainer Impact Report).

The gap looks a lot like the one microcredit was invented to close. A maintainer has proven work, often a public history of commits and users, but nothing a bank or investor will accept. The amounts needed are small: a laptop, a test device, a month to fix security bugs. And the people best placed to judge the work are its users, just as a village group knows which of its members will repay.

Our guide to how open source projects are funded covers the big money: company staff time, foundations and business models. The rest of this article covers the small, trust-based money, the part that works most like microfinance.

Five ways small, trust-based money reaches developers

1. Sponsorship: small, regular amounts from users

Sponsorship is the closest thing open source has to small, frequent repayments, except that nobody owes anything. Users pay a small amount each month because the tool keeps working for them.

  • GitHub Sponsors charges no fee on sponsorships from personal accounts, and up to 6% on sponsorships from organisations. A maintainer can publish up to 10 monthly and 10 one-time tiers.
  • Open Collective adds a fiscal host, an organisation that lends a project its legal status and holds its money, and shows every donation and expense in public. Open Source Collective, the host most software projects use, charges 10% of funds raised (Open Source Collective).
  • Ko-fi takes 0% of one-time tips on its free plan, though the payment processor still charges its own fee.

Setting one up takes minutes. A FUNDING.yml file in your repository's .github folder adds a Sponsor button that can point to GitHub Sponsors, Open Collective, Ko-fi, thanks.dev and up to four custom links (GitHub Docs). Mr Pirate's own support page is built the same way.

2. Microgrants: small grants for defined work

Microgrants fund a specific piece of work, such as a feature, an audit or a port, without asking for equity or repayment. Like a first microloan, a small grant is a way to prove the work before larger money follows.

  • NLnet and NGI Zero (EU). The Dutch foundation NLnet handed out EU Horizon Europe money through the NGI Zero Commons Fund in grants of €5,000 to €50,000. That fund's 13th and final call closed on 1 June 2026, and NLnet now runs new calls under the EU's Open Internet Stack programmes (NLnet, NLnet news).
  • FLOSS/fund. Run by the Indian brokerage Zerodha, it gives $1 million a year in grants of $10,000 to $100,000 per project. Projects apply by publishing a funding.json file (FLOSS/fund).
  • Sovereign Tech Agency (Germany). Funded by the German government, it pays for maintenance and security work on open digital infrastructure. Five years in, it reports "over €60 million" across "more than 110 investments" (Sovereign Tech Agency, October 2026). Its grants are larger than micro, but the logic is the same: fund proven, under-served work.

3. Bounties: small payments for one fix

A bounty pays whoever fixes a specific issue. On Algora, a maintainer comments /bounty $100 on a GitHub issue, the contributor references it in their pull request, and the maintainer pays through Stripe. Algora's pricing page shows a 9% service fee (Algora pricing).

Bounties carry a trust risk that microlenders know well: the intermediary can fail. Bountysource stopped paying out in 2023, and the video app NewPipe says it lost about €6,400 of bounties it had been awarded (NewPipe). If you use a bounty platform, withdraw your balance often.

4. Dependency funding: paying the whole chain

Microfinance spread risk across a group. Dependency funding spreads money across a supply chain. thanks.dev scans a company's repositories, maps their dependencies up to three levels deep, and splits a donation across them, so small libraries deep in the tree get paid too.

5. Real microloans for small software businesses

Some developers need an actual loan: to buy hardware for an embedded project, cover a few months while a paid product launches, or pay for a certification. Microloans are built for that. In the US, Kiva U.S. and SBA microlenders lend to sole traders and small firms. In the EU, microfinance banks backed by the European Investment Fund lend to micro-enterprises and the self-employed. A small software business that sells something, such as a paid plugin or a support plan, can qualify like any other small business.

The safest use is the one the research supports: borrow to grow something that already earns, not to start from zero.

How Mr Pirate's tools fit in

BuildForPeople lists open-source and low-profit software, and Mr Pirate's own tools show several of these models side by side.

  • mr-usage and LLM Dogfight are free and open source, MIT licensed. Both are free to use, so the only money behind them is whatever users choose to give through the support page.
  • OpenCarMind is an open-source, MIT-licensed OBD2 logger that runs its AI model on an ESP32. Hardware projects like it are where a small loan or grant for test boards and cars makes the most difference.
  • TigerOCR is a hosted service paid in small, prepaid amounts, so each user pays only for the GPU time their own jobs use.
  • GlassVGL and LightEDA sell paid packs next to free parts. The sales pay for the free versions, the open-core pattern described in our funding guide.

Read Mr Pirate's tools for what each one does, or see the support page if one of them saved you time.

A checklist if you maintain an open-source project

  1. Add a FUNDING.yml file so GitHub shows a Sponsor button.
  2. Publish a funding.json file if you want to apply to FLOSS/fund.
  3. Write down two or three pieces of work a €5,000 to €50,000 grant could pay for, with a timeline. Grant programmes ask for exactly that.
  4. Keep your public history clean: releases, a changelog and answered issues. It is your credit history.
  5. If you sell anything, keep the books separate. That is what a microlender will ask to see.
  6. List your project on BuildForPeople so users who care about how software is paid for can find it.

Frequently asked questions

What is the difference between microcredit and microfinance?

Microcredit is lending. Microfinance is the wider set of services for people banks do not serve, including savings, insurance and money transfers as well as loans.

Who started microcredit?

Small, informal loans are centuries old. The modern model of lending to poor borrowers without collateral, at scale, was pioneered in Bangladesh in the 1970s by Muhammad Yunus and Grameen Bank. Many other lenders, Kiva among them, have since built their own versions.

Can open-source developers get microloans?

Yes, if they run a business. Microlenders lend to sole traders and small firms, and a developer who sells software or services counts. For unpaid open-source work, sponsorship and microgrants fit better because nothing has to be repaid.

Is GitHub Sponsors free to use?

For sponsorships from personal accounts, GitHub charges no fee. Sponsorships from organisations carry a fee of up to 6%.

Does microcredit reduce poverty?

The best evidence, six randomised trials summarised in 2015, found modest gains rather than a transformation. It helps most where borrowers already run a business.

Sources