Rocket.Chat Self-Managed

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

11 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Rocket.Chat 9.0.0 security and authentication update

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.

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.

Primary source · Reviewed 2026-11-18

What lands where

  1. Supplied by

    Vendor or project

    Docker or Docker Compose, Kubernetes with the official Helm chart, or the Launchpad CLI

  2. Operated by

    Your team

    Customer operates MongoDB, application instances, storage, TLS, monitoring, backups, scaling and upgrades; plan entitlements govern enterprise capabilities.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodDocker or Docker Compose, Kubernetes with the official Helm chart, or the Launchpad CLI
InfrastructureServers / containers
Production paths run persistent application and MongoDB workloads on customer virtual machines or Kubernetes.
Licensing modelOpen Source / Open Core
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.
LicenseMIT Community Edition core; Enterprise Edition code and non-community plans use separate proprietary licensing.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 7 documented · 5 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

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.

Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

Named-cloud installation and paid workspace plans do not establish a qualifying Marketplace purchase or cloud-commitment eligibility.

Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

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.

Self-managed Rocket.Chat 9.0+ identity plan boundary · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

Current self-managed identity guidance documents LDAP/SAML and plan boundaries. A SCIM endpoint, lifecycle operations and entitlement were not established.

Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

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.

Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

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.

Self-managed controls; plan qualifications retained Rocket.Chat self-managed 9.0.0 release; exact component and feature applicability follows the release notes. · Source ↗ · Prior security-controls source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Air-gapped operation
Edition-dependentEvidence and scope for Air-gapped operation

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.

Paid isolated workspace configuration · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Self-managed Kubernetes installation · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

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.

Premium HA sizing table; application replica count and data size require design · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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.

Rocket.Chat Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

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.

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 ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

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.

Rocket.Chat self-managed 9.0 release · Source ↗ · Release lifecycle ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Scope & considerations

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.

Category fit

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

Compare within Collaboration

  • 3CX Self-HostedCommercial business communications and PBX platform installed into the customer's public-cloud account.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Commercial Only
  • Apache AnswerSelf-hosted community questions, answers and knowledge content.
    • AWS
    • DigitalOcean
    • Railway
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • BigBlueButtonSelf-hosted conferencing and virtual classroom platform.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Scaleway
    Customer-operated · Open Source / Open Core
  • BookStack Self-HostedSelf-hosted wiki and documentation organized into books, chapters and pages.
    • AWS
    • DigitalOcean
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • Campfire (ONCE)Self-hosted group chat and team conversation application.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Collabora Online (CODE)Community office editing server for integration with a document platform.
    • AWS
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    Customer-operated · Open Source / Open Core

Showing 8 of 25 other listings in Collaboration. These products address related workflows; read their category-fit notes before comparing scope. See all of Collaboration →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Rocket.Chat in the customer's AWS environment ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

    • Rocket.Chat self-managed deployment on DigitalOcean ↗ · DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory