# OSS sustainability

The recurring question for small-team OSS: how does the maintainer afford to keep doing it. The pattern catalog below comes from posts ingested into this wiki, not from a survey.

## The income sources, in rough order of how common they are

**GitHub Sponsors.** The default. Friction is low, payouts are direct, but absolute amounts tend to be small relative to the audience. [[jdx-going-full-time-oss|jdx]] reports about $500/month from Sponsors at 27k stars and top-10 Homebrew status — useful as a rough ceiling for "passive Sponsors income at the top of the dev-tools long tail."

**Documentation ads.** Banner or text ads inside the project's docs site. jdx reports ~$100/month from this channel. The number is small but the mechanism scales with traffic rather than goodwill, so it's complementary to Sponsors rather than redundant.

**Tiered memberships with perks.** Below the corporate tier, individual sponsorships need a reason beyond charity. Discord access, bi-weekly Q&As, named mentions, newsletters. jdx's tiers run $5–$50+/month for individuals, $200–$1,000+/month for companies.

**Consulting.** The maintainer sells their attention directly. Migration help, custom plugins, integration work. Common shape: "up to N days/week" so it doesn't crowd out the OSS work.

**Hosted services.** A managed offering for the open-source project — usually framed as "for teams." Often listed as a future plan rather than launched, because it's a different product with different operational requirements.

## The Ciężarkiewicz angle

[[i-dont-want-your-prs]] adds a related observation: in the LLM era, the scarce resource for a small-team maintainer isn't writing code — it's understanding, design, and review. So contributors who help with those things (feedback, bug investigation, prompts, forks-with-reports) are net positive, while drive-by PRs cost time even when the code is fine.

That reframes "supporting a maintainer" as something with two parallel tracks: pay them so they have time, and feed them inputs that respect where their time actually goes.

## Bus-factor consideration

A consistent worry across these posts is that one-person OSS is one disengagement away from stalling. jdx explicitly frames the en.dev membership tiers as funding a path to a second maintainer for mise. The same theme shows up in [[building-syntaqlite-ai]] and [[no-silver-bullet-llms]] from the other direction: design and judgment don't delegate to LLMs, so a project still needs at least one human who understands it deeply.

## What's not in scope here

This page is about funding mechanisms reported by authors in our sources. It is not about foundation/non-profit OSS funding, OpenSSF / Sovereign Tech Fund / EU NGI grants, or corporate-sponsored OSS where the maintainer is a salaried employee of the funder. Those exist; we just don't have ingest material on them yet.

## Related

- [[jdx-going-full-time-oss]] — concrete numbers from a single announcement
- [[i-dont-want-your-prs]] — how maintainer time *should* be spent in the LLM era
- [[features-to-steal-from-npmx]], [[forge]] — single-maintainer OSS in the registry/forge space
- [[phk-goodbye-bikesheds]] — Poul-Henning Kamp's forecast that age-verification, attestation, and EU accountability law end the single-maintainer BDFL model outright