Three independent OSS projects with public money above $1k/month — and what that number does not mean (2026)

A clean list of three solo maintainers who crossed $1,000 a month in the past quarter is not what the public record can support this week. The available evidence is more useful than that headline: oRPC has a single $1,000/month sponsor; Luanti lists a €1,233/month part-time developer line; AnkiDroid reports a $71,463 annual project budget.

Those are three real funding signals. None is the same as a maintainer’s net income, and none of the first-party pages proves a threshold crossing between May 6 and August 6, 2026. Treating them as paychecks would turn transparent data into a misleading success story. Treating them as useless would miss the practical question: what exactly did each payer decide to fund?

The figures below are public snapshots checked on August 6, 2026. The distinctions are the point.

The public pages describe oRPC as a middleapi project, Luanti as a community collective hosted by Open Source Europe, and AnkiDroid as an open-source team hosted by Open Source Collective. None of the cited pages identifies a venture-backed company or corporate parent. That is why they fit this edition’s independent-maintainer frame; it is not proof that every contributor works alone or that every dollar reaches one person.

1. oRPC: one dependent company makes the sponsorship legible

What it is: oRPC is an MIT-licensed TypeScript library for building end-to-end type-safe APIs that also follow OpenAPI standards. The middleapi/orpc repository shows 5.4k GitHub stars. 1

Public money figure: ScreenshotOne’s sponsorship disclosure lists oRPC at $1,000 per month, sponsored since March 15, 2026. It records five payments totaling $5,300, including $300 in GitHub Sponsors fees. 2

That is strong evidence of a recurring sponsor commitment. It is not evidence of oRPC’s total monthly income, the maintainer’s take-home pay, or the amount that reached the maintainer after fees. One company’s line item is still a meaningful floor: a real user with a real dependency decided that keeping the project healthy was worth a four-figure monthly commitment.

Model: sponsorship attached to paid dependency risk. The payer is not being asked to reward an abstract public good. ScreenshotOne says it relies on open source to build and operate its screenshot service, and the sponsorship page links to its own oRPC migration story.

The trigger: On March 15, ScreenshotOne published the technical reason for moving from API routes and Server Actions to oRPC. The team wanted explicit client/server boundaries, stronger end-to-end typing, less framework-specific coupling, easier reuse outside React, and OpenAPI support. It also described security and operational concerns around Server Actions. 3

The dates support a sequence: ScreenshotOne adopted oRPC for a production need, then publicly listed a $1,000/month sponsorship. They do not prove that the migration caused the payment. The honest trigger description is therefore narrower: oRPC became commercially legible when a dependent company could point to the code as part of its own operating stack.

If you maintain a project like oRPC, would this work for you?

Possibly, if your code sits in a company’s production path and you can name the cost of it failing. A sponsor pitch becomes stronger when the payer already depends on your release cadence, security fixes, or compatibility work. The project does not need millions of stars; it needs a concentrated buyer with a reason to care next month.

The catch is that you cannot manufacture this with a $1,000 tier alone. The evidence here is one sponsor and one dependency story. If your users are mostly hobbyists, a corporate sponsorship tier may be an invitation to ignore you rather than a price signal.

2. Luanti: a funded developer line inside a community budget

What it is: Luanti, formerly Minetest, is a free open-source voxel game engine with easy modding and game creation. Its LGPL-2.1 GitHub repository shows 13.4k stars. 4

Public money figure: The Luanti Open Collective page lists an estimated monthly budget of €928 and, under its team section, a “Part-time dev” line of €1,233 per month. The same page shows a current balance of €2,238, 67 contributions totaling €3,717.76, and 13 recurring contributions totaling €1,759. 5

The €1,233 line is the relevant number, but its label matters. The page does not say that one maintainer has received €1,233 every month. It sits inside a community collective whose stated expenses include infrastructure, ContentDB, forums, and conference travel. The page also says the collective may pay developers and freelancers in the future. This is a project-funded capacity line, not a verified personal salary.

Model: sponsorship and community funding for a shared game platform. The scarce thing being funded is not a premium plugin. It is contributor time around an engine, its content ecosystem, infrastructure, and outreach.

The trigger: Luanti’s July 2 blog post describes an April appearance at Radioamatore Tech Expo in Pordenone, Italy. The project ran four connected laptops, attracted children and educators, and received an invitation and attendance support from the Pordenone Linux User Group; some costs were paid by the Luanti nonprofit. 6

That is a recent change in outreach, not a proven earnings trigger. The public record does not say that the expo caused the €1,233 developer line, or when the line crossed €1,000. What it does show is a project making its funding case concrete: events, education, infrastructure, and a visible contributor role. The money has a destination a backer can understand.

If you maintain a project like Luanti, would this work for you?

Community funding is a fit when the project has a public-good shape and recurring costs that users can see. A game engine with servers, content distribution, events, and educational use has more to explain than “please keep coding.” It can show what a contribution buys and why independence matters.

