Technology

Deepgram Buys Daily, the Company Behind the Pipecat Voice AI Toolkit

Martin HollowayPublished 2w ago3 min readBased on 6 sources
Reading level
Deepgram Buys Daily, the Company Behind the Pipecat Voice AI Toolkit
source:deepgram.com

Deepgram has agreed to acquire Daily, the company that builds and maintains Pipecat, a free, open-source toolkit for making voice AI agents. The deal was announced on October 29, 2026, according to TechCrunch. Neither company has disclosed the purchase price.

A voice AI agent is a program that talks with people in real time, such as a phone assistant that listens, understands and answers. Building one takes several separate parts working together.

Daily provides hosted infrastructure for voice and video calls. It also maintains Pipecat, which sits between the system that carries the audio and the AI services that understand speech and generate replies. Think of Pipecat as a switchboard operator. It passes each piece of the conversation to the right service at the right moment.

Deepgram and Daily said they will keep Pipecat open-source. Daily co-founder Kwindla Kramer said that Deepgram CEO Scott Stephenson had committed to keeping Pipecat open-source and vendor-neutral permanently.

The two companies have a longer history than this deal suggests. Both were part of the same Y Combinator batch in 2016. Daily has raised more than $62 million in funding to date, according to PitchBook data cited by TechCrunch.

Deepgram is also launching the Real-Time Context Standard (RCS), an open protocol for voice agents. It developed the standard with the Pipecat team. RCS is meant to give parts of a voice agent, even those from different companies, a shared way to exchange real-time context. The details of its message format and governance will matter more to developers who build with it than the announcement itself.

The companies were already working together. Pipecat ships with native Deepgram services. Deepgram lists Daily.co as a partner for live transcription in video calls. Daily Bots, which Daily describes as an open-source cloud for voice AI built on Pipecat, natively integrates Deepgram. On August 17, 2026, Deepgram published instructions for building a voice agent with Pipecat using Deepgram Flux STT and Flux TTS, its speech-to-text and text-to-speech models.

Deepgram's own blog lists the Daily deal in its Announcements section, under the headline "Deepgram is acquiring Daily, makers of Pipecat, to offer the first complete, production-ready, open stack for conversational voice AI."

Deepgram announced in January 2026 that it had completed its latest funding round, in a post titled "Today We Start the Next Chapter of the Voice AI Economy." The Daily deal is a separate step. The announcement does not say how it will be financed.

The broader context here is a consolidation of the voice AI stack, meaning the set of tools that together make a voice agent work. Speech recognition, speech generation, the layer that manages turn-taking, and the hosted infrastructure that carries the call have usually come from different vendors. Placing the framework and the call infrastructure under one company that is also a major speech provider changes who controls the default path for a developer who starts with Pipecat.

In my view, the most important question for engineering teams is not the acquisition itself but whether vendor neutrality holds in practice. Pipecat's appeal has rested on its ability to swap providers behind a common pipeline. Developers who built with other speech vendors will want to watch how the roadmap, the service integrations and the governance of RCS develop after the deal closes. The stated commitments are clear, and they are the standard against which later releases can be judged.

For developers, the upside is easier to describe. A single open stack, from the call itself to the speech models, could mean less custom glue code needed to get a responsive voice agent running. An open standard for real-time context could let parts from different vendors work together. Whether that happens depends on other companies adopting RCS, and on the open-source project attracting contributors who do not work for Deepgram.