Hello Rocket.Chat Community,
I’m writing this post out of frustration and disappointment, and I hope it starts a constructive conversation about Rocket.Chat’s licensing model and its consequences — especially in regions experiencing crisis.
Our organization has been using Rocket.Chat Community Edition for over four years as our primary internal communication tool. It has always been important for us to have control over our infrastructure, particularly in a country like Iran where access to global platforms like WhatsApp and Telegram can be unstable or blocked.
Recently, after war broke out between Iran and Israel, our government shut down access to the global internet, isolating the country from the outside world. As expected, all major communication platforms became inaccessible. But what we didn’t expect was that Rocket.Chat itself would also stop working.
Our self-hosted server, running the Community Edition, went into read-only mode and displayed this message:
“Workspace in read-only mode. Admins can restore full functionality by connecting it to the internet or upgrading to a premium plan.”
At a time when every communication channel in the country was cut off by the regime, and we were relying on Rocket.Chat as our only functional internal platform, we were suddenly locked out — not by censorship or a technical failure, but by the software we trusted to remain under our control.
We contacted Rocket.Chat support and explained the situation but the support team declined our request for a temporary license grace period, citing sanctions.
This experience raises a serious concern: how can software that claims to be open-source and self-hostable fail in exactly the kind of situation where self-hosting is supposed to matter most?
This wasn’t just a technical limitation — it was a direct disruption to our ability to communicate during a national emergency. If you promote open-source tools for secure, self-hosted communication, they must actually function independently of centralized infrastructure, especially in crisis scenarios.
I hope this post encourages the Rocket.Chat team to reconsider the current approach to license enforcement in the Community Edition, and to ensure that critical communication software doesn’t fail the people who rely on it most — especially when they have no alternatives left.
P.S.
Things still haven’t returned to normal. We’re still struggling every day just to keep our Rocket.Chat server online and functional
Thank you.
A frustrated, sanction-locked Middle Eastern sysadmin