Do not copy the €1,233 number into a personal income forecast. Luanti’s page reports €307.17 in expenses paid, €2,238 in today’s balance, and a collective-wide financial history. A budget line can be an intention, a target, or an approved role; it is not automatically a disbursement. Publish those categories separately if you use a collective.

3. AnkiDroid: a large project budget built from small, explicit work units

What it is: AnkiDroid is a semi-official Android port of the open-source Anki spaced-repetition system. The ankidroid/Anki-Android repository shows 11.5k stars and uses GPL-3.0 for the main project. 7

Public money figure: AnkiDroid’s Open Collective page reports an estimated annual budget of $71,463.10, equivalent to roughly $5,955 per month if spread evenly. It also offers a $150/month sponsorship for small organizations that funds 10 hours of developer work, and a $300/month organization tier for 20 hours. The page reports $206,001.80 raised and $131,626.64 disbursed over time. 8

The budget clears the $1,000/month threshold by a wide margin. It still does not establish that any individual maintainer earns $5,955/month. The page says contributions go directly to people working on AnkiDroid, but the project has an open-source team, multiple admins, and a contributor pool. The honest category is team funding, not solo-maintainer income.

Model: sponsorship for paid contributor time, sold in understandable units. The organization tiers tell a company what it is buying: 10 or 20 hours of maintenance and feature work each month. That is a more concrete offer than an undifferentiated donation, while retaining a free app for users.

The trigger: AnkiDroid’s December 31, 2025 year-end update says contributions helped maintainers cut down on day jobs and justify the time spent on the app. It reports roughly 800,000 additional unique users, seven big releases, about 1,882 commits from roughly 85 contributors, and 1,708 new Open Collective backers during 2025. 9

Those figures explain why the funding offer is credible, but they do not prove a new $1,000 crossing in the past quarter. The nearest public trigger is sustained product growth paired with a clear promise: contributions buy more maintainer time. That is a plausible mechanism, not a disclosed causal event.

If you maintain a project like AnkiDroid, would this work for you?

It can work when users depend on the software for a daily practice and companies benefit from its maintenance without needing a private enterprise fork. The important design choice is to sell a bounded unit of work: hours, releases, compatibility work, or a named maintenance area.

The model is harder for a small library with no contributor pool. A $300 tier that funds 20 hours is credible only if you can actually schedule, report, and deliver those hours. If the money is split among a team, say so. The project’s transparency is part of the offer because the payer is buying continuity, not a feature that appears instantly.

The number you should put on your own page

These three cases produce three different answers to “How much do you make?”

oRPC: one company’s public commitment is $1,000/month. Total project income and maintainer net income are not disclosed.
Luanti: a €1,233/month part-time developer line appears inside a community collective. The page does not prove that it was paid out.
AnkiDroid: a $71,463 annual project budget supports a team, with $150 and $300 monthly work-unit tiers. It is not one maintainer’s paycheck.

That distinction changes the advice. If you report only the largest number, readers will assume it is personal recurring revenue. If you report only take-home pay, you may hide the operating budget that made the work possible. Publish at least four fields: money received, money committed, money disbursed, and who gets paid.

The strict filter for this channel asks for a public crossing event in the past quarter. These pages do not supply that event for all three projects. They do supply current, first-party funding evidence and recent changes in product, outreach, or contributor capacity. That is enough to study the models; it is not enough to claim three newly crossed personal-income milestones.

Model-fit matrix

Project archetype	Models to test first	Why the fit is plausible	What to prove before copying it
Library	Sponsorship, paid support, documentation/books	A production dependency creates a recurring need for reliability, compatibility, and specialized help. oRPC shows the strongest version of this pattern in this issue.	Name the buyer’s operational risk and separate sponsor commitments from maintainer income.
Framework	Sponsorship, dual license, paid support	Frameworks shape commercial architecture, so companies may pay for maintenance priority, support, or a commercial boundary.	Show why the free license is insufficient for a real buyer; do not invent a license boundary for pricing theater.
CLI tool	Hosted version, pro plugin, sponsorship, documentation/books	The local tool can stay free while teams pay for hosted state, integrations, policy controls, or dependable support.	Identify the recurring workflow that the free binary does not solve.
Web tool	Hosted version, paid support, community funding, pro plugin	Operators can pay to avoid running stateful services, while public-good projects can fund contributor time and infrastructure directly. AnkiDroid and Luanti show why the funding destination must be explicit.	Publish usage, operating costs, committed work, and disbursements separately.

The practical threshold is not $1,000. It is a payer who can explain what the next month’s money buys. If you cannot name that unit, a public earnings number will be marketing, not a monetization model.

참고 출처

1
oRPC repositorygithub.com
2
Supporting Open Sourcescreenshotone.com
3
From API Routes and Server Actions to oRPC in Next.jsscreenshotone.com
4
Luanti repositorygithub.com
5
Luantiopencollective.com
6
Luanti at Radioamatore Tech Expoblog.luanti.org
7
AnkiDroid repositorygithub.com
8
AnkiDroidopencollective.com
9
AnkiDroid 2025 #wrappedopencollective.com