// the find
RocketChat/Rocket.Chat
The Secure CommsOS™ for mission-critical operations
Rocket.Chat is a self-hosted team messaging platform — essentially an open-source Slack alternative built on Meteor.js with TypeScript. It targets organizations that need to keep communications on their own infrastructure, particularly in regulated industries like defense and government.
The Apps-Engine framework is genuinely useful — you get a sandboxed plugin system with well-defined bridges for rooms, messages, users, and HTTP, so third-party apps can't escape their lane. The monorepo structure with changesets shows disciplined release management for a project this size. E2E encryption, RBAC, federation, and air-gapped deployment support are real features with real architecture behind them, not checkbox items. The REST API surface is extensive and versioned (v1 namespace with proper middleware chain for auth, CORS, metrics, tracing).
Still running on Meteor.js in 2026 is a significant liability — Meteor's reactivity model and oplog tailing are the reason real-time works, but it's also why the build system is slow, the deployment story is awkward, and hiring is hard. The codebase mixes JavaScript and TypeScript throughout (see the converters directory), and some core files are still .js. Operationally, running this yourself is non-trivial: you need MongoDB, Meteor, and ideally multiple instances behind a load balancer before you even get to HA. Documentation is thorough but scattered across four separate sites.