Plug-N-Meet is an MIT-licensed, self-hosted web conferencing system written in Go that runs on LiveKit's WebRTC infrastructure and is meant for teams, developers, and organizations that want to embed video meetings with an AI meeting agent into their own websites, applications, or systems.

What it is

Plug-N-Meet is a web conferencing platform split into three core components. plugNmeet-server is the backend, written in Go, and handles all API and business logic. It is paired with plugNmeet-client, the main frontend built with React and Redux, and plugNmeet-recorder, a dedicated Go application that manages MP4 recordings and RTMP broadcasting. It sits in the WebRTC ecosystem and is built on the high-performance WebRTC infrastructure of LiveKit, with the project's topic list also pointing to Pion, WebRTC meetings, and AI agents.

The concrete problem it solves is ownership of the meeting stack. Rather than sending users out to a hosted third-party conferencing service, Plug-N-Meet lets a site or application host the meeting experience itself and integrate it into an existing website, application, or system. It provides the meeting server, the browser client, and the recording/broadcast worker as separate, self-hosted pieces, so the video conferencing layer becomes part of the operator's own software rather than an external dependency.

Key capabilities

• Adaptive streaming through Simulcast and Dynacast, with support for the H264, VP8, VP9, and AV1 codecs to keep calls stable on weak networks.
• Collaboration tooling that includes HD audio and video, screen sharing, virtual backgrounds, a collaborative whiteboard with office file support for PDF, DOCX, and PPTX, a shared notepad, polls, and breakout rooms.
• WebRTC-based encryption by default, with optional End-to-End Encryption (E2EE) applied to all media and data channels.
• An AI Meeting Agent that produces live spoken translations, real-time transcription, and automated summaries with action items, reachable through the Artifacts API.
• A SIP gateway for telephone dial-in, letting participants join the audio of a meeting from a standard phone number without internet access.
• Recording and broadcasting through reliable MP4 recording, RTMP/RTMPS output to services such as YouTube, and RTMP/WHIP ingress for production tools such as OBS.
• Integration and customization surfaces that include an API plus official PHP and JavaScript SDKs, ready-to-use plugins for WordPress, Moodle, and Joomla, LTI support for compatible LMS platforms, and the ability to change UI, features, branding, and URLs without modifying core code.

Who uses it and how

• Operators of WordPress, Moodle, or Joomla sites install the corresponding plugin or component to add meetings without building a conferencing frontend.
• Schools and training providers connect it to any compatible LMS through LTI, so courses can launch sessions from inside the learning platform.
• Developers embedding conferencing into an existing product use the API with the PHP or JavaScript SDK, and can customize branding and URLs without forking the core code.
• Mobile and desktop teams follow the hybrid integration model, combining a native media layer with the full plugNmeet web client UI for iOS, Android, Flutter, React Native, or desktop.
• Broadcasters and event producers use RTMP/WHIP ingress with tools such as OBS, push RTMP/RTMPS output to YouTube, and record sessions to MP4 via plugNmeet-recorder; audiences with only a phone can join audio through the SIP gateway.

Getting started

The README points to a simple installation script that deploys all necessary components in minutes, documented in the installation guide at https://www.plugnmeet.org/docs/installation. A public demo is available at https://demo.plugnmeet.com/.

How it compares

Among the tools named in the project's own materials, LiveKit is the closest relative: LiveKit supplies the underlying WebRTC media server, while Plug-N-Meet builds on it and adds the meeting UI, recording and broadcasting worker, AI meeting agent, SIP dial-in, and ready-made CMS and LMS plugins. The README does not list specific paid conferencing products that Plug-N-Meet is positioned to replace, so no direct licence, hosting, or cost comparison to named commercial services is available from these facts.

When to use it — and when not

Choose it when the meeting experience has to live inside your own infrastructure and the team can operate several moving parts: plugNmeet-server, plugNmeet-client, plugNmeet-recorder, and a LiveKit deployment beneath them. Anyone who wants a zero-operations hosted service, or who lacks the capacity to run and update that stack, should not pick this project. The README excerpt is also thin on supporting infrastructure such as database, storage, and mail configuration, and the repository shows a modest 534 stars with 11 open issues, so operators should expect to read the full documentation and source before committing.

docker run --rm -p 8080:8080 \
    -v $PWD/config.yaml:/config.yaml \
    mynaparrot/plugnmeet-server \
    --config /config.yaml \