Run a Lightweight Matrix Homeserver on Raspberry Pi 4

Yes—a Raspberry Pi 4 can run Conduit, and the project publishes ARM64 builds. For a small personal or family homeserver, the most important setup choices are a 64-bit OS, a permanent Matrix server name, persistent storage, and working HTTPS routing. Conduit currently describes itself as beta, so keep it updated and do not assume a Pi 4 has a specific supported user capacity; the project does not publish a Raspberry Pi 4 capacity benchmark.

Is Conduit the right fit for this Pi?

Conduit is a lightweight Matrix homeserver with RocksDB as its recommended database backend. Its official deployment docs list an aarch64 binary and OCI image, which matches a 64-bit Raspberry Pi OS installation. The project’s changelog listed v0.10.15, dated September 30, 2026, when checked on October 10, 2026. The preceding v0.10.14 release fixed an account-access vulnerability and recommended upgrading promptly. That history makes update monitoring part of the setup, not an optional later task.

Conduit’s website still labels the project beta and notes that some features are missing. Before choosing it, check that its current feature set meets your needs, especially if you depend on bridges, advanced administration, or broad client compatibility. A Pi can be a practical host for a small deployment, but traffic, media use, and federation activity affect performance. Start with a modest user group and watch memory, temperature, and storage use rather than relying on a promised user count.

What should you decide before installing?

  • Choose the Matrix server name. In this example, it is matrix.example.org. This domain appears in users’ Matrix IDs, such as @alex:matrix.example.org. Choose a domain you control and plan to keep; changing it later is not a simple hostname edit.
  • Plan public access. Give the domain a DNS record pointing to your public IP address. Configure router forwarding and a reverse proxy with a valid HTTPS certificate. Conduit’s deployment guidance requires HTTPS and says federation traffic must be reachable on port 443 and/or 8448, depending on your discovery and proxy arrangement.
  • Use 64-bit Raspberry Pi OS. Check the architecture with uname -m. It should report aarch64. Docker’s current Raspberry Pi guidance notes that future Docker Engine major releases no longer provide packages for 32-bit Raspberry Pi OS; on 64-bit ARM it directs users to Debian’s arm64 installation instructions.
  • Keep the database persistent. Store Conduit’s data on a persistent directory or Docker volume and include it in a tested backup plan. Do not store the only copy in a container’s writable layer or on a removable card you might reformat.

How do you start Conduit with Docker?

Install Docker Engine and the Compose plugin using the current instructions for your Raspberry Pi OS version. Then confirm Docker is running. The Conduit documentation lists the stable Docker Hub image registry.gitlab.com/famedly/conduit/matrix-conduit:latest and ARM64 OCI images. Pull the stable image and check that Docker selected an ARM64 image:

docker image pull registry.gitlab.com/famedly/conduit/matrix-conduit:latest
docker image inspect registry.gitlab.com/famedly/conduit/matrix-conduit:latest \
  --format '{{.Architecture}}'

Continue only if the reported architecture matches your 64-bit OS. Create a working directory and a Compose file:

mkdir -p ~/matrix-conduit/data
cd ~/matrix-conduit
nano compose.yaml

Use this configuration as a starting point. It assumes the reverse proxy runs on the Pi host and forwards Matrix requests to port 6167. Replace the example server name. The empty CONDUIT_CONFIG tells the container to use environment variables, as the current Conduit Docker instructions require for this setup.

services:
  conduit:
    image: registry.gitlab.com/famedly/conduit/matrix-conduit:latest
    container_name: conduit
    restart: unless-stopped
    ports:
      - "127.0.0.1:6167:6167"
    volumes:
      - ./data:/var/lib/matrix-conduit
    environment:
      CONDUIT_CONFIG: ""
      CONDUIT_SERVER_NAME: "matrix.example.org"
      CONDUIT_ADDRESS: "0.0.0.0"
      CONDUIT_PORT: "6167"
      CONDUIT_DATABASE_BACKEND: "rocksdb"
      CONDUIT_ALLOW_REGISTRATION: "true"
      CONDUIT_REGISTRATION_TOKEN: "${CONDUIT_REGISTRATION_TOKEN}"
      CONDUIT_ALLOW_FEDERATION: "true"
      CONDUIT_TRUSTED_SERVERS: '["matrix.org"]'

Create a private registration-token file and launch the service:

umask 077
printf 'CONDUIT_REGISTRATION_TOKEN=%s\n' "$(openssl rand -hex 32)" > .env
docker compose up -d
docker compose logs --tail=100 conduit

