For small installations I really prefer to have PostgreSQL. Technically I really think it's a downside to be forced to use Mongodb (Meteor requires Mongo).
#ROCKET.CHAT VS SLACK FULL#
Now, I don't have anything against Meteor and I really think a Slack-clone is exactly the kind of use case where you could use Meteor to its full potential. It's feature set also rivals Slack, it's good looking enough.
#ROCKET.CHAT VS SLACK CODE#
I could pay Slack already if I didn't care, so I would not just pay an alternative and not have full-control (including the ability to tweak and improve the entire code base).
I really want to have full-control, not just make it cheaper. It's still at least 3 times cheaper than Slack, so it may be a good option for you. If you want permission control for that you must use their "Enterprise" offering and pay USD 20/year per user. You can create both public channels or private groups, but anyone can delete a private group. Unfortunatelly, it has an important show-stopper for my needs. It uses MySQL or PostgreSQL which I like. So it's both lightweight, very fast, and not so difficult to contribute. It has a very similar feature set to Slack and most importantly, it's written in Go. I tried MatterMost first and I really wanted to like it. With the cost reasoning out of the way, then it's a matter of choosing which alternative to use. Any other scenario and we have to analyze it differently. There are also many other alternatives that you may want to try.įor the sake of this article, let's assume you're a small to medium company, in need of private rooms, many external users (for example, your clients), with at least 50 people.
For example, if you're an open source community, you would try Gitter instead. For most companies, the conversation history is not so important and even the free-tier will be more than enough.Ĭost is less relevant depending on your context, and there are many different uses for group chats. That's 12 times cheaper.Īgain, you shouldn't do it just for the cost savings as the maintenance burden can easily not be worth it if you or your team are not devops savvy and you don't have anyone to keep monitoring it.
#ROCKET.CHAT VS SLACK PLUS#
You avoid paying around USD 12,000 a year or more, and instead you will pay USD 960 a year in Digital Ocean boxes and MMS plus a few hours every month in basic maintenance. What I will argue is that if you have 150 people or more, and you're still growing, it's not such a big burden to jump into your own infrastructure. Of course, it costs some work and maintenance, so it's not for everybody. If you're a medium to big company it really starts to make sense to want to have more control over your own property.
If you're from outside of the US coastal cities, specially from countries in South America, Asia where currency can be more than 3 times devalued, than it quickly starts to become a big deal.Īpart from that, we are currently offloading a whole lot of out IPs and knowledge into the care of companies we don't really know and where we don't hold any real stakes. On my GitLab cost calculations, some people argued that saving USD 15k yearly is not such a big deal, and they're not wrong.
If you have more than 20 people then it starts to become a conundrum. If you're a small team (around a dozen people) it's well worth it and you should definitely pay and get over with. But then you have to commit to pay USD 8/month per user (USD 6.67 if you pay ahead of time).
0 kommentar(er)
