Self-host Element Web with Levelrail

The Element Matrix web client, served as static files and pointed at the homeserver you choose, for example the Matrix Synapse template. AGPL-3.0 licensed client. No account lives here, sign in or register on your homeserver.

  • Authorelement-hq
  • LicenceAGPL-3.0-or-later OR GPL-3.0-or-later OR LicenseRef-Element-Commercial
  • Memory64 MiB
  • Archarm64
  • Services1

How to self-host Element Web

  1. Pull the images

    One image is pulled on your server.

    Show images
    • vectorim/element-web:v1.12.33
  2. Create the app

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

  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.

Element Web requirements

Memory
About 64 MiB
Architectures
amd64 image published, arm64 image published
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
  • 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 Element Web. 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 Element Web docs page.

Deploy Element Web your way

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

Deploy Element Web from the CLI

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

levelrail-cli templates install element-web --name my-element-web

Deploy Element Web 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/element-web/install \
  -d '{
    "name": "my-element-web"
  }'

Element Web configuration

Element Web services

ServiceImagePortsVolumes
element vectorim/element-web:v1.12.33 80 none

Element Web environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
80
Volumes
none

Element Web FAQ

How much memory does Element Web need?

The catalog lists about 64 MiB of memory for Element Web.

Does Element Web run on arm64?

For Element Web, an arm64 image is published; amd64 is image published.

What licence is Element Web under?

Element Web is licensed under AGPL-3.0-or-later OR GPL-3.0-or-later OR LicenseRef-Element-Commercial, which is copyleft, so changes you distribute must be shared under the same terms.

Does Element Web need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Element Web use?

Element Web listens on port 80 inside the stack.

Can I deploy Element Web 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 Element Web, 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 vectorim/element-web:v1.12.33 is what you deploy there.

levelrail-cli templates install element-web --name my-element-web