Self-host Matterbridge on a VPS
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.
levelrail-cli templates install matterbridge --name my-matterbridgeSpecification
- Status
- Listed
- Category
- Communication
- Services
- matterbridge
- Ports
- 4242
- Volumes
- 0
- Memory
- about 64 MiB
- arm64
- unknown
- amd64
- unknown
- Settings to fill in
- none
- License
- Permissive license, Apache-2.0
- Listing
- Community template
About Matterbridge
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.
What it deploys
Matterbridge runs as one service in a single Compose app, listening on port 4242.
| Service | Image | Tag | Ports | Volumes |
|---|---|---|---|---|
| matterbridge | 42wim/matterbridge | 1.26.0 | 4242 | none |
Before you install
- CPU architecture. arm64 unknown. The scan could not read a manifest or the tag is chosen at install time. This is not a claim either way.
- Listed. It is in the catalog. Back up the data volume before changing an image tag.
Settings and environment
The catalog lists no environment variables for this template.
First run
- 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.
Install Matterbridge on a VPS
-
Install Levelrail on a fresh VPS
Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.
curl -fsSL https://levelrail.com/install.sh | sudo sh -
Sign in
Open the setup link, choose a password, then log the CLI in. The CLI install command is
curl -fsSL https://levelrail.com/install-cli.sh | shif the machine does not have it. See Getting started.levelrail-cli login --device -
Read the template
Shows the entry, including its full compose.yaml.
levelrail-cli templates get matterbridge -
Install it
This template has an install form, so the CLI fills each setting from --env, a generated secret or its default.
levelrail-cli templates install matterbridge --name my-matterbridgeTo put a service behind a domain at install, add
--domain SERVICE=HOST:levelrail-cli templates install matterbridge --name my-matterbridge --domain matterbridge=matterbridge.example.com
Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Matterbridge.
Docs and upstream
More in Communication
- Matrix Synapse (Postgres)A Matrix homeserver backed by Postgres, for self-hosted federated chat and voice/video signaling.
- MattermostAn open-source, self-hosted alternative to Slack for team messaging and collaboration.
- Matrix SynapseA federated, end-to-end encrypted chat server implementing the Matrix protocol.
- Mail server (mox, experimental)Experimental. Needs APP_EXPERIMENTAL=mail on the control plane: without it this template is hidden and cannot be installed. Install with the MAIL_FIRST_DOMAIN setting (templates install mail-mox --env MAIL_FIRST_DOMAIN=example.com). MAIL_HOSTNAME (the FQDN other servers connect to) defaults to mail. that domain and MAIL_ADMIN_EMAIL to postmaster@ that domain. Ports 25, 465, 587 and 993 are published on the host with a private bind by default. After install, open them with the CLI command mail ports open --confirm (or Open mail ports on the Mail page): that makes only those four ports public and allows them in the host firewall, then set up DNS. Webmail and the account UI are on port 8025 (private, no admin pages). The admin API and metrics are never published; never make them public. TLS: the first start makes a self-signed certificate (valid for localhost only, made by mox itself) so the server comes up with no manual steps. Replace it before sending real mail: put your certificate and key in the config volume and set MAIL_TLS_CERT_FILE and MAIL_TLS_KEY_FILE (paths under /mox/config, for example certs/cur.pem and certs/cur.key). Existing files at those paths are never overwritten. A changed certificate needs a container restart. Relay mode: set MAIL_SMARTHOST_HOST (and port, user, password) to send through a provider. Changing it needs a restart. The admin password is the generated secret SERVICE_PASSWORD_MAILADMIN. Back up the config and data volumes together. Deliverability depends on reverse DNS, SPF, DKIM and a clean IP; see the mail template guide. Licence: MIT.
- LiveKitOpen-source WebRTC server for real-time audio, video and data, with an API for rooms and tokens. The install form carries livekit.yaml as an editable file and generates the API key and secret.
- ListmonkA self-hosted newsletter and mailing list manager with a fast, dependency-light core.