Today in ransomware, Slack increases pricing by $195k with a week's notice for a non-profit that teaches teenagers how to code.

@kepano

Are there more cases like this with #Slack? We have a 25k€/year plan and non-profit status and if this is systematic then I would initiate a #Mattermost installation _now_.

On a side note: Are self-hosted Mattermost instances free of license charges or do they still cost money?

@knud @kepano Wouldn‘t just a single known case justify to at least have a proven plan for immediate migration to Mattermost on standby? It’s an obvious risk, do you mitigate or do you accept it?

@chris @kepano

I've been toying with the idea for a long time, but, as usual, the lock-in effect is quite substantial. We built a lot of workflows in Slack and have actual experts.

If Mattermost were free as a self-hosted instance, we would probably switch, but that I still think is not the case. Then we'd have an incentive to spend the time to transition.

Here, this might be contract change from "old" non-profit to a 20% rate. Which we already pay. So I'd like more statistics.

@knud @chris @kepano
What do you mean "if Mattermost were free as self-hosted instance"?
Mattermost *IS* opensource, and can be self-hosted.

Mattermost is an open-source, self-hostable online chat service with file sharing, search, and third party application integrations.
https://en.wikipedia.org/wiki/Mattermost

Mattermost - Wikipedia

@joosteto @chris @kepano

Yes, but as soon as we need single sign-on capabilities this doesn't work with the "free" (Team) version but requires a Pro subscription - even if self-hosted. For 1000 active users this would be again several 10k€ per year.

"Non-profit" status would not apply since we're a science collaboration and not a registered non-profit.

@knud @chris @kepano
Ah, didn't know that, guess I never used the single-sign-on capability of mattermost. Just used the app/program, login once and stay logged in (that's also a single sign on, isn't it?).

@joosteto @chris @kepano

Sort of - we need to manage 1000-2000 members and so far linked Slack invites to an external identity system that serves a number of our tools. To do that manually for these many people would be gruesome (and cost person-power).