Flowdock vs Mattermost: What are the differences?
Developers describe Flowdock as "Flowdock is your team's chat with a shared inbox. Teams using Flowdock react in seconds and never forget anything". Flowdock is a web-based team chat service that integrates with your tools to provide a window into your team's activities. With the team inbox, everyone on your team can stay up to date. Stay connected with Flowdock's iOS and Android apps. On the other hand, Mattermost is detailed as "Open-source, self-hosted, Slack alternative". Mattermost is modern communication from behind your firewall.
Flowdock and Mattermost can be categorized as "Group Chat & Notifications" tools.
Some of the features offered by Flowdock are:
- Team Inbox
- Group Chat
- 1-On-1 Private Chat
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
"Threaded chat" is the primary reason why developers consider Flowdock over the competitors, whereas "Open source" was stated as the key factor in picking Mattermost.
Mattermost is an open source tool with 15.4K GitHub stars and 3.14K GitHub forks. Here's a link to Mattermost's open source repository on GitHub.
Uber Technologies, DuckDuckGo, and Kanteron Systems are some of the popular companies that use Mattermost, whereas Flowdock is used by Teespring, Verba, and TED. Mattermost has a broader approval, being mentioned in 38 company stacks & 24 developers stacks; compared to Flowdock, which is listed in 37 company stacks and 5 developer stacks.
What is Flowdock?
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 Flowdock?
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 have been using flowdock for about two years. We brainstorm in there and store important links and notes. We've integrated github, trello, twitter, several rss feeds and have all of our support emails go straight into our flow.
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.