Internal communication & Infrastructure

Self-hosted internal communication with Rocket.Chat replacing Slack

Rocket.Chat deployed on the client server to replace Slack with an open-source solution and minimal recurring cost.

Back to projectsContact

Solution flow

  1. Internal users
  2. Cloudflare Tunnel
  3. Rocket.Chat in Docker
  4. Client server
  5. Backup routine

Internal users, followed by Cloudflare Tunnel, followed by Rocket.Chat in Docker, followed by Client server, followed by Backup routine

Context

The accounting office used Slack for internal communication, but recurring costs increased without additional features that justified dependence on a paid platform.

Problem

Internal communication costs needed to be reduced without losing channels, users, team organization and important operational files.

What I delivered

  • Deployed Rocket.Chat in a Docker container on the client server
  • Published it securely through Cloudflare Tunnel without direct port exposure
  • Recreated the functional channel, user and team structure used in Slack
  • Organized permissions and usage routines to preserve internal operations
  • Configured backups for environment files and conversations

Outcomes

  • Significantly reduced recurring internal communication costs with an open-source solution.
  • Channels, users and team organization were maintained to avoid operational disruption.
  • Files and conversations gained a dedicated backup strategy.
  • Internal communication no longer depends exclusively on an external paid platform.