# Self-hosted mail server and control version instance **URL:** \ **Category:** Technology\ **Tags:** software\ **Created:** [9 October 2023 11:24 UTC](https://community.coops.tech/t/self-hosted-mail-server-and-control-version-instance/3700 "2023-10-09T11:24:30Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Pau](https://community.coops.tech/user_avatar/community.coops.tech/pau/32/486_2.png) [@Pau](https://community.coops.tech/u/Pau)\ **Post date:** [9 October 2023 11:24 UTC](https://community.coops.tech/t/self-hosted-mail-server-and-control-version-instance/3700/1 "2023-10-09T11:24:30Z")
Hi, I am looking for use cases of organisations that host their own mail server. I am collaborating with an organisation of ~30 members. The mail plans that hosting providers offer are just enough for them for now (50GB, although they offer extra storage if needed) and they would like to explore the option of hosting their own mail server on their VPS. Cost can be a reason for moving to a self-hosted option, but what they save in hosting costs can be less than what they need to spend in technical work for setting it up and maintaining it. This organisation works with marginalised communities, but data privacy is just a medium concern for them, specially when emails are sent to and from mail servers that are oriented to privacy in different levels. The information I could gather from the people around me is that it is difficult to set it up in a way that the messages sent from it are not detected as spam by other mail servers. I haven’t found many resources about self-hosting mail servers at a professional level and I would appreciate if someone can refer me to information about when it makes sense to go for the self-hosted option and how to set it up properly for making it reliable. In addition to this, they would also like to explore the option of hosting their own control version instance. They have 4-5 repositories that they want to publish in order to make the projects collaborative, so having their own instance can hinder the visibility of the project and may not be the right solution for such a small number of repositories. Any thoughts and experiences are welcome. Thanks! ---
**Author:** ![chris](https://community.coops.tech/user_avatar/community.coops.tech/chris/32/2_2.png) [@chris](https://community.coops.tech/u/chris)\ **Post date:** [9 October 2023 11:55 UTC](https://community.coops.tech/t/self-hosted-mail-server-and-control-version-instance/3700/2 "2023-10-09T11:55:00Z")
I’d suggest using Mailcow for email: > **[mailcow: dockerized - Blog](https://mailcow.email/)** > > The mailserver suite with the 'moo' – 🐮 + 🐋 = 💕 | Official Blog Page Webarchitects hosts several Mailcow servers for clients, it needs at least 6GB of RAM in my experience, we have hosted it on VPSs with 3GB but it ends up swapping all the time. Given the number of SCM repos you have Gitea probably makes sense: > **[Lightweight DevOps Platform](https://about.gitea.com/)** > > Gitea is a lightweight DevOps platform. It brings teams and developers high-efficiency but easy operations from planning to production. Rather than [GitLab CE](https://about.gitlab.com/install/?version=ce) as it is quite resource hungry, but personally I like GitLab, we have an instance at `git.coop` for Webarchitects Co-operative members: > **[Sign in · GitLab](https://git.coop/users/sign_in)** > > Git hosting for Co-operators ---
**Author:** ![equalmatt](https://community.coops.tech/user_avatar/community.coops.tech/equalmatt/32/2671_2.png) [@equalmatt](https://community.coops.tech/u/equalmatt)\ **Post date:** [13 October 2023 09:03 UTC](https://community.coops.tech/t/self-hosted-mail-server-and-control-version-instance/3700/3 "2023-10-13T09:03:22Z")
> [@Pau](#): > > if someone can refer me to information about when it makes sense to go for the self-hosted option 99% of the time, it doesn’t! If I was making this decision, I’d need to have overwhelming requirements for control over our data to sway the decision. So overwhelming that there are no providers that will enter into a sufficient SLA with us to cover what we want. If the organisation doesn’t already have the experience to make this call, then they’ll end up spending more on consulting fees for someone to maintain their new mail service over time than they’ll save. All this on top of battling against spam filters. That said, there are plenty of other options depending on what they need email for. For example, if they just want some arbitrary email addresses that forward to a group of people, they could use [Cloudflare Email Routing](https://www.cloudflare.com/developer-platform/email-routing/) for free. ( Also hi Pau! 👋 )