← Templates · Applications
RO
Rocket.Chat
Verified2 services
Rocket.Chat, the open-source team chat platform — a self-hosted alternative to Slack with its own dedicated MongoDB replica set.
| Runs | 2 services |
|---|---|
| Stack | rocket-chatrocket-chat-mongo |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Yes, deployed end to end by the Railyard team |
Why deploy on Railyard
Railyard provisions all 2 services in this stack together — rocket-chat, rocket-chat-mongo — wired to reach each other over the private network, on a server you already pay for.
Deploying Rocket.Chat is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- A self-hosted Slack alternative for a team or community
- Chat with full data ownership, including on-prem compliance requirements Slack can't meet
Good to know
- MongoDB is started as a single-node replica set because Rocket.Chat requires change streams for real-time updates — this isn't optional and can't be satisfied by a shared, non-replica-set Mongo addon
- This deploys the classic monolith, not Rocket.Chat's microservices split — fine for most team sizes, see Rocket.Chat's own docs if you need to scale past that
- Create the first admin account from the setup wizard on your first visit
- mongodb-community-server's own docker-entrypoint.py drops privileges via a subprocess exec that needs new-privileges — the default no-new-privileges hardening makes it fail every boot (mongod --fork: 'child process failed, exited with 1'); disable_no_new_privileges is required, same class of issue as Castopod's and Jitsi's