this post was submitted on 30 Nov 2025
27 points (100.0% liked)

Self-hosting

3873 readers
4 users here now

Hosting your own services. Preferably at home and on low-power or shared hardware.

Also check out:

founded 3 years ago
MODERATORS
poVoq@slrpnk.net
sam_uk@slrpnk.net
27
Self-hosting a Matrix server for 5 years (yaky.dev)
submitted 3 days ago by Yaky@slrpnk.net to c/selfhosting@slrpnk.net
7 comments fedilink hide all child comments
 

Experiences with the Matrix protocol, Matrix Synapse server, bridges, and Element mobile app. There are some you-just-have-to-know-this issues.

TL;DR:

  • Matrix Synapse: works fine, but requires constant manual maintenance.
  • Bridges: work pretty well.
  • Element: generally OK, some issues with timely notifications, no feature parity between Element Classic and Element X, terrible on-boarding (with current setup)
you are viewing a single comment's thread
view the rest of the comments
[–] assaultpotato@sh.itjust.works 1 points 3 days ago

I've been selfhosting Synapse on Docker Compose for... maybe 1.5 years now? I'm also running bridges. I've never had to do monthly maintenance. I have around 20 users (my friends) active daily, a few federated rooms. I have message retention on and it "just worked" for me (not sure why OP had to do extra config)

I only find two of the critiques to be true in my experience:

  1. Onboarding can be confusing for non-technical users. I use SSO so no registration, but the average person doesn't know what an encryption key is, and they probably don't want to either.
  2. Synapse is written in python and as such isn't super kind to memory/cpu. I'm doing fine on my cheap Hetzner box though.

Overall synpase for me has been very much "set it and forget it". I can't remember when I last did server maintenance.