Our take
Inactiveno commits in over a year- Activity
- 19
- Community
- 64
- Issues
- 21
- Pull requests
- 20
+35 stars in the last 30 days
- More contributors than 78% of the projects we track
Matterbridge is a capable self-hosted chat relay with unusually broad protocol support, but its measured inactivity and concentrated maintenance make it a cautious choice for new deployments.
Good fit if
- You need to connect specific supported chat platforms and can run and configure a Go service yourself.
- You can validate the bridges you depend on and are comfortable operating the last available release if upstream remains inactive.
- You want an Apache-2.0-licensed project that can run without Mattermost.
Look elsewhere if
- Your deployment requires recent upstream fixes or regular releases, since the project has had no commits in over a year and no release in over a year.
- You need a project with broadly distributed maintenance: most of the code comes from one person, despite a contributor history spanning many contributors.
- You need a connector that is not natively supported and cannot maintain or adopt a third-party API integration.
All health signals
| Last commit | 2024-12-12 (1.9 years ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 (latest v1.26.0, 2023-01-29) |
| Contributors | 100+ (top contributor: 80% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 11 years |
Checked on 2026-10-22 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
7,621Forks
743Change since Nov 13, 2026: +1 stars·0 forks
Overview
Matterbridge is a Go-based chat bridge for connecting people across messaging platforms. It relays messages between supported services such as Discord, IRC, Matrix, Mattermost, Microsoft Teams, Slack, Telegram, WhatsApp, XMPP and Zulip, so people can use different chat systems without splitting a conversation. Mattermost is not required.
You configure gateways that link accounts and channels across protocols. Matterbridge can also preserve threads when possible and handle edits, deletes and attachments. It is aimed at people and teams who want to operate their own cross-platform chat relay rather than move everyone onto one service.
Key Features
- Connect channels across a broad set of natively supported chat protocols.
- Configure multiple gateways for different accounts and channel combinations.
- Relay message edits and deletes where supported.
- Preserve threading when the connected platforms allow it.
- Handle attachments and files.
- Customize remote usernames and avatars.
- Expose a basic API that third-party connectors can use.
- Run from a binary, build from source, or deploy with Docker.
Use Cases
- A community administrator can connect an IRC channel with a Mattermost channel so participants on either service can follow the same conversation.
- A team using Slack and Discord can relay messages between corresponding channels without requiring everyone to join both platforms.
- An operator can connect chat services used by separate groups, such as a Matrix room and a Telegram group, through configured gateways.
- A game-server administrator can use a third-party API connector to relay in-game chat to supported chat services.
What you need
Detected in the repository
- Go 1.22.0 or newer (from go.mod)
- A Dockerfile, so it can run in a container
- Automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install the latest stable version with Go:
go install github.com/42wim/matterbridge
Then follow the configuration walkthrough and consult the README for binaries, Docker deployment, and build options.
Considerations
The project is marked inactive in the supplied health data: it has no commits in over a year, no recent releases, and no recent issue closures or merged pull requests. Maintenance is concentrated, with most of the code attributed to one contributor. These factors may make platform API changes and future compatibility fixes a concern.
Building requires Go 1.22 or later. The README says a build with all bridges enabled can require about 3 GB of RAM, and WhatsApp multidevice support requires a local build because of a GPL-3 library dependency. The project also describes its API as basic, and Steam is no longer supported. Check the status of each bridge you rely on before adopting it.
Found this useful?
Share it with someone who would like matterbridge.