FreeBSD runs in production infrastructure at Netflix, Sony, Juniper, Apple, and many others. The FreeBSD Foundation coordinates development with 13 staff and around 19 contractors (per the Foundation, 2026), on a budget that has moved between roughly $2M and $3M a year.

This post is a plain look at how FreeBSD is funded. I put together the public financial statements, the donor list, and the Cyber Resilience Act timeline. The short version: 2025 closed much better than 2024, the direction is improving, and a structural gap is still there.

The numbers

The financial data below comes from the Foundation’s published financial statements. The donations column is contributions only.

Year Donations Other income Expenses Investment income Net income Net assets
2021 $1,281,437 0 $1,260,643 +$182,591 +$203,592 $5,818,368
2022 $1,231,096 0 $1,280,936 -$340,655 -$390,555 $5,280,629
2023 $1,268,896 0 $1,928,906 +$259,133 -$400,126 $4,880,502
2024 $1,524,259 0 $2,602,008 +$224,582 -$853,594 $4,026,908
2025 $1,697,744 $644,320 $2,576,586 +$175,948 -$70,235 not published

2021 to 2024 come from the Foundation’s P&L statements and balance sheets. 2025 comes from the 2025 P&L; the 2025 year-end balance sheet was not published as of 2026-11-18. Net income is the figure the Foundation reports. The columns do not always foot exactly because some years include lines such as other income or taxes that are not shown separately here.

One reconciliation is worth flagging. For 2021 and 2022 the P&L net income does not match the change in net assets: 2021 shows +$203,592 but net assets rose only $53,079, and 2022 shows -$390,555 while net assets fell $537,739. The two gaps, about +$150K and about -$147K, roughly cancel, which suggests an amount recorded in the 2021 P&L was reversed or reclassified in 2022. The 2021 Form 990 reports $53,079 of net income. 2023 and 2024 reconcile exactly.

Donations have grown, from $1.28M in 2021 to $1.70M in 2025. Expenses grew faster for a while, from $1.26M to $2.60M in 2024, mostly because the Foundation invested in developers, hardware support, and CRA readiness. 2025 then closed with a net loss of about $70K, a big improvement over the $853K loss in 2024.

Part of the improvement came from income outside donations. The 2025 P&L lists about $644K of other income on top of the $1.70M in contributions, and investment returns added another $176K. Expenses stayed high at $2.58M, which is why the bottom line improved but did not turn positive.

For 2026 the Foundation has published the first half. Total income through June was about $626K against $1.40M in operating expenses, a net loss of $777K so far. The fourth quarter carries most of the year. In 2025 the first half closed at a net loss of $459,816 and the first three quarters at $689,277, then the full year landed at a net loss of $70,235, so the fourth quarter alone added roughly $619K. The first half of 2026, at a net loss of $777K, is about $317K weaker than the same period in 2025, which is why the half-year number should not be read on its own. The approved 2026 budget plans $2.1M in revenue against $3.06M in expenses, with another planned draw from reserves.

Reserves have come down from $5.8M at the end of 2021 to $4.0M at the end of 2024. At the current deficit planned in the 2026 budget, that is roughly four years of runway. The 2025 budget planned to draw about $1.03M from reserves, but the year closed at a net loss of only $70K. The 2025 balance sheet, when published, will show where they landed.

Where the money comes from

The Foundation publishes a donor list organized by tier, split into Partners and Corporate/Individual tabs by year. The current Partners tab, for 2026, lists NetApp and Quantum Leap Research together in the $100,000 to $249,999 band, with other partners in lower bands. NetApp has been the Foundation’s single largest cumulative corporate donor from 2019 to 2023. Quantum Leap Research’s contribution is not general support: in September 2024 the Foundation announced that Quantum Leap committed $250,000 toward laptop support and usability, with the Foundation committing $500,000 of its own toward a $750,000 program, later described as a $1M+ project. In its 2024 partnership announcement the Foundation also named the companies that had donated every year for five years: Beckhoff, Juniper Networks, Netflix, Stormshield, and Tarsnap.

Some entries on the list are not straightforward corporate decisions. An employer matching program can put a company name on the list through individual donations, and the Foundation can usually tell the difference internally even though matching gifts are not broken out in the public list. A discussion on r/freebsd, later confirmed by the Foundation, clarified this.

The Koum donations are worth noting because of their size. Jan Koum, co-founder of WhatsApp, grew up in government housing and learned to code on FreeBSD because it was free. After Facebook acquired WhatsApp for $19B in 2014, Koum donated $1M that year and another $500K in 2016. The Koum Family Foundation continued to appear on donor lists through at least 2022. Those gifts shaped the reserve trajectory for nearly a decade, but they are not a repeatable funding model.

