Exactly.
We're looking at paying for Slack and mattermost seems to offer most of what Slack does and is something that would be pretty easy to run. It's slick. Well documented and installs nicely in a container.
Has anyone here used Mattermost?
We're looking at paying for Slack and mattermost seems to offer most of what Slack does and is something that would be pretty easy to run. It's slick. Well documented and installs nicely in a container.
Has anyone here used Mattermost?
We only have/had a short eval phase and our use case is a small raceengineering team with 40 people at the racetrack, independent of internet access. So a very particualar use case, and our needs might not cover you needs.
Zulip pro
* Threading model (can't value that high enough)
* All messages overview, no matter what stream they were written in
* Zulip community at chat.zulip.org with direct contact to the devs. Tim Abbott the lead dev helped me out in a issue with a user login (haven't used the Mattermost support so can't compare)
Zulip con
* Most ops work has to be done by a python script manage.py, API has room to improve
Mattermost pro
* API
* haven't measured but the UI felt smoother, faster
Mattermost con
* you have to pay for Enterprise features
Both have great docs and a docker deployment
Our use case is basic chat features with some integrations for a team of around 40.
We run it in a t2.small instance along with another tool. I only had to manually restart it once, which is fine by me.
A postgres backend and S3 storage is most welcome and makes it very simple to manage.
My only complaint would be that the config file is not included in the postgres database so you need a separate routine for its backup. (If anyone from Mattermost reads this, please just include it in the database)
It could also handle importing multiple emojis for us Hipchat castaways.
Both mattermost and zulip look well worth it for saving quite a bit of money over slack for a fair sized company though.
The responses from people here are really interesting.