https://github.com/cyclikal94/matrix-helm-charts
Collection of charts and configs to deploy services alongside ESS Community.
https://github.com/cyclikal94/matrix-helm-charts
element ess ess-community ess-helm matrix ntfy
Last synced: 3 months ago
JSON representation
Collection of charts and configs to deploy services alongside ESS Community.
- Host: GitHub
- URL: https://github.com/cyclikal94/matrix-helm-charts
- Owner: cyclikal94
- License: apache-2.0
- Created: 2026-02-05T07:09:24.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2026-02-27T00:04:20.000Z (4 months ago)
- Last Synced: 2026-02-27T03:25:18.115Z (4 months ago)
- Topics: element, ess, ess-community, ess-helm, matrix, ntfy
- Language: Go Template
- Homepage: http://cyclikal.dev/matrix-helm-charts/
- Size: 115 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Matrix Helm Charts
## Overview
A collection of helm charts to deploy Matrix-related components into Kubernetes, with example `values.yaml` files pre-configured for use with Matrix.
All charts are created and tested against a deployed [ESS Community](https://github.com/element-hq/ess-helm) instance but should work with any Matrix deployment accessible from your cluster.
## Usage
Generally speaking, installation / usage follows these steps:
1. You configure a `values.yaml` file for your environment then deploy the helm chart using it. (Matrix-specific `values.yaml` files in this repository are provided as examples, just replace the placeholder values).
2. Point your Synapse deployment at the generated App Service Registration file, i.e. if using ESS Community, just redeploy with the sample `values.yaml` per the chart `README.md`.
3. Start a DM with the bot `@componentnamebot:example.com`, i.e. `@whatsappbot:example.com`, login etc.
> [!TIP]
> You should start with the [INSTALLATION](INSTALLATION.md) guide!.
### OCI Registry (Preferred)
All charts are published as OCI artifacts on GHCR:
```bash
helm upgrade --install oci://ghcr.io/cyclikal94/matrix-helm-charts/ --namespace --create-namespace --values
```
### HTTP Registry (Legacy-Compatible)
The legacy index-based repository remains available:
```bash
helm repo add matrix-helm-charts https://cyclikal94.github.io/matrix-helm-charts
helm repo update
helm upgrade --install matrix-helm-charts/ --namespace --create-namespace --values
```
## Components
![TIP]
Click on the desired helm charts' badge to be taken to its README for detailed deployment information.
Components are organised into categories copying the [matrix.org Ecosystem](https://matrix.org/ecosystem/) section. As such components will be either `Clients`, `Bridges`, `Servers`, or `Integrations` - where components aren't present on [matrix.org](https://matrix.org/ecosystem/) I'll do my best to put them in an appropriate category. The remaining catefories of `SDKs`, `Distribution` and `Hosting` are unlikely to be applicable here.
Given this is new, I'm actively looking for useful new charts to make, I'm prioritising projects listed on [matrix.org Ecosystem](https://matrix.org/ecosystem/) likely filtering on a "Maturity" of `Stable` / `Beta` - if you have suggestions, please do raise an issue!
### Integrations
[](charts/ntfy/README.md)
[](https://github.com/binwiederhier/ntfy)
HTTP-based pub-sub notification service. Useful to allow providing Matrix push notifications on Android without Google. You'll need to be using a Matrix Android client that supports serving push notification via UnifiedPush, i.e. `Element X`.
### Bridges
[](charts/matrix-appservice-irc/README.md)
[](https://github.com/matrix-org/matrix-appservice-irc)
IRC bridge for Matrix. This bridge allows you to join IRC channels and chat to IRC users via Matrix rooms. For capabilities etc. check it's entry on [matrix.org IRC Bridges](https://matrix.org/ecosystem/bridges/irc/).
### Mautrix Bridges
Given there are so many `mautrix` bridges, I'm collating them under a dedicated section. They also, for the most part, all use the same base chart and so setup (`values.yaml` / App Service Registration) is the same for all.
#### Python Bridges
[](charts/mautrix-googlechat/README.md)
[](https://github.com/mautrix/googlechat)
A Matrix-Google Chat puppeting bridge. For all 5 of you using Google Chat this will allow continuing those conversations in Matrix. No it's not, Allo, Hangouts or Meet - why do/did they have so many. I think this is some holdover from Google+. For capabilities etc. check it's entry on [matrix.org Google Chat Bridges](https://matrix.org/ecosystem/bridges/google_chat/). For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-telegram/README.md)
[](https://github.com/mautrix/telegram)
A Matrix-Telegram hybrid puppeting/relaybot bridge. Note this is a `mautrix` python bridge, so I believe will eventually be replaced with a go variant. For capabilities etc. check it's entry on [matrix.org Telegram Bridges](https://matrix.org/ecosystem/bridges/telegram/). For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
#### Go Bridges
Double puppetting is enabled by default, and as such, any charts sharing the same `mautrix-go-base` chart version will use the same double puppet App Service registration automatically.
[](charts/mautrix-go-base/README.md)
[](https://github.com/cyclikal94/matrix-helm-charts)
The base chart used for all `mautrix-` go bridges. Created in order to reduce duplication, all dependant charts use this base chart, then extend as needed for bridge specifics.
[](charts/mautrix-bluesky/README.md)
[](https://github.com/mautrix/bluesky)
A Matrix-Bluesky DM puppeting bridge. No category for Bluesky bridges on [matrix.org Ecosystem Bridges](https://matrix.org/ecosystem/bridges/) for this one. For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-gmessages/README.md)
[](https://github.com/mautrix/gmessages)
A Matrix-Google Messages puppeting bridge. For capabilities etc. check it's entry on [matrix.org SMS Bridges](https://matrix.org/ecosystem/bridges/sms/). For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-gvoice/README.md)
[](https://github.com/mautrix/gvoice)
A Matrix-Google Voice puppeting bridge. No category for Google Voice bridges on [matrix.org Ecosystem Bridges](https://matrix.org/ecosystem/bridges/) for this one. For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-linkedin/README.md)
[](https://github.com/mautrix/linkedin)
A Matrix-LinkedIn puppeting bridge. For capabilities etc. check it's entry on [matrix.org LinkedIn Bridges](https://matrix.org/ecosystem/bridges/linkedin/). For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-meta/README.md)
[](https://github.com/mautrix/meta)
A Matrix-Meta puppeting bridge. For capabilities etc. check it's entry on [matrix.org Instagram Bridges](https://matrix.org/ecosystem/bridges/instagram/), don't let the link fool you, it also does Facebook Messaging. For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-signal/README.md)
[](https://github.com/mautrix/signal)
A Matrix-Signal puppeting bridge. For capabilities etc. check it's entry on [matrix.org Signal Bridges](https://matrix.org/ecosystem/bridges/signal/). For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-slack/README.md)
[](https://github.com/mautrix/slack)
A Matrix-Slack puppeting bridge based on [slack-go](https://github.com/slack-go/slack). For capabilities etc. check it's entry on [matrix.org Slack Bridges](https://matrix.org/ecosystem/bridges/slack/). For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-twitter/README.md)
[](https://github.com/mautrix/twitter)
A Matrix-Twitter DM puppeting bridge. For capabilities etc. check it's entry on [matrix.org X Bridges](https://matrix.org/ecosystem/bridges/X/). For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-whatsapp/README.md)
[](https://github.com/mautrix/whatsapp)
A Matrix-WhatsApp puppeting bridge based on [whatsmeow](https://github.com/tulir/whatsmeow). For capabilities etc. check it's entry on [matrix.org Whatsapp Bridges](https://matrix.org/ecosystem/bridges/whatsapp/). For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
[](charts/mautrix-zulip/README.md)
[](https://github.com/mautrix/zulip)
A Matrix-Zulip puppeting bridge. For capabilities etc. check it's entry on [matrix.org Zulip Bridges](https://matrix.org/ecosystem/bridges/zulip/). For hands-on `mautrix` docs, check [docs.mau.fi](https://docs.mau.fi/bridges/), just note you only need to care about the custom configuration (everything else is handled by the chart).
## Credits
This project has been a bunch of work, but it is nothing without the underlying projects these charts deploy. These charts could not exist without the people who built and maintain those cool things, so credit and thanks goes to them.
- [@binwiederhier](https://github.com/binwiederhier) / [binwiederhier/ntfy](https://github.com/binwiederhier/ntfy) contributors, this was the original chart / plan for this project, created to be able to deploy `ntfy` alongside `ess-helm` easily.
- [@matrix.org](https://github.com/matrix-org) / [matrix-org/matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) contributors, this was the first helm chart I setup that meant I had to figure out App Service Registration via the charts. Hopefully the way it works makes sense!
- [@tulir](https://github.com/tulir) / [@mautrix](https://github.com/mautrix) contributors, it's kinda crazy how many bridges there are and that they all nicely work the same. It meant after creating the `mautrix-go-base` chart and getting `mautrix-whatsapp` working, it was just copy/paste for the rest! As this point, they are the bulk of these charts so... you should seriously check out the repos links above!