Some support is also indirect. Companies maintain the parts of FreeBSD they depend on, and some financial contributions flow through consulting companies or matching programs. The BSD license permits this, and it is part of the trade the project made. The result is that the public donor list understates the real level of corporate involvement.

Technical contributions vs funding

A significant share of corporate contribution to FreeBSD consists of maintaining dependencies that primarily serve the contributing company. Netflix improves the network stack it runs on. Microsoft maintains the Hyper-V drivers that matter to its hypervisor. Google writes gVNIC drivers for its cloud platform. This work does benefit FreeBSD, and in some cases, most clearly Netflix, it benefits it substantially.

It is a different thing from funding the shared work that does not belong to any single product: release engineering, security advisories, CI and CD, documentation, community coordination, operational costs. That work benefits every user and rarely has a corporate owner, which also makes it the part most exposed to under-funding.

Why this happens

The gap between industrial use and financial contribution is a classic public-goods problem. The BSD license is a deliberate philosophical choice, and nothing here argues it should have been GPL. This kind of freedom produces a specific economic pattern, and that pattern has been studied for a long time.

Free rider problem

Mancur Olson’s The Logic of Collective Action (1965) showed that rational actors do not voluntarily pay for public goods when they can benefit without paying. The BSD license maximizes freedom and adoption while leaving the incentive structure intact. Anyone can benefit from the common resource without contributing to it. The community made that trade knowingly, and it paid off in adoption, with the sustainability cost carried by the Foundation.

In his 2023 year in review, Greg Wallace, then the Foundation’s Director of Partnerships and Research, wrote that the companies that donate consistently are largely the same ones active in FreeBSD development, and that the harder problem was reaching companies that use FreeBSD without participating upstream. Corporate partners grew about 20% that year over the 2019 to 2022 average, but the base stayed narrow: 50 companies contacted, 3 new partners, 11 in total.

Bystander effect

Darley and Latane (1968) described the pattern where a larger group of potential helpers makes it easier for each one to assume that someone else will act. When many large companies depend on FreeBSD, each can assume that another participant will absorb the cost.

Visibility

Public communications from the Foundation focus on delivery: conferences, releases shipping on time, hardware support gains. Quarterly financial reports are where the numbers live, but they are not where most readers look. A potential sponsor reading only the blog sees no strong signal that the Foundation needs help. Nadia Eghbal’s 2016 Ford Foundation report Roads and Bridges made the same observation for open source infrastructure more generally: under-investment persists because the state of the resource stays invisible until it breaks.

Fundraising capacity

A small team splits its time across delivery, fundraising, and CRA readiness. The Foundation has said that much of its fundraising work is staff time, donor relationships, campaign planning, and corporate conversations, and it lives inside other budget categories rather than a dedicated line. In a 13-staff organization (per the Foundation, 2026), anything that demands sustained attention from the same people reduces throughput elsewhere.

Donated skills can move the outcome, especially in areas that are not the Foundation’s home terrain. I reviewed the donation page in March 2026: it does not yet include some of the elements behavioral research associates with higher giving, such as suggested amounts, impact framing, a progress bar, or social proof. I wrote about this in a separate post on donation page design. Qualified time on fundraising pages, UX, grant writing, or documentation can have a disproportionate effect compared with what the same work would cost the Foundation to do itself.

What could change

If the gap is structural, the corrections are structural too: corporate funding, donated skills, dedicated CRA funding, public or government support, and better visibility of the financial situation.

Corporate funding

Companies that embed FreeBSD in products or services already have a formal channel through the partnership program: Platinum ($250K+), Gold ($150K to $249K), and Silver, which scales by headcount: $10,000 under 100 employees, $25,000 for 100 to 999, $50,000 for 1,000 to 4,999, $75,000 for 5,000 to 9,999, and $100,000 for 10,000 or more. Those numbers make the cost of joining concrete for a large company.

Donated skills

Part of the bottleneck does not require new salaries. Qualified time on fundraising, UX, grant writing, CRA documentation, or financial analysis can move work that engineering staff currently absorbs as a side task. An ICSE 2020 study (Overney et al., “How to not get rich”) found that very few open source projects receive meaningful donations, and those that do rarely communicate their financial situation clearly. More than 80% of the Foundation’s budget goes into program work, which leaves real margin for donated work on non-engineering problems.

Dedicated CRA funding

