Self-host Matterbridge with Levelrail

Bridges chat between platforms. The install form carries matterbridge.toml as an editable file with a local API gateway, so you add your own accounts there.

  • Author42wim
  • LicenceApache-2.0
  • Memory64 MiB
  • Services1

How to self-host Matterbridge

  1. Pull the images

    One image is pulled on your server.

    Show images
    • 42wim/matterbridge:1.26.0
  2. Create the app

    One service starts in a single Compose app, on port 4242.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Edit the config file setting to add your chat accounts and gateways, then reinstall or update to apply it. The starter exposes only the local API.

Matterbridge requirements

Memory
About 64 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
4242
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Matterbridge. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Matterbridge docs page.

Deploy Matterbridge your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Matterbridge from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain matterbridge=app.example.com.

levelrail-cli templates install matterbridge --name my-matterbridge

Deploy Matterbridge with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/matterbridge/install \
  -d '{
    "name": "my-matterbridge"
  }'

Matterbridge configuration

Matterbridge services

ServiceImagePortsVolumes
matterbridge 42wim/matterbridge:1.26.0 4242 none

Matterbridge environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
4242
Volumes
none

Matterbridge FAQ

How much memory does Matterbridge need?

The catalog lists about 64 MiB of memory for Matterbridge.

Does Matterbridge run on arm64?

For Matterbridge, arm64 support is not confirmed; amd64 is unknown.

What licence is Matterbridge under?

Matterbridge is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does Matterbridge need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Matterbridge use?

Matterbridge listens on port 4242 inside the stack.

Can I deploy Matterbridge on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Matterbridge, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image 42wim/matterbridge:1.26.0 is what you deploy there.

levelrail-cli templates install matterbridge --name my-matterbridge