The token is needed to register your first account; Conduit makes the first created user the server administrator. Keep the .env file private and do not commit it to a public repository. The example binds Conduit to the Pi’s loopback interface, so it is reachable only through a reverse proxy running on the same host. If your proxy runs in another container or on another machine, use a private Docker network or a protected private interface instead of exposing port 6167 publicly.

How do you make the server reachable and secure?

Configure your reverse proxy to serve the domain over HTTPS and forward Matrix client and federation requests—including /_matrix/ and /.well-known/matrix/—to Conduit. The simplest public arrangement depends on your proxy and whether federation uses port 8448 or delegated discovery over port 443. Follow the matching example in Conduit’s Docker deployment documentation; do not copy a proxy snippet without adapting its hostnames, certificate handling, and network paths.

If you use the same domain for server_name and the homeserver URL, make sure clients can reach the advertised HTTPS endpoint. If Conduit is hosted on a separate subdomain from the Matrix ID domain, configure both /.well-known/matrix/client and /.well-known/matrix/server as described in the delegation guide. Opening a port alone does not configure discovery or TLS.

Register your administrator account promptly with a Matrix client that supports registration tokens. Then turn off open registration unless you intentionally want others to create accounts. In Compose, change CONDUIT_ALLOW_REGISTRATION to "false", remove the registration token from the service environment, and recreate the container with docker compose up -d. Your bind-mounted data directory remains in place. Review who can access the Pi’s Docker socket and configuration files, because they can reveal or change server secrets.

How can you confirm the setup works?

Check the local Matrix client API through the public HTTPS hostname:

curl -fsS https://matrix.example.org/_matrix/client/versions

A JSON response confirms that the client API is reachable; it does not prove federation is working. Run the official Matrix Federation Tester for your server name and correct any DNS, TLS, port-forwarding, or .well-known errors it reports. Finally, log in with your new account, confirm it has administrator access, and test a message in a room with a user on another homeserver if federation is part of your goal.

The technical details above were checked against Conduit’s official Docker, configuration, delegation, and changelog pages on October 10, 2026. See the Conduit Docker deployment guide, ARM64 binary and generic deployment guide, configuration reference, delegation guide, Conduit changelog, and Docker’s Raspberry Pi OS installation notes for details that vary by release.

Leave a Comment

Run a Lightweight Matrix Homeserver on Raspberry Pi 4

Set up Conduit on a 64-bit Raspberry Pi 4 with persistent data, HTTPS federation, protected registration, and checks for a working homeserver.

Set Up a Custom Matrix Room Alias on Your Own Domain

Give a Matrix room an easy-to-share address on your domain using Element or the Matrix API, with checks for permissions, Synapse naming, and federation.

Set Up coturn for Reliable Matrix Voice and Video Calls

Configure coturn and Synapse with matching TURN credentials, open the required relay ports, and verify that Matrix clients can obtain relay candidates.

Deploy Matrix Synapse with Docker Compose and PostgreSQL

Deploy Matrix Synapse with Docker Compose and PostgreSQL

Set up a persistent Synapse homeserver with Docker Compose, PostgreSQL, a private config, and checks before exposing it through HTTPS.

Customize Element Web’s Theme and Branding

Set a branded name, custom colors, and login assets for your Element Web deployment while understanding which parts remain Element-branded.

Raise Synapse’s Systemd File Limit Without Guesswork

Raise Synapse’s Systemd File Limit Without Guesswork

Diagnose whether Synapse hit its per-process open-file cap, set a systemd drop-in for the right service or worker, and verify the live limit.

Element Shows “Failed to Decrypt”? Restore the Missing Room Key

Element Shows “Failed to Decrypt”? Restore the Missing Room Key

Find out whether the error is limited to one browser or one event, then use Element’s recovery key or a trusted device without risking your remaining encrypted history.

Clean Up Old Synapse Messages and Media Without Losing Data

Use Synapse’s history and media purge APIs or retention settings to remove stale data safely, then verify completion and disk-space recovery.

Build a Matrix Echo Bot in Python with Simple-Matrix-Bot-Lib

Build a Matrix Echo Bot in Python with Simple-Matrix-Bot-Lib

Install the current library, connect a dedicated Matrix account, and run a small !echo bot with safer credential handling and a clear test.

Connect Matrix to WhatsApp, Telegram, and Discord with Separate Bridges

Connect Matrix to WhatsApp, Telegram, and Discord with Separate Bridges

Set up three mautrix bridges with separate registrations, logins, and tests—and avoid Docker networking, account-policy, and sync surprises.