CRA compliance introduces work that does not sit cleanly as undifferentiated overhead. It needs a dedicated funding line, through grants, contributions from commercial users affected by the requirements, or both. Two recent examples show the model works. The Sovereign Tech Agency grant of EUR 686,400 for infrastructure modernization covered investment years 2024 and 2025. The Foundation also received a $250,000 grant from the Alpha-Omega project, backed by the Linux Foundation, to fund a Security Engineer in Residence role focused on AI-generated vulnerability reports and AI-assisted vulnerability discovery.

Public and government funding

Where regulators create new obligations for open source stewards, there is a strong argument for funding part of the capacity needed to meet them. The Sovereign Tech Agency and Alpha-Omega grants are small precedents. A commercial path is less obvious: Tidelift raised $73.5M in venture capital over seven years to pay maintainers through enterprise subscriptions, and was acquired by Sonar in December 2024 for its security intelligence, not its sustainability mission.

Visibility

The financial situation is public, but it is not surfaced in a way that easily produces attention or behavior from people who depend on the project. When fragments of the data in this analysis appeared on r/freebsd, some readers donated inside the same thread.

The CRA timeline

The EU Cyber Resilience Act entered into force in December 2024. For FreeBSD the important dates are now clear. Manufacturer obligations for actively exploited vulnerabilities came into force on 2026-09-11. The European Commission has clarified that steward reporting obligations begin on 2027-12-11, when full manufacturer obligations also apply. I wrote a broader overview in a separate post on the CRA and open source.

The Foundation has declared itself an open source steward, and the FreeBSD Core Team issued a statement of support in September 2026. The CRA Readiness Project runs through December 2026 and covers six areas: security and vulnerability handling, SBOM toolchain, public documentation, community legislative engagement, public project repository, and communications.

Concrete progress includes a cyber security policy and a CRA reporting protocol developed with the FreeBSD Core and Security Teams, currently internal; SBOM toolchain work in development and review; and public CRA guidance for business users and community members. The Foundation continues to engage with the ORC working group and ran a CRA and SBOM tutorial at EuroBSDCon 2026.

From a regulatory standpoint the Foundation has an advantage: a single recognizable entity that can speak for the entire operating system, with one SBOM story and one point of contact. The equivalent question for Linux, who is the steward for the kernel, still does not have a clean answer.

That advantage coexists with an organizational reality: release engineering and part of the security response remain largely volunteer-run. The Foundation provides developer support and infrastructure but does not manage releases or run the security team directly. Paid security capacity currently comes from fixed-term grant funding, and there is no permanent paid backup if a key release volunteer is unavailable during a reporting window.

The steward model places much of the CRA cost on the Foundation, while the reduced compliance risk sits with the manufacturers. Red Hat already has CVE Numbering Authority status and CSAF/VEX infrastructure. Canonical markets CRA compliance as an Ubuntu Pro differentiator. Those companies treat compliance as a business expense. Companies shipping FreeBSD inside their products are themselves manufacturers under the CRA, and their compliance work does not flow back to the Foundation. The 2025 Linux Foundation readiness survey found that 62% of the ecosystem was unfamiliar with the CRA and that 50% of stewards name financial support as what they need most. The 2026 survey puts the unfamiliar share at 66%.

What I don’t know

The Foundation answered several questions for this analysis, which closed most of the open gaps. One question remains outside the public picture: what happens when the Foundation approaches corporate users, how many decline, how many do not respond, how many were never asked. That information is probably sensitive, and I cannot say how much of the divergence depends on companies that were never contacted, requests without response, or explicit refusals.

Disclosure

This post uses public Foundation sources, fiscal filings, and clarifications received from the Foundation, integrated into the text where relevant.

Closing

FreeBSD’s industrial value does not yet convert cleanly into stable support for the organization that maintains the shared work. 2025 shows the direction can change. The gap between $2.1M of planned revenue and $3.06M of planned spending in the 2026 budget is still there, and the CRA adds work that needs its own funding.

Readers who want to check the underlying numbers or support the Foundation directly can start from the Foundation financials and the public donor list.


Sources: FreeBSD Foundation 2024 Profit & Loss and Balance Sheet, FreeBSD Foundation 2025 Profit & Loss, FreeBSD Foundation income statement, six months ended June 30, 2026, FreeBSD Foundation 2025 approved budget, FreeBSD Foundation 2026 approved budget, FreeBSD Foundation donor list, Quantum Leap Research and FreeBSD Foundation laptop support announcement, FreeBSD Foundation 2024 partnership growth announcement, Greg Wallace, 2023 in Review: Partnerships and Research, FreeBSD Foundation partnership program, FreeBSD Foundation CRA page, FreeBSD Q2 2026 status report, FreeBSD Q3 2026 CRA status report, Sovereign Tech Agency FreeBSD page, FreeBSD AI-assisted Vulnerability Discovery Project launch. Academic references cited inline.