HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nayafia
lemonade-stand
Learning & Reference2016–2022
nayafia / lemonade-stand

lemonade-stand

A handy guide to financial support for open source

18Distinct people
24Mentions
1Explicit recommenders
7.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A handy guide to financial support for open source

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I cannot agree more. Funding must play a part in the sustainability of open source. I recommend the Lemonade Stand document by Nadia Eghbal…

cavneb used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year24 dated mentions

Observed mentions: 2016-06-16 15:59:22 UTC to 2022-08-29 09:12:55 UTC.

02462016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 3 submissions, 4 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC422
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC734
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC413
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC211

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
A handy guide to financial support for open source. "I do open source work, how do I find funding?" This document aims to provide an exhaustive list of all the ways that people get paid for open source work. Hopefully, projects and contributors will find this helpful in figuring out the best options for them. The list below is roughly ordered from small to large. Each funding category links to several real examples (using topical articles or pages wherever possible instead of just a project's homepage.) The categories are not mutually exclusive. For example, a project might have a foundation but also use crowdfunding to raise money. Someone else might do consulting and also have a donation button. Etc. Table of Contents Donation button Bounties Sponsorware Crowdfunding (one-time) Crowdfunding (recurring) Books and merchandise Advertising & sponsorships Get hired by a company to work on project Start a project while currently employed Grants Consulting Paid support SaaS Copyleft + paid license Open core Foundations & consortiums Venture capital Restricted license APPENDIX: Contributing to this guide // License & attribution TRANSLATIONS: Traditional Chinese(繁體中文) // Simplified Chinese(簡體中文) // Italian(italiano) // Japanese(日本語) // Russian(русский) // Bulgarian(български) *"personal effort" notes when a funding effort was led by an individual, not a project Donation button Stick a donation button on your site. Stripe and PayPal are examples of services you can use to accept donations. Pros Few strings attached Little work involved: "set it and forget it" Cons Usually not much money unless you have dedicated fundraising efforts Need an entity to accept donations, which may take a fee for doing so. Examples are Stripe and PayPal. To make donations tax-free for the person/organization who is donating, may need a legally charitable entity (in the United States, a 501(c)(3) nonprofit entity) to accept donations. Software Freedom Conservancy and NumFOCUS are examples. Harder for individuals or international donations to manage Sometimes not clear who “deserves” money in a project or how it gets distributed. An entity like OpenCollective may help with this. Case Studies ChatSecure Git Transmission Twisted Bounties Sometimes, projects or companies post bounties for open source work (ex. "fix this bug and collect $100"). There are several websites, listed below, that help facilitate the posting and collection of bounties. Pros Open to community participation Money is tied to doing specific work (more like paying for service than donations) Especially popular for security work Cons Can create perverse incentives in a project (low quality PRs, distracting priorities) Conflicts can arise over whether work fulfills a bounty Usually not much money per bounty (~<$500) Doesn’t provide recurring revenue Case Studies Gitcoin GitHub Bug Bounty Program Google Patch Rewards Inkscape's "funded development" system Internet Bug Bounty IssueHunt Sponsorware If you'd like to open source a project but want to ensure that others will invest in its long-term maintenance, you could tell your community that you'll open source the project once you've hit a certain amount of sponsorship. (Writer Tim Carmody refers to this as "unlocking the commons.") This is similar to Crowdfunding (one-time) described below, except that instead of funding the work in advance, you build the software from the get-go, then choose whether or not to open source it depending on whether you hit your goal. Pros Can be a recurring source of revenue after initial development, depending on how you set up the conditions of releasing the project It can be a useful signal as to whether people value the package Gives people immediate value – people can sponsor you and get access to the package right away Doesn’t restrict future potential growth of the project and upholds the spirit of open source Cons Doesn't work for projects that are already released Likely only works for eye-catching projects where a demo or proof-of-concept is very exciting Case Studies Caleb Porzio's sushi package Crowdfunding (one-time) If you have a specific idea you'd like to implement (rather than ongoing project work), a one-time crowdfunding campaign can help raise the funds you need. Both individuals and companies might be willing to donate to your campaign. Pros Few strings attached Can be easier for an individual to legally manage via, e.g. Kickstarter Cons Lots of work involved to market campaign Usually has to be tied to concrete outcome, perks Usually not that much money (~$50K for one time) Companies are not always comfortable donating to campaigns Case Studies Andrew Godwin + Django (personal effort) Dave Gandy + Font Awesome GDAL Coordinate System Barn Raising Monero Community Crowdfunding System (CCS) RESTful WP-CLI Crowdfunding (recurring) If you'd like to fund ongoing project work, you can set up a recurring crowdfunding campaign, with a monthly or annual financial commitment that renews indefinitely (or until the donor cancels). Those who use your project regularly (including both individuals and companies) might be willing to fund your work. Pros Few strings attached Can be easier for an individual to legally manage via, e.g. Patreon, Liberapay, OpenCollective Cons Harder to get commitments to recurring donations (often requires preexisting brand/reputation) Harder to explain concrete outcomes, perks that come with recurring donations Usually not that much money (~$1-4K monthly) Companies are not always comfortable donating to campaigns Case Studies Babel Caleb Porzio + Laravel Livewire and more Clojurists Together Eran Hammer + hapi Patreon ESLint Evan You + Vue.js Patreon GnuPG Ruby Together Tom Christie + Django REST framework (personal effort) webpack Books and merchandise If you are an expert in a domain that other people might find useful to learn about, you could write and sell a book or series of books. You can find a
Read the full README on GitHub

What Hacker News says

24 sources
Nice list! See also: https://github.com/nayafia/lemonade-stand What I find missing in most discussions around this topic is something in between donations and purchases: Very few projects [1] offer "goodwill licenses" to buy, which allows companies to support the product using their "usual means" (without getting any actual benefit from it, so in some ways it is a donation): In most places I know, arguing up the chain why the guy from the IT department wants to DONATE money is near to impossible, whereas simply purchasing 100 or 500 or more "licenses" of something deployed on all machines does not raise any eyebrows. [1] Is there a list of such projects somewhere? How well does it work? I came across such projects but I don't remember specific examples.
In Monetizing Your Open Source Project
While I don't have a specific advice for passive income, I'd like to point interested people to https://github.com/nayafia/lemonade-stand. This is a resource detailing various money-making models for open source projects, which feels like a good subset of what people might imagine when thinking about passive income, as chances are a lot of people on HN love open source as well as making money and probably strive to find a way to combine the two if they could.
In Advice for Passive Income Project
I loved this article. Disclaimer, I'm the founder of CodeFund (formerly Code Sponsor). As such, my focus is funding for open source. To start, you should check out Nadia Eghbal's Lemonade Stand (https://github.com/nayafia/lemonade-stand). She lists many different ways to generate funding, along with the pros and cons. There is no silver bullet. I believe that real substantial funding must come from all directions. Also, funding sources vary based on the personality of the maintainers. Some may prefer to go the fund-raising path with Patreon or Open Collective. Some may prefer the TideLift SLA path. Some go the route of selling merchandise, training or books. However, most paths of funding require the developer to take on the role of fundraiser, marketer, or even publisher. Developers may not want to do this and would prefer to focus on th
Read the rest
e code. This is why advertising fits most models. It provides passive, recurring and consistent income that does not require the maintainer to veer from their chosen path. It supports DHH's "fuck you" policy. The maintainer is not beholden to the advertiser with CodeFund, because there is no direct agreement. CodeFund (https://codefund.app) is an open source platform that helps fund maintainers, bloggers, and builders through non-tracking ethical ads. We only display ads based on the context of the website, not the visitor profile. Our ads are relevant and non-obtrusive to visitors. For example, go to https://jsbin.com or https://codesandbox.io.
In The complicated business of funding open source software development
Tidelift is insanely exciting and I can't wait for this to be the primary way open source software is built, sustained, and matured. Funding for open source is a crucial topic for everyone here. Nadia Eghbal's lemonade-stand [1] - A handy guide to financial support for open source - shows the myriad of solutions that have existed over the years, and none have really stood out. Unlike foundations who spend significant portions of their funding on executives and other services for a narrow subset of the OSS ecosystem, Tidelift is doing something novel by doing something simple. Make it easy for companies to buy a subscription to open source software that carries added commercial benefits [2] and then take that money and pay the maintainers. That's it. For companies and maintainers alike, this seems ideal. [1] https://github.com/nayafia/lem
Read the rest
In Tidelift wants open-source developers to get paid

Showing the 15 most recent of 24 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.