I gotta say I love getting some good feedback on yesterday’s post about my new gig via comments and tweets. The well wishes were, well, great, but what I really valued immensely were the suggestions people made in my response to me discussion on collaboration systems.

Internet, “you complete me” (and “you had me in 1987 at hello world”).

My first day was spent somewhat taking on a request that I recommend an online collaboration space/system for the project. It will be for a geographically dispersed group, likely technically adept but not technology developers, to offer a place for discussions, sharing documents/links/media, maybe some project management, likely integrating with other services, and also, have some portion that is public.

As mentioned, because of my experience using it for several projects this year, is Slack (though it lacks the public part, it is proprietary, and there is the 10,000 message limit on searching).

I found 8740 results in a google search for “alternatives to slack”. Looking at AlternativeTo I cannot even see the bottom of the list


I do like the ways I can filter the results on this site, by pay model, platform, etc. And I can vote (sorry Asana, I accidentally clicked a “no” to recommend and I cannot find a way to un-vote that, gulp). It’s somewhat of a mixed bag, given the Skype is at the top, between some being communication tools and others being communication and document management tools and others being collaboration tools.

I started looking at the ones that were hosted but had free options, and tried to see how crippled the free is. It seems like they all offer the free hooks but want you to Premium-ize to some paid plan. Or Pay mega bucks for a self hosted version.

I found a few from Ten Alternatives for Slack (Beebom). In a quick look (meaning scanning yhe features, I find the demo videos pretty much pretty graphics ads). I saw promise in:

With hosted you will have to hope for reliable uptime, that you have not missed a critical limit on free, and the possibility that the service will even be available for the duration of your project.

For looking at open source options, which might be the preference for Creative Commons, I sifted through 4 Open Source Alternatives to Slack (Opensource.com) and another list from VentureBeat.

The ones from my first scans that caught my eye included:

  • Rocket.Chat (plus they have a live demo site, and I could play with one on the OET Sandstorm server)
  • Mattermost – billed as “slack compatible” (someone who has used it told me by email that it was a bit “immature” beyond the chat features)

Pretty much they look similar… to Slack.


I grossly generalize. They differ in terms of integrations and limits/use of media and synchronous tools.

Now I might look at Wrike. Bloomfire. Glip. Discord. Filevine. Let’s Chat. Tricube. qiscus. Kune. Flock.co. Hubgets. Kandan. Gitter. Fleep. Sameroom. Campfire. ChatGrape. Jostle. Slenko. Flow Grape. Zulip. Crux. Scudcloud. Bitrix24. Asana. Jacondo.

This, welcome to Paradox. To really compare them, even a demo session won’t cut it. I won’t really know without putting it to use in a real situation, with real people. The time it would take to do this? And so I have to thus make some hunch guesses based on limited skim by, reviews, and what people I might know who have more experience.

And while I understand why people want to know when they ask, and despite the endless flow of listicles that people publish, there can never be a simple answer to “What is the best tool for X?” There are a lot of importance differences between X for me and X for you.

Thus, the answer then often comes from the now cliché, somewhat of an industry for Chase Jarvis, but at it’s heart true for photography:

Dribble image by Sean McCabe

Dribble image by Sean McCabe

I am writing nothing revelatory here. This is just recognizing that we have a frame of experience of what we know, that we mix in what we can summarize from web searches and recommendations by people we trust/respect. At some point, the hunch kicks in, we pick one, plunge/commit. Then we find out what we guessed wrong, or the unexpected limit, we find work arounds, or have to adjust our own processes. Sometimes we have to painfully accept that we guessed wrong, and might have to do a complete rewind.

It’s not just a feature set of a tool, it’s mixed in with our own experiences, the needs/interests/aptitudes of others we hope to use the system, and a quasi large amount of situations we can never anticipate. That’s a lot of delta in the equation. The more we can flex with this uncertainty, and find the end arounds, the better we might be in the long run. We are the most important thing in the feature list of tools.

And in some sense I have to spread some wonder about how much effort is spent building more or less tens, hundreds of platforms that are more or less the same functionality, many of which will not be around a year or two from now– why are there so many alternatives to Slack? Might it be there is something to Slack? I am not saying this is reason to go with it, but as a platform that has surged to the front of the pack, all the ones trying to catch up are likely not quite as mature. But it’s hard know that from their Every Bootstrap Website Ever site.

Or am I wrong?

And then you will face the open purists. They spend inordinate amounts of time, energy patching their BananaFizz Linux OS, or trying to figure out what is cumbersome in GIMP that is fluid in Photoshop. I do not question the Open Purists and their IRC channels, I can respect the lines they stand behind. But I would rather be getting stuff done than figuring our end-arounds.

Now lest you think I am building a sand castle case to select a proprietary platform, think again. I’m just trying to work this out. I was pretty keen with the functionality I saw in Rocket Chat, and if I can make use of an open tool without too much fuss, I will lean that way.

Are there absolute Best Tools?

I have not made any decisions at all. Just talking out loud.

And I see no road sign that says “You Are Now Leaving Paradox.”

Top / Featured Image: This one was easy; I knew I had my own photo of the sign for a small town in upstate New York that I drove through in 2012. Yes, it is a real place. It’s also a lake nearby.

The photo is mine on flickr https://flickr.com/photos/cogdog/8077130869 shared under a Creative Commons (BY) license… with my clever title “Just Having a Town Sign is Paradoxical”

Profile Picture for Alan Levine aka CogDog
An early 90s builder of the web and blogging Alan Levine barks at CogDogBlog.com on web storytelling (#ds106 #4life), photography, bending WordPress, and serendipity in the infinite internet river. He thinks it's weird to write about himself in the third person.


  1. Nice post Alan. Always enjoy your open ramblings. I had a similar such moment recently in regards to the growing use of Facebook by schools in my area (http://readwriterespond.com/?p=1710). Cameron Hocking wrote an interesting post which I referenced in regards to some questions to consider.

  2. THIS: “We are the most important thing in the feature list of tools.” Just because a tool is the bees knees for me doesn’t mean it will work for you. Knowing how you think, what tools you like and how you work (or your customers if that is the goal) goes a long way to making the tool right for you.

  3. You are right, there are many such tools on the market, some of them looking almost the same, while others are completely different. And although many of the features are similar, each of these tools follows a certain communication and collaboration flow. Considering that what is right for your team might not be OK in someone else’s work scenario, here comes the decision making process. Which, as you said, can take a lot of time and much energy.

    I’m not a fan of the x-ways-to-choose-the-best-tool lists because they generalize something that should be strictly customized. However, I strongly believe that when choosing such a tool (and any tool for that matter), it is highly important to check if its approach towards the problem you want solved (in this case, communication and collaboration) is right for your workflows. Cause you shouldn’t have to change your workflows completely just to use a tool.

    In the *others* list you mentioned the tool I’m using, Hubgets. It doesn’t look anything like Slack and it has a different approach to communication altogether. Our team loves it, but that doesn’t necessarily mean it would be good for you too :)

Leave a Reply

Your email address will not be published. Required fields are marked *