Answers: <p>TBH,</p>
  <p>I would question the reason for it to be on-premise, since nowadays the trend is to look for SaaS solutions (so, nothing to maintain from an IT / Ops point of view).</p>
  <p>Slack has a free plan as long as your team is not concerned about message retention or multi-calls/video.</p>
  <p>I don't see the reason to have yet another piece of software to be installed/configured/maintained/patched/secured etc
  when there are so many players out there which lift all of this out (for a price, of course), so if this is a case of &quot;<em>my boss doesn't want it to be on the cloud/not under his control</em>&quot; or b***shit like that, I would question the real need for it to be on-prem.</p>
  <p>Even the old Skype4Business (therefore, Microsoft) dropped its on-prem installation in favour of Teams through Office365...</p>
  <p>Again, my thought.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-09-17T05:13:53.950Z
Answers: Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-ask).
Answers: Community
Answers: CC BY-SA 4.0
Answers: 2021-09-16T11:35:45.143Z
Answers: 2021-09-16T11:35:45.143Z
Answers: Lorenz_DR
Body: <p>I started my graduation internship two weeks ago. My assignment is to look for a Slack alternative that'll be able to deploy on-premise. A lot of things need to be automated. I already did some research and found some interesting platforms like Mattermost, Zulip, Rocket.chat.</p>
  <p>I was wondering if someone has any recommendations that really worth diving into? Also would like your extensive arguments about topics like user interface, integrations/webhooks/bots, security, scalability and so on.</p>
  
Comments: CC BY-SA 4.0
Comments: 2021-09-12T18:09:41.077Z
Comments: Bij het deployen en implementeren komen er DevOps zaken bij kijken.. Dus het lijkt me niet heel ver weg van DevOps. Heb je een suggestie voor een andere community? @Pierre.Vriens
Comments: Lucas Scheepers
Tags: <devsecops><slack>
Title: Collaboration tools recommendations like Slack
UserDisplayName: Lucas Scheepers
ThreadText: # Collaboration tools recommendations like Slack
  
  (Asked by: username_0 on 2021-09-12)
  
  I started my graduation internship two weeks ago. My assignment is to look for a Slack alternative that'll be able to deploy on-premise. A lot of things need to be automated. I already did some research and found some interesting platforms like Mattermost, Zulip, Rocket.chat.
  
  I was wondering if someone has any recommendations that really worth diving into? Also would like your extensive arguments about topics like user interface, integrations/webhooks/bots, security, scalability and so on.
  
  **Tags:** devsecops, slack
  
  > **Comments:**
  > **username_0**: Bij het deployen en implementeren komen er DevOps zaken bij kijken.. Dus het lijkt me niet heel ver weg van DevOps. Heb je een suggestie voor een andere community? @Pierre.Vriens  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-09-16. Score: 1
  
  TBH,
  
  I would question the reason for it to be on-premise, since nowadays the trend is to look for SaaS solutions (so, nothing to maintain from an IT / Ops point of view).
  
  Slack has a free plan as long as your team is not concerned about message retention or multi-calls/video.
  
  I don't see the reason to have yet another piece of software to be installed/configured/maintained/patched/secured etc
  when there are so many players out there which lift all of this out (for a price, of course), so if this is a case of "*my boss doesn't want it to be on the cloud/not under his control*" or b\*\*\*shit like that, I would question the real need for it to be on-prem.
  
  Even the old Skype4Business (therefore, Microsoft) dropped its on-prem installation in favour of Teams through Office365...
  
  Again, my thought.
  
  > **Comments:**
  > **username_2**: Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-ask).  
  
  ---
  
  