Skip to main content
Pipecat is an open-source voice pipeline you host yourself. Unlike the SIP-trunk providers, you don’t configure Pipecat as a carrier - instead you drop the Unpod brain into a Pipecat pipeline as a FrameProcessor. Audio that Pipecat captures flows through your DialogMachine, and the reply streams back out the same pipeline.
Pipecat is a runtime, not a SIP provider. There’s no Dashboard/API provider config - you wire it in code. The full, working integration lives in the embedding guide.

Pipecat embedding guide

The drop-in FrameProcessor, install steps, and a complete pipeline example.

​
How it fits

🎙️Mic / SIP audioAny Pipecat transport
① frames
⚙️Pipecat pipelineSTT · VAD · TTS stages
② user turn③ reply tokens
🧠Unpod FrameProcessorDialogMachine
④ TTS stream
🔊Audio outLow-latency reply
  • Bring audio in - any Pipecat transport (WebRTC, Daily, telephony) feeds frames.
  • Insert the brain - add the Unpod FrameProcessor so each user turn drives your DialogMachine.
  • Stream the reply - tokens stream back through Pipecat’s TTS stage for low latency.

​
When to pick Pipecat

Choose Pipecat when…Otherwise consider
You want a fully self-hosted, open-source pipelineVapi (managed)
You already run a Pipecat app and want to add a brainUnpod Voice (native runtime)
You need fine control over each pipeline stageLiveKit (low-latency SIP)

Bring your agent

The adapter pattern any runtime uses.

All platforms

Back to the integrations overview.