Hey dear community, we just launched today our fully managed hosting of Lemmy

We offer to do Deployment / Security / DNS / SMTP / Monitoring / Alerts / Backups / Automated updates / Handle migrations / Fully automated but with Human support :)

We deploy each instance on a dedicated VM, and we provide full root access as well if you want to customize anything.

Pricing start at $10/month (billed hourly, no contract)

https://elest.io/open-source/lemmy

I would love to get some feedback from the community

  • ComputerSagtNeinEnglish
    7·
    1 year ago

    This seems like the thing I am looking for. I have no experience with servers and stuff though. Could you give me a brief overview what the basic offer would mean in terms of stuff important for lemmy, like how many users can join your instance with that option, how much can they post etc.

    • jbenguira@lemmy.elest.ioOPEnglish
      8·
      1 year ago

      The smallest offer comes with 1vcpu / 2GB ram (+2GB of swap on NVME) / 20GB of disk (NVME), I would say it’s good enough for up to 50 active users. For the storage it’s possible to connect a Network volume to extend the storage up to 10TB.

      Bigger plans have way more ram & cpu allowing you to scale to thousands and tens of thousands of active users.

        • jbenguira@lemmy.elest.ioOPEnglish
          2·
          1 year ago

          Yes! We already have support of ARM64 on Elestio, but not yet for Lemmy because public docker image are not multiarch currently … We are going to publish our own image or Lemmy very soon that will be MultiArch and so can be used on Elestio

          • example@reddthat.comEnglish
            1·
            1 year ago

            although the official images are not multiarch, there are arm64 tags with different names (and published with some delay)

            • jbenguira@lemmy.elest.ioOPEnglish
              1·
              1 year ago

              Yes indeed I noticed that, but I was not super happy with different tags for different arch, that’s not a best practice and complicate deployments

              We decided to go another route and publish our own public image on Docker hub, that way it will be multi arch and also it will be verified by our automated pipeline (Code vulnerabilities, Dependencies, healthcheck, breaking changes). It should be ready soon, and will be similar to this: https://hub.docker.com/r/elestio4test/traduora