
# Rocket.Chat Self-Managed

Self-managed team messaging and collaboration platform deployed on customer cloud infrastructure.

Canonical page: https://launchinyourcloud.com/directory/rocket-chat-self-managed/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Rocket.Chat Self-Managed

Self-managed team messaging and collaboration platform deployed on customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/rocket-chat-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Community Edition core; Enterprise Edition code and non-community plans use separate proprietary licensing.
- Licensing model: open-source
- Installation: Docker or Docker Compose, Kubernetes with the official Helm chart, or the Launchpad CLI
- Architecture: Customer-operated Rocket.Chat application and MongoDB deployment on virtual machines or Kubernetes.
- Operations: Customer operates MongoDB, application instances, storage, TLS, monitoring, backups, scaling and upgrades; plan entitlements govern enterprise capabilities.
- Product website: https://www.rocket.chat/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-18; infrastructure review: 2026-11-17

### Scope and qualifications

New self-managed deployments receive the Starter plan, intended for evaluation or small non-critical teams and limited to 50 users. Commercial, Government, Defense and air-gapped capabilities require the applicable plan. Push notifications normally require Rocket.Chat Cloud registration and outbound access unless an alternative gateway is configured. Launchpad excludes Omnichannel and federation workloads and includes a closed-source operator. The documented DigitalOcean Marketplace one-click path is unsupported. Rocket.Chat 9.0.0 moves LDAP, SAML, and Custom OAuth to premium editions and removes several login integrations. It also fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure; verify at least one administrator login path before upgrading.

Community Edition code outside designated Enterprise Edition paths is MIT-licensed. Enterprise Edition code and paid self-managed plans have separate proprietary terms and feature entitlements. Since 9.0.0, LDAP, SAML, and Custom OAuth are premium features; several legacy login integrations were removed. Confirm the purchased plan and an administrator recovery path before upgrade.

Production paths run persistent application and MongoDB workloads on customer virtual machines or Kubernetes.


### Category fit

- collaboration: Team channels, messaging, file sharing and collaborative workflows; governance, scale and isolated-network capabilities depend on plan.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.rocket.chat/partners/aws (checked 2026-11-17). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://rocket.chat/install (checked 2026-11-17). 


### Cloud deployment evidence

- Rocket.Chat in the customer's AWS environment (aws): https://www.rocket.chat/partners/aws
  Rocket.Chat states that the self-managed deployment runs in the customer's own AWS environment and can be launched from AWS Marketplace. The EKS Launchpad guide is a separate current implementation path.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Rocket.Chat self-managed deployment on DigitalOcean (digitalocean): https://rocket.chat/install
  The current publisher installation page explicitly names DigitalOcean for self-managed deployment. The older Marketplace one-click guide is unsupported and is not presented as a supported one-click method.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Self-managed installation options and named clouds: https://rocket.chat/install

- AWS customer-account deployment: https://www.rocket.chat/partners/aws

- Launchpad deployment on Amazon EKS: https://docs.rocket.chat/docs/deploy-with-launchpad

- Kubernetes and Helm deployment: https://docs.rocket.chat/docs/deploy-with-kubernetes

- Deployment guide: https://docs.rocket.chat/docs/deployment-guide

- Community Edition license: https://github.com/RocketChat/Rocket.Chat/blob/develop/LICENSE

- Enterprise Edition license: https://github.com/RocketChat/Rocket.Chat/blob/develop/apps/meteor/ee/LICENSE

- Current self-managed plans: https://docs.rocket.chat/our-plans

- Release support lifecycle: https://docs.rocket.chat/docs/releaselifecycle

- Unsupported DigitalOcean one-click path: https://docs.rocket.chat/docs/deploy-with-digital-ocean

- Rocket.Chat 9.0.0 release notes: https://docs.rocket.chat/docs/rocketchat-release-notes/

### Licensing sources

- https://github.com/RocketChat/Rocket.Chat/blob/develop/LICENSE

- https://github.com/RocketChat/Rocket.Chat/blob/develop/apps/meteor/ee/LICENSE

- https://docs.rocket.chat/our-plans

- https://docs.rocket.chat/docs/rocketchat-release-notes/

### Infrastructure sources

- https://docs.rocket.chat/docs/deployment-guide

