this post was submitted on 13 Feb 2026
46 points (97.9% liked)

Selfhosted

56368 readers
1235 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Unless I am blind or my search-fu is hugely failing me, I cannot for the life of me find any information on the recommended/minimum specs to self-host the matrix backend services. I'm trying to spin up a VM just to play around with it and see if I like it. Specifically, I'm looking at Synapse or Continuwuity. Any advice?

Looking for vCPUs, memory, storage.

you are viewing a single comment's thread
view the rest of the comments
[–] iamthetot@piefed.ca 2 points 13 hours ago (1 children)

Could you explain what makes an S3 bucket better suited than the default storage scheme? No pressure if not, you've already been helpful!

[–] scrubbles@poptalk.scrubbles.tech 2 points 12 hours ago (1 children)

Basically for a cloud provider s3 storage is just any storage. It's not a disk that needs to be high availability with programs reading and writing to it with an OS on top, its just blobs of data. Images, video, isos, whatever. Its meant for access that is lower than what a VM would need for an active program.

For matrix this is ideal for its content. An image uploaded will be read a fee dozen times, and then less and less until eventually it isn't really needed ever unless someone scrolls and scrolls up.

So for hosting, if you store that on a disk you're saying "this is critical to the operation of the software and must be highly available and optimized for vms reading and writing to it.". Think like m.2 ssds. Blob storage then analogous to us home labbers to throwing it on a giant nas. Its there, may take a bit to load, but its there.

Then s3 has classes too, where if you need your data even less you can pay even less trading off access times, you can get even better rates if you know you need it extremely infrequently, like audit logs. Tape drives are actually used quite a bit for those opt-in low access tiers because if you think about it the data storage is incredibly dense, but opening up a tape can be minutes or longer to access. No problem if you're pulling up some archive from 20 years ago.

[–] iamthetot@piefed.ca 1 points 10 hours ago (1 children)

Very interesting stuff, thanks!

I am not saying it's exactly the same but that does sound similar to what I am gonna try out. Main my first successful spin up I just have everything in a frankly small VM running on an ssd, but next I'm going to play around with mapping the crucial stuff on that ssd but putting media on my 8TB platter.

[–] scrubbles@poptalk.scrubbles.tech 2 points 1 hour ago (1 children)

That's how I started too, so very good plan, and good way of thinking ahead. Ssd will be fast so the app will load fast for your users, and images can take a few seconds and no one will mind.

Make sure you have a solid backup plan for both

[–] iamthetot@piefed.ca 1 points 10 minutes ago

I try to always follow 3-2-1 backups!