RocketChat/Rocket.Chat

Prefer upstream unless you explicitly need this older 2020 snapshot. This fork looks unsuitable for adopters who want a current, maintained Rocket.Chat; it is only attractive for legacy compatibility or historical experimentation.

Prefer this fork only if you explicitly want the older, stripped-down Chat-Locker behavior and can live without upstream Rocket.Chat's modern platform features. For most adopters, upstream is the safer choice because this fork is stale, highly divergent, and has clearly removed several major workflows.

Prefer upstream unless you specifically need a frozen 2025 snapshot and are willing to own maintenance. This fork shows no added functionality, but it is far behind upstream, so adopters should expect missing fixes and features rather than unique value.

Choose this fork only if you need its specific legacy/API behavior and are prepared to maintain a large upstream gap. If you want current Rocket.Chat features, fixes, and lower maintenance risk, upstream is the better default.

Choose this fork only if you intentionally want an older, mostly unchanged Rocket.Chat base and are prepared to do substantial catch-up work. For most adopters, upstream is the better choice because this fork shows no added functionality and is materially behind.

Adopt this fork only if you specifically want a legacy, simplified Rocket.Chat derivative and are prepared to maintain it yourself. For most adopters, upstream Rocket.Chat is the far better choice because this fork is stale, heavily diverged, and likely missing most modern capabilities.

Choose this fork only if you specifically want a conservative downstream baseline and are willing to own merge debt; otherwise upstream looks like the better default because it is much newer and still actively moving.

Prefer this fork only if its livechat and data-protection tweaks are the point; otherwise upstream is the safer choice because this fork is far behind and likely missing many recent fixes and polish.

Prefer this fork only if you need its specific data-protection and E2EE-oriented customizations and can absorb heavy upstream lag. For most users, upstream Rocket.Chat is the safer choice because this fork is far behind and unlikely to include current fixes or features.