- https://docs.rocket.chat/docs/deploy-with-kubernetes


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The installation page names customer AWS/DigitalOcean deployment, but not a current cloud Marketplace procurement offer. The Rocket.Chat app Marketplace is a different catalogue. Scope: Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment. Source: https://rocket.chat/install (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Named-cloud installation and paid workspace plans do not establish a qualifying Marketplace purchase or cloud-commitment eligibility. Scope: Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment. Source: https://rocket.chat/install (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. From Rocket.Chat 9.0, LDAP and SAML are included in Starter and premium plans, and excluded from Community. The reviewed identity FAQ explicitly separates these plans; older Community entitlement assumptions no longer apply. Scope: Self-managed Rocket.Chat 9.0+ identity plan boundary. Source: https://docs.rocket.chat/docs/identity-management-faq (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Current self-managed identity guidance documents LDAP/SAML and plan boundaries. A SCIM endpoint, lifecycle operations and entitlement were not established. Scope: Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment. Source: https://docs.rocket.chat/docs/identity-management-faq (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Rocket.Chat Self-Managed material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.rocket.chat/docs/security-overview (reviewed 2026-11-17).

- Security controls: Documented. The security overview distinguishes plan-specific audit, custom-role and encryption capabilities. FIPS configuration requires a Government/Defense add-on; customers operate TLS, firewall rules and the compatible MongoDB deployment. Current advisory review: Rocket.Chat 9.0.0 fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure while changing authentication feature availability. Upgrade to 9.0.0 or later, verify an administrator login path, and confirm premium authentication entitlements. Scope: Self-managed controls; plan qualifications retained Rocket.Chat self-managed 9.0.0 release; exact component and feature applicability follows the release notes.. Source: https://docs.rocket.chat/docs/rocketchat-release-notes/ (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.rocket.chat/docs/security-overview.

- Air-gapped operation: Edition-dependent. The documented air-gapped model requires a paid plan and alternative handling for cloud-dependent services. Stage licensing/registration and apps through the supported workflow; ordinary mobile push and app Marketplace access require separate arrangements. Scope: Paid isolated workspace configuration. Source: https://docs.rocket.chat/v1/docs/choose-your-deployment-model (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Rocket.Chat documents Helm deployment into customer Kubernetes, with MongoDB and application configuration managed separately. Launchpad is a distinct deployment path with its own feature and operator constraints. Scope: Self-managed Kubernetes installation. Source: https://docs.rocket.chat/docs/deploy-with-kubernetes (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. For HA premium workspaces, the sizing guide lists Rocket.Chat at 4 vCPU/8–12 GiB and MongoDB at 2 vCPU/8–16 GiB per replica, recommending three MongoDB members. It is a workload-specific baseline, not proof that every 100-user workload fits. Scope: Premium HA sizing table; application replica count and data size require design. Source: https://docs.rocket.chat/docs/system-requirements (reviewed 2026-11-17).

- License pricing: Documented. Community Edition code outside designated Enterprise Edition paths is MIT-licensed. Enterprise Edition code and paid self-managed plans have separate proprietary terms and feature entitlements. Scope: Rocket.Chat Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://github.com/RocketChat/Rocket.Chat/blob/develop/LICENSE (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm a premium HA workspace design, application replicas, MongoDB replica sizing, attachment storage and clock-speed requirements. The Starter 50-user plan does not cover the requested 100-user scenario. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://docs.rocket.chat/docs/system-requirements (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Rocket.Chat 9.0.0 was released November 10, 2026. It changes authentication feature entitlements, removes login integrations, and includes access-scoping, SSRF, and Brotli fixes. Scope: Rocket.Chat self-managed 9.0 release. Source: https://docs.rocket.chat/docs/rocketchat-release-notes/ (reviewed 2026-11-18). Supporting source: Release lifecycle — https://docs.rocket.chat/docs/releaselifecycle.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Rocket.Chat 9.0.0 security and authentication update (security-advisory): Rocket.Chat 9.0.0 fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure while changing authentication feature availability. Scope: Rocket.Chat self-managed 9.0.0 release; exact component and feature applicability follows the release notes. Conditions: Exposure depends on messaging, transcript, outbound request, and affected dependency use. Authentication migration depends on edition. Action: Upgrade to 9.0.0 or later, verify an administrator login path, and confirm premium authentication entitlements. Source: https://docs.rocket.chat/docs/rocketchat-release-notes/; reviewed 2026-11-18.



