Hi fellow self-hosters! Has anyone ran Element Server Suite or updated their existing Synapse to include Element Call? How many users do you have?

I have been running Matrix Synapse server on a 1 CPU 1 GB RAM VPS for about 5 years. Just a few close people and a WhatsApp bridge (also for just a few people who use that). It worked fairly well.

Now that Element took over many of the Matrix things, they are expanding the server architecture and bundling the server install as Element Server Suite. The Community Edition is said to be aimed at “small to mid-sized deployments (1–100 users)”, but looking at the architecture and requirements… the setup requires Kubernetes (!), at least 2 CPUs and 2 GB RAM, a handful of services, each with their own sub-domain.

Is this corporatesque setup overkill for only a handful of users, or is this my inner Luddite talking? For comparison, Snikket (bundled XMPP server that provides very similar functionality) requires only 128MB RAM. Not sure if it’s worth it trying to set up Element Call alongside existing Synapse, starting over with ESS, or going to Snikket.

    • Yaky@slrpnk.netOP
      link
      fedilink
      arrow-up
      1
      ·
      15 hours ago

      What will I see? I mean I am seeing some corporatization and incompatibilities as I described.

      • mistermodal@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        52 minutes ago

        Yes and a shitton of overhead for nothing. Sorry that was a vague and unhelpful comment I’ll elaborate on my issues wjth Matrix in a larger post about tech libertarian activism and NGOs

  • tenchiken@anarchist.nexus
    link
    fedilink
    English
    arrow-up
    11
    ·
    3 days ago

    I would suggest instead looking into the deployment via the very thorough system here:

    https://github.com/spantaleev/matrix-docker-ansible-deploy

    It may seem a little overwhelming at first due to the large list of options, but underneath it boils down to some simple variables in a file. Once complete, you can then add/remove components merely with a small edit and redeploy.

    I’ve been using this for about a year, after manually doing the systems for Element and Synapse for a few years before that and HATING how kludgy things seemed.

    Once on the Ansible deploy from above, features just work. It’s been a night vs day difference without trying to convince you to pay money any time you go into an interface.

    My few users (about 2 dozen) regularly do group calls via the newer Element Call stuff (RTC) and even with a high-latency connection from one of the users using satellite internet, things work smoothly.

    XMPP / Snikket might be a better fit for your needs, but I wanted to make sure you had a chance to try out the better solution for implementing Synapse (or other Matrix servers!) before just judging by the problematic corporate deployment.

    • Yaky@slrpnk.netOP
      link
      fedilink
      arrow-up
      2
      ·
      14 hours ago

      Ironically, this was the first thing I tried for Matrix deployment circa 2019. Worked like a charm… Until a reboot. Then, since I did not know where anything was installed and how it worked, I had no idea where to even start.

      I guess it would make more sense now that I know a bit more.

  • thagoat@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 days ago

    I just switched to snikket from matrix in the last 2 weeks. I ran a matrix server for 6 years, for just 3 users. Snikket works perfectly, and the phone apps work so well without the need to constantly authenticate with a second device. Just log in.

    XMPP is a stable protocol. And snikket has ssl certs, audio/video calling, and media uploads baked right in.

    Give it a try on a modest vps and I don’t think you will be disappointed. I’m sure happy with it.

    • signaleleven@slrpnk.net
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      3 days ago

      Do you run any bridge (I forget the XMPP nomenclature). One of the reasons I run matrix (synapse) myself is to have a single interface for many instant-message platforms. I’ve been looking into migrating to XMPP (im sure my matrix deployment can be slimmed down but for now it’s a behemoth taking 4 GB of RAM…) but I’ve been somewhat discouraged by the process

    • Yaky@slrpnk.netOP
      link
      fedilink
      arrow-up
      1
      ·
      3 days ago

      Why did you switch? I went from Matrix to XMPP around 2019 since Riot/RiotX (matrix client) at the time would not get notifications in time and/or was a battery hog. And then went back to Matrix when it seemed more stable, to avoid messing with prosody configs.

      • thagoat@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        Apps had notification problems, and crashes. My gf stopped getting pictures unless she was on home wifi. Just weirdness. I set up another instance with docker on a different server, and that worked better, but 8 was tired of the silliness. Those were the main reasons I switched. I’m also a tinkerer, so I enjoy trying new projects.

  • jimmy90@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    3 days ago

    i’ve been running it for 2 users for a very long time

    frankly it’s a bit of a pain to setup but it works and it doesn’t need 2 cpus and 2 gb ram

  • stratself@lemdro.id
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 days ago

    If it ain’t broke, don’t fix it. I think it’s better hooking up Element Call to your current setup, and remove Element Web if you can BYO client.

    For a more lightweight alternative, I personally find continuwuity to be reasonably stable for the specs you mentioned. It does admin tasks in an #admins room, use an embedded database, and has no client UI so less containers needed. So continuwuity + EC should be able to run under the constraints you mentioned

    The lightest would still be any XMPP server, though its functionality does differ from Matrix overall

    • Yaky@slrpnk.netOP
      link
      fedilink
      arrow-up
      2
      ·
      3 days ago

      Any hidden nuances that one has to know for Snikket nowadays?

      E.g. with Matrix Synapse, user accounts cannot be deleted via API, DB accumulates hundreds of thousands of records in state_groups_state taking up space, and for client-side, onboarding is a pain

      • SidewaysHighways@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        3 days ago

        not that i can think of? i pop over to look at storage space every so often and it doesn’t look like it’s growing very much.

        inviting people is easy, directly from the android app.

        the snikket app itself is pretty straightforward. The only thing I would caution is telling people using the chat service to make sure their encryption button is checked or whatever.

        there are other apps that work with this, the one i use on android is conversations.

        i haven’t had to delete users yet, but that sort of thing is done directly at the home page with admin login.

        I had tried to use the Ansible playbook to get a matrix server up and running and failed for about a week straight before trying out Snicket and was texting with my mom across the country in an hour

  • normis@infosec.pub
    link
    fedilink
    arrow-up
    2
    ·
    3 days ago

    Not really understanding what problem you are trying to solve, but I have a 50 people Matrix server on Conduit, it’s running great, uses minimal resources and takes just minutes to set up. All clients support it and I haven’t seen any missing features yet.