Gitter vs Mattermost: What are the differences?
Gitter: Messaging for people who make software. Integrated with your team, projects and your code. Free chat rooms for your public repositories A bit like IRC only smarter. Chats for private repositories as well as organisations.; Mattermost: Open-source, self-hosted, Slack alternative. Mattermost is modern communication from behind your firewall.
Gitter and Mattermost can be categorized as "Group Chat & Notifications" tools.
Some of the features offered by Gitter are:
- Know who's seen any message
- Edit messages after you've sent them
- Full emoji support
On the other hand, Mattermost provides the following key features:
- All your team communication in one place, searchable and accessible anywhere
- Slack-compatible, not Slack-limited. Imports Slack channels, users and themes. Offers Slack-compatible webhooks and integrations including Hubot, Jenkins, GitLab and others
- Self-host ready with System Console and IT admin tools for managing dozens of team sites. Installs with Linux binary, plus Docker, Heroku, AWS, Azure and Cloud Foundry options
"Github integration" is the primary reason why developers consider Gitter over the competitors, whereas "Open source" was stated as the key factor in picking Mattermost.
Mattermost is an open source tool with 14.9K GitHub stars and 3.04K GitHub forks. Here's a link to Mattermost's open source repository on GitHub.
According to the StackShare community, Gitter has a broader approval, being mentioned in 25 company stacks & 41 developers stacks; compared to Mattermost, which is listed in 38 company stacks and 24 developer stacks.
What is Gitter?
What is Mattermost?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Gitter?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I use Zulip instead of Slack, Mattermost, or RocketChat because of its first class threading. One week after switching to Gmail (in 2004) I realized I was never (willingly) going to use an unthreaded email product again. I had that same experience the first time I saw Zulip.
Zulip is also fully open-source, with a well-maintained (e.g. 90+% test coverage, fully static python), easily extensible code-base. In many companies, your communication platform (chat or email) is the center of the workplace -- no one asks for a chat integration into their calendar, they ask for a calendar integration into their chat. A fully open-source codebase means you can customize Zulip to your needs, and are never at the whim of a corporate maintainer who can't or won't fix simple bugs, or who will charge you tens of thousands of dollars for making minor customizations.
Slack is the industry standard for managed instant messaging (IM). A good alternative would be to self (or cloud) host an open source IM such as Mattermost but as always it would be a good idea to do a cost benefit analysis between the solutions.
Some of the main things to consider:
- Having a good SDK for plugin creation
- Having good integrations with existing tools ( JIRA , GitHub , OpsGenie , etc.)
- Maintenance and administration
- Covers all your businesses use cases
I use Slack because it offers the best experience, even on the free tier (which we're still using). As a comparison, I have had in depth experience with HipChat, Stride, Skype, Google Chat (the new service), Google Hangouts (the old service). For self hosted, Mattermost is open source and claims to support most Slack integrations, but I have not extensively investigated this claim.
We run a major community project named as @Donut which is an #OpenSource social platform which allows communities to set up their own social environment and @slack platform drives us through the best experience of community interaction. Though we have been using some Open Source Interacting platforms like Gitter and Zulip but the fact that Slack exists and is such an essential tool, it’s really helped us with scaling and still feeling connected to one another across remote places with various teams with appropriate features in it.
The #User-Friendly Slack brings all the organised conversations at one place giving a prospectus to feel the better user experience on desktop.
Followings its pros:
- Allow creating of various channels which can be best suited to organised #projects, #teams and #events.
- Allow multiple tools and integrations such as Google Drive and GitHub
- Video Conferencing addition helps teams to organise meetings.
- No limit for addition of users and its free.
- Allow threads to keep side conversations from derailing the topic or project at hand.
The most crucial thing it supports the best security and protection with 2 factors authentication.
From a StackShare Community member: “We’re about to start a chat group for our open source project (over 5K stars on GitHub) so we can let our community collaborate more closely. The obvious choice would be Slack (k8s and a ton of major projects use it), but we’ve seen Gitter (webpack uses it) for a lot of open source projects, Discord (Vue.js moved to them), and as of late I’m seeing Spectrum more and more often. Does anyone have experience with these or other alternatives? Is it even worth assessing all these options, or should we just go with Slack? Some things that are important to us: free, all the regular integrations (GitHub, Heroku, etc), mobile & desktop apps, and open source is of course a plus."
It is no secret that we use Mattermost at Faelix — after all, it is a product we already support to be able to offer it to our customers. And like many network operators we use Oxidized to track and log changes to our routers and switches, even when those changes are made by automation tools.
As part of our move to using more ChatOps within the business I wanted to get visibility of network changes within our network operations channel in Mattermost. A quick and dirty script achieved this.
We haven't found a better way to communicate directly with the core contributors and developers for many open source projects we utilize on GitHub (Scala, Scala-js, Sinatra, Apache top-level projects, just to name a few).
It is a solid piece of software that appeals to us who have used Slack in the past, and the tight integration with a single GitHub repository or organization for each Gitter room just makes sense in our eyes.
Many GitHub communities are on Gitter. It's a great place to ask and answer questions related to open-source frameworks and libraries.
Using Gitter for open source talks and directly communicating with contributors.