Overview
Spotify announces the three recipients of its 2025 FOSS Fund: FFmpeg (€30,000), Mock Service Worker/MSW (€15,000), and Xiph.Org Foundation (€25,000). The article highlights how these open source projects underpin Spotify's technology stack, featuring interviews with maintainers about project vision, fund usage, and the broader impact of corporate open source funding initiatives.
What You'll Learn
How Spotify's FOSS Fund selects and funds critical open source dependencies
Why corporate open source funding matters for project sustainability and maintainer support
How open source projects like FFmpeg, MSW, and Xiph.Org allocate corporate sponsorship funds
Why single-maintainer projects face unique sustainability challenges compared to large community-driven efforts
Key Questions Answered
What is the Spotify FOSS Fund and which projects received funding in 2025?
How much funding did FFmpeg receive from the 2025 Spotify FOSS Fund?
What is Mock Service Worker (MSW) and why does Spotify fund it?
Why does Xiph.Org Foundation receive Spotify FOSS Fund support every year?
How do open source maintainers spend corporate sponsorship funds?
What new features did MSW ship in 2025?
What are the biggest challenges facing open source sustainability?
How can companies better support open source projects they depend on?
Key Statistics & Figures
Technologies & Tools
Some links below are affiliate links. We may earn a commission if you make a purchase.
Key Actionable Insights
1Establish a structured FOSS fund program to support critical open source dependencies your company relies on. Spotify's model, running since 2022, demonstrates that selecting a small number of high-impact projects (3 per year) with meaningful funding amounts (€15,000–€30,000) is more effective than spreading thin donations across many projects.This approach strengthens the sustainability of your technology stack while building goodwill in the open source community and demonstrating corporate responsibility.
2Identify single-maintainer open source projects in your dependency tree that represent critical risk. MSW, used across Spotify's entire web testing stack, is maintained full-time by a single individual. Funding such projects directly supports the maintainer's ability to continue development and prevents abandonment of critical infrastructure.Single-maintainer projects are especially vulnerable to burnout and abandonment. Even modest funding can make the difference between a maintainer continuing or stopping work on a project your organization depends on.
3Consider joining the Open Source Pledge and establishing repeatable, long-term funding commitments rather than one-time donations. FFmpeg's maintainer specifically called out the need for reliable, recurring funding to pay full-time developers, as one-time grants don't solve the sustainability problem.The Open Source Pledge is gaining adoption across the industry, and both maintainers interviewed emphasized that predictable funding enables better project planning and developer retention.
4Go beyond financial support by providing dedicated developer time to open source projects. FFmpeg's maintainer explicitly mentioned that companies providing dedicated developers is one of the best ways to support open source sustainability, complementing monetary contributions.Combining financial and developer contributions creates a more robust support model. Developer contributions also build internal expertise with the open source tools your team relies on.
5When evaluating which open source projects to fund, consider both large community-driven infrastructure projects (like FFmpeg and Xiph.Org) and smaller but critical tooling projects (like MSW). Diversifying across project scales and types ensures broad ecosystem health.Spotify's 2025 fund recipients ranged from 25+ year old multimedia infrastructure projects with many maintainers to a single-developer testing library, showing that impact isn't correlated with project size.