textlint Maintainer azu: ¥2.29M a Year in OSS Sponsorships — textlint, JSer.info, and 14 Years of Continuity Built a Donation-Funded Solo Practice

Give software away for free, ask nothing in return — and ¥2.29M a year still comes in. That is OSS developer azu’s 2025 balance sheet. The proofreading tool textlint; JSer.info, a JavaScript news site updated every week for 14 years. JavaScript Primer, a book published free of charge. All of it is free, and the income comes from monthly GitHub Sponsors and donations. The “open source year in review” he publishes every New Year’s Eve includes the actual amounts, month by month.

In this site’s taxonomy, this is our strangest case. There is no product, no price, no customers. Yet there is continuous income, and seven years of it are public. It is Japan’s most transparent fixed-point observation of how far donation-funded solo development can actually go.

For scale, up front: ¥2.29M a year averages ¥190K a month. It does not work as a full-time income, but in the solo/side-project monthly-revenue distributions this site has compiled, it sits near the median. Between “you can’t live on OSS” and “OSS makes no money,” there is, in reality, a band about this wide.

The record in numbers

Donations attach to continuity, not achievements

The base level of ¥160–170K a month is not payment for any single product. Companies using textlint, readers of JSer.info, developers who learned from JavaScript Primer. The set of beneficiaries has accumulated into roughly 50 individual and corporate sponsorships.

The structurally important point is that donations attach not to one-off achievements but to a track record of continuity. JSer.info’s history (14 years, every week) is itself the predictability that “supporting this person will not be wasted.” Sponsorship is trust paid in advance, and the only collateral for that trust is past continuity. Rather than a structure where donations spike in a viral month, this is one where money gathers, little by little, around the person who does not quit. The income graph’s gentle upward slope since 2019 reflects exactly that property.

The sources of variance are recorded too. The ¥366K in January 2025 was an upswing from the Thanks OSS Award (a program in which companies give prize money to OSS), and he notes that December’s increase came from a sponsor’s account migration. The meticulousness of annotating even the reasons for the bumps is itself what sustains this dataset’s documentary value. A single corporate sponsor joining or leaving moves the number by tens of thousands of yen a month. The income is less diversified than it looks.

The apparatus for being supported is also designed

Ending azu’s case at “a story about good character” would miss the reproducible parts. The receiving apparatus is deliberately designed: the GitHub Sponsors tier structure, the explanation of how support is used, and the annual public accounting itself all function as disclosure that makes it easier for a sponsoring company to clear internal approval. For JavaScript Primer, he has set a policy of distributing Open Collective funds to contributors, paying out about ¥680K a year. What he has built goes beyond a way to receive money as an individual: a mechanism for routing funds through the project.

This is the management of a donation-funded practice. Even an activity that gives everything away has managerial work (income transparency, explaining the use of funds, distributing to contributors) and donations gather around the person who does that work carefully.

The content of his 2025 activity also explains sponsor motivation. textlint added MCP server support so AI agents can call it directly. Secretlint expanded its rules for detecting leaked API keys. JSer.info arranged its pages for AI referencing. The more companies depend on AI-assisted coding, the more the linters, security tools, and information sources underneath it become visible as “critical infrastructure enjoyed for free.” OSS sponsorship is shifting in character from goodwill donation to supply-chain maintenance cost, and azu’s income curve is a domestic observation point of that shift. Keeping OSS running alongside a main job also resonates with the labelmake case, where open-sourcing the project let outside contributions halve the codebase.

Risks and limits

Nobody discloses the fragility of this income better than azu himself. Sponsorship income drops the moment a sponsor cancels, and a substantial share of it depends on “institutional” money, Japanese corporate support programs and awards. If corporate budgets or policies shift, the number moves by tens of thousands of yen a month. And ¥2.29M a year should be read not as an amount that supports a livelihood on its own but as income that, combined with other income, raises the sustainability of the activity.

Note: this case sits at the boundary of our usual inclusion criteria (businesses operated on an ongoing basis). It is not a for-profit business, but with six years of continuous income and seven years of public records, we included it as a reference point for how an individual’s technical activity can be monetized.

11,082 contributions a year against ¥2.29M, not an hourly wage

Fourteen years of weekly updates and 11,082 contributions in 2025 alone, about 30 a day, is an input volume for which ¥2.29M a year never works out as an hourly wage. The base level of ¥160,000 to ¥170,000 a month is itself the sum of about 50 sponsors, and one corporate sponsor coming or going moves the month by tens of thousands of yen. It is more accurate to read this not as compensation for labor but as the sustaining cost of an activity that gives its output away.

From there, what azu has put in place comes into focus. The Sponsors tiers, the explanation of how funds are used, the annual public accounts, the distribution from Open Collective to contributors: none of these is mainly a way to raise income. Each translates fourteen years of activity into a form that can pass a company’s approval process. That this translation was already done in 2025, the year the maintenance of linters and information sources under AI coding started to look like a necessary expense, is what holds up the monthly figures. For comparing solo-dev revenue models, read this alongside Pomofocus (free + ads) and Inkdrop (paid subscription only), the structural differences stand out.