Skip to main content
Community integrations are Pipecat services built and maintained by developers in the community. They live in their own repositories, ship as separate packages, and extend Pipecat beyond the services the core team maintains. Browse them on the Supported Services page — community integrations are marked with a Community maintainer badge, and each has its own page with install and usage details.

​
Using a community integration

  • Community-maintained. Built and maintained by their authors, not the Pipecat team. Pipecat does not test, review, or officially support them.
  • Installed separately. Each ships as its own package (e.g. uv add pipecat-replicate), versioned independently of pipecat-ai.
  • Support lives on the source repo. Report issues and request changes on the integration’s repository, linked from its service page.
  • Evaluate before depending on it. Check the repository’s activity, changelog, and last tested Pipecat version.

​
Building an integration

Anyone can build and publish a Pipecat integration. The program gives you:
  • Base classes and patterns to follow for each service type (STT, LLM, TTS, image, vision, telephony, and more)
  • Naming and packaging conventions that keep your integration discoverable
  • A path to get listed on the Supported Services page, alongside core services

Read the Community Integrations Guide

Base classes, examples, naming conventions, and how to submit your integration and its docs.