Congratulations to the recipients of the 2025 Spotify FOSS Fund

Dave Zolotusky
6 min readintermediate
--
View Original

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

1

How Spotify's FOSS Fund selects and funds critical open source dependencies

2

Why corporate open source funding matters for project sustainability and maintainer support

3

How open source projects like FFmpeg, MSW, and Xiph.Org allocate corporate sponsorship funds

4

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?
The Spotify FOSS Fund, established in 2022, provides monetary support to open source projects that underpin Spotify's technology stack. In 2025, three projects received funding: FFmpeg (€30,000) for multimedia processing, Mock Service Worker/MSW (€15,000) for API mocking in JavaScript/TypeScript testing, and Xiph.Org Foundation (€25,000) for audio codecs and containers including Ogg, Opus, Vorbis, and FLAC.
How much funding did FFmpeg receive from the 2025 Spotify FOSS Fund?
FFmpeg received €30,000 from the 2025 Spotify FOSS Fund. The project, which has been under continuous development for over 25 years, plans to use the funding for hardware purchases, travel to conferences, and funding development projects. FFmpeg is written almost entirely by volunteers, making external funding crucial for its sustainability.
What is Mock Service Worker (MSW) and why does Spotify fund it?
Mock Service Worker (MSW) is an industry-standard JavaScript library for API mocking, created and solely maintained full-time by Artem Zakharchenko. Spotify uses MSW for unit test coverage and throughout their web stack. A Spotify developer described it as making 'writing useful tests in the JavaScript/TypeScript stack not only possible but easy.' MSW also received funding from the 2024 Spotify FOSS Fund.
Why does Xiph.Org Foundation receive Spotify FOSS Fund support every year?
Xiph.Org has received Spotify FOSS Fund support every year since the fund was established in 2022. The foundation stewards essential audio containers and codecs — including Ogg, Opus, Vorbis, and FLAC — that have powered Spotify's audio delivery from its earliest days and remain fundamental to music, podcasts, and audiobooks. Xiph also produces documentation and educational materials used in Spotify's onboarding resources.
How do open source maintainers spend corporate sponsorship funds?
Usage varies by project scale. FFmpeg allocates funds to hardware purchases, conference travel, and development projects. MSW's sole maintainer Artem Zakharchenko uses funds primarily for personal sustenance while working full-time on open source, and seeks ways to financially support active contributors. The article highlights how funding directly enables maintainers to dedicate time to critical infrastructure projects.
What new features did MSW ship in 2025?
In 2025, MSW shipped a new Interceptors architecture utilizing custom mock agents that tap into the network at the node:net level, and added first-class support for Server-Sent Events (one of the most requested features). For 2026, MSW plans a completely revamped internal architecture and remote request interception, which has been in development for years due to its technical difficulty.
What are the biggest challenges facing open source sustainability?
According to the maintainers interviewed, the biggest challenges include securing long-term, reliable funding for full-time developers. FFmpeg's Kieran Kunhya advocates for companies providing dedicated developers and repeatable funding. MSW's Artem Zakharchenko notes difficulty in getting contributors to accept financial compensation, highlighting the need for better models to support external contributions sustainably.
How can companies better support open source projects they depend on?
The article presents several approaches: financial contributions through FOSS funds, joining the Open Source Pledge, providing dedicated developers to work on open source projects, offering repeatable long-term funding rather than one-time donations, and individual-level sponsorship. Both maintainers emphasize that 'giving back' — whether financially, through code contributions, or by other means — is the best way to ensure project longevity.

Key Statistics & Figures

FFmpeg FOSS Fund allocation
€30,000
Amount received by FFmpeg from the 2025 Spotify FOSS Fund
MSW FOSS Fund allocation
€15,000
Amount received by Mock Service Worker from the 2025 Spotify FOSS Fund
Xiph.Org FOSS Fund allocation
€25,000
Amount received by Xiph.Org Foundation from the 2025 Spotify FOSS Fund
FOSS Fund program duration
Established in 2022
Year the Spotify FOSS Fund was created
FFmpeg development history
Over 25 years
Duration of continuous, active development on FFmpeg
Total 2025 FOSS Fund distribution
€70,000
Combined total distributed across three recipient projects

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Multimedia Processing
Ffmpeg
Decoding, encoding, transcoding, muxing, demuxing, filtering, streaming, and playing multimedia files
Testing
Mock Service Worker (msw)
Industry-standard JavaScript library for API mocking used for unit test coverage and throughout Spotify's web stack
Audio Codec/Container
Ogg
Audio container format stewarded by Xiph.Org, used in Spotify's audio delivery
Audio Codec
Opus
Audio codec stewarded by Xiph.Org, fundamental to Spotify's products
Audio Codec
Vorbis
Audio codec stewarded by Xiph.Org, used in Spotify's audio delivery
Audio Codec
Flac
Lossless audio codec stewarded by Xiph.Org, used in Spotify's audio delivery
Web Protocol
Server-sent Events
First-class support added to MSW as one of the most requested features
Programming Language
Javascript
Primary language for MSW API mocking library
Programming Language
Typescript
Used alongside JavaScript in Spotify's web testing stack with MSW
Runtime
Node.js
MSW's new Interceptors architecture taps into the network at the node:net level

Key Actionable Insights

1
Establish 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.
2
Identify 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.
3
Consider 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.
4
Go 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.
5
When 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.

Common Pitfalls

1
Relying on critical open source infrastructure without providing financial or development support. Projects like FFmpeg, which is written almost entirely by volunteers, power massive commercial services but face ongoing sustainability challenges without corporate funding.
Companies should audit their open source dependencies and establish formal support programs rather than assuming volunteer maintenance will continue indefinitely.
2
Assuming that one-time donations are sufficient for open source sustainability. FFmpeg's maintainer specifically highlighted the need for long-term, reliable, and repeatable funding to pay full-time developers rather than sporadic grants.
Recurring funding commitments and programs like the Open Source Pledge create predictable income streams that enable maintainers to plan development roadmaps effectively.
3
Overlooking single-maintainer projects as funding risks. MSW is maintained full-time by a single person despite being an industry-standard library used by hundreds of thousands of developers. This creates significant bus factor risk for dependent organizations.
Organizations should identify single-maintainer dependencies and prioritize them for funding, as the loss of one developer could impact their entire testing or development workflow.

Related Concepts

Open Source Sustainability
Foss Funding Models
Open Source Pledge
Corporate Open Source Support
Multimedia Codec Development
API Mocking And Testing
Audio Streaming Infrastructure
Volunteer-driven Software Development
Single-maintainer Project Risks
Open Source Governance