Inside Pipecat's code repository sits a folder called speechmatics. It holds the code that connects Speechmatics, a British speech-recognition company, to the framework. As of Oct. 28, the folder had 153 commits, 64 of them from engineers using Speechmatics email addresses. They write the code and open a pull request, and a Pipecat maintainer reviews and merges it. Nearly all of those maintainers work for Daily.
On Oct. 29, voice AI company Deepgram said it is acquiring Daily, a real-time audio and video infrastructure company that built Pipecat and, by its account, open-sourced all of it in 2024. In a blog post, Daily co-founder Kwindla Hultman Kramer wrote that the Daily team will join Deepgram, that "Deepgram is adopting Pipecat as the core of the company's new voice AI products and services," and that Pipecat will remain open source and vendor neutral. Deepgram's press release says Pipecat will stay under its "existing BSD V2 license"; the repository's LICENSE file is BSD 2-Clause. An independent Pipecat Foundation will be "managed by a steering committee that represents the entire realtime AI ecosystem, including companies that compete with Deepgram." Deepgram sells speech-to-text and text-to-speech APIs. In the speech-to-text row of Pipecat's README, it is one of 24 listed providers, alongside Speechmatics, AssemblyAI, Soniox and Gladia.
The license isn't changing. But day to day, an open-source project is only as neutral as the people who decide what gets merged, which services the examples and docs reach for first, and what goes on the roadmap. By that measure, Pipecat has for the past year been run by one company, and that company's engineering team is now moving inside one of the providers listed in its README.
That makes the foundation the most important promise in the deal, and the one with the least detail. Neither announcement names the steering committee's members, says how it will vote or how the foundation will be funded, or says who will own the pipecat-ai GitHub organization and the Pipecat trademark. Until those details arrive, vendor neutrality is a commitment, not yet a structure anyone can check.
Who holds the merge button
An analysis of Pipecat's public Git history (snapshot: the last commit on main on Oct. 28, UTC, e89ccbe at 23:56 UTC) covers the 12 months starting Oct. 29, 2025. Most pull requests in Pipecat are merged with GitHub's "Create a merge commit" option, which creates a commit titled "Merge pull request" whose author is the person who clicked merge. Counting those commits by author shows who merges the code. Another 60 pull requests were squash-merged, which leaves no record in Git of who merged them, and are not counted.
In that year there were 1,844 such merge commits. At least 1,811 of them, about 98.2%, were merged by Daily employees (1,610 from daily.co addresses, plus 171 by Filipi da Silva Fuchter and 30 by Mark Backman from personal addresses; Fuchter's GitHub profile lists his company as daily-co). That is a lower bound: Vanessa Pyne merged 28 from a personal address, and a Vanessa appears among the Daily engineers Kramer thanks, but those 28 weren't counted.
Mark Backman alone merged 1,094, including the 30 above, close to 60% of the total. Kramer's post thanks him as the person "who has driven development of Pipecat since its launch."
Authorship is more spread out. Of 6,744 non-merge commits in the same period, 4,454, or about 66%, came from daily.co addresses. Email domains understate the share, since employees sometimes commit under personal addresses. Kramer's post says Pipecat has "almost 400 contributors" and thanks by name the 18 Daily engineers who built it.
Rivals writing code in the same repo
Much of the outside contribution comes from companies whose business overlaps Deepgram's. Over the past year there were 80 commits from speechmatics.com addresses, 52 from assemblyai.com and 32 from cartesia.ai. Across the repository's full history, each vendor's integration folder looks like this:
- speechmatics: 153 commits, 64 from Speechmatics addresses, 78 from Daily
- assemblyai: 140 commits, 35 from AssemblyAI, 80 from Daily
- soniox: 105 commits, 23 from Soniox, 67 from Daily
- gladia: 102 commits, 11 from Gladia, 80 from Daily
Deepgram addresses, by contrast, account for 3 commits in the repository's entire history, all in November and December 2025. Over that same full history, Deepgram's own integration folder has 219 commits, 163 of them from Daily addresses. Daily engineers have long been the main maintainers of Pipecat's Deepgram code, and they are about to become Deepgram colleagues.
For a company like Speechmatics or AssemblyAI, that means the integration code its engineers maintain will, unless the foundation spreads merge rights around, be reviewed by employees of a competitor.
The defaults already leaned toward Deepgram
Pipecat's sample code tilted toward Deepgram well before the deal. The snapshot's examples directory holds 523 files. Deepgram appears in 269 of them and Cartesia in 231. AssemblyAI appears in 7, Speechmatics in 5 and Soniox in 4.
There is history behind that. Kramer writes that Daily and Deepgram went through Y Combinator together in 2016 and that "since 2019, Deepgram has powered transcription inside our audio-video APIs." The numbers show that under Daily, vendor neutrality meant anyone could integrate and anyone's pull request could be merged. It never meant equal billing in the examples. The deal doesn't change that standard. It changes who employs the people applying it.
The case for trusting it
Daily is a vendor too. It sells WebRTC, telephony and other infrastructure. Yet Pipecat's transport layer ships a module for LiveKit, a direct Daily competitor, alongside Daily's own and a SmallWebRTC option that needs no commercial service at all. Daily didn't lock rivals out while it owned the project, and that record is the strongest support for the neutrality pledge.
Kramer described the business logic to TechCrunch: "If you sit in the middle of an ecosystem that's growing very fast, and have many parts of that ecosystem that are genuinely the best from your company, then everything being as open as possible is like a commercial advantage." He said Deepgram Chief Executive Scott Stephenson "was super committed to Pipecat being open source and vendor-neutral forever."
Stephenson told TechCrunch: "It's great if you're using Deepgram models, but I want you to be using the best models for your use case." Deepgram's announcement says the foundation is being set up "together with many of the organizations that have contributed to and use Pipecat," without naming them.
The BSD 2-Clause license is permissive, so anyone can fork. Pipecat already has about 3,000 forks on GitHub. Keeping a fork current is another matter: Pipecat shipped three releases, v1.13 through v1.15, between Oct. 19 and Oct. 29.
What to watch
Several outlets have already noted that the announcements leave the foundation's governance unspecified. At least four questions can be checked as answers come in: which companies sit on the steering committee and how it votes; whether the pipecat-ai GitHub organization and the trademark move to the foundation; whether anyone outside Daily and Deepgram gets merge rights; and where the foundation's money comes from.
Deepgram says Pipecat and Daily's infrastructure will underpin its coming Deepgram Voice Agent Platform. That gives Deepgram every reason to grow Pipecat, and a stake of its own in where the project goes. The first signal will show up on GitHub, the next time a Speechmatics engineer opens a pull request: who reviews it, and under what rules it gets merged.
Sources
- Daily: Deepgram Is Acquiring Daily and Establishing an Independent Pipecat Foundation
- Deepgram: Deepgram is acquiring Daily, makers of Pipecat
- TechCrunch: Deepgram acquires Pipecat-maker Daily to bolster its voice AI infrastructure
- TSN: Deepgram to Buy Daily, Pipecat Gets a Foundation
- Foundra: Pipecat's promised independence becomes the central test
- GitHub: pipecat-ai/pipecat
- Pipecat snapshot commit e89ccbe