Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Rocket.Chat Technologies Corp. · www.rocket.chat

Compare with Mattermost → Report an error on this page Is this your product? →

Link to this page

Rocket.Chat: AI-assisted analysis on whats-best.ai Rocket.Chat: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Rocket.Chat at a glance

Vendor
Rocket.Chat Technologies Corp.
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates Rocket.Chat 3/5, the mean of 6 judges. Rocket.Chat is a business instant messaging platform that scores highest on deployment control, at 9, and encryption and access, at 8 to 9, and lowest on sovereignty, 2 to 4, and pricing transparency, 1 to 2. how scores are made
As of
Vendor pages captured 31 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Rocket.Chat alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Platform Engineer

Weighted verdict

Would rather run it than rent it, and wants to know whether that is a supported deployment or a hobby build. Cares about open protocols, federation, a plugin system with real permissions, and an upgrade path that does not orphan the customisations.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Platform Engineer

Panel median The Platform Engineer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Platform Engineer
Channels, threads & search 3.5 of 5 3 of 5
Encryption & access control 4 of 5 4 of 5
Retention, discovery & co-determination 3 of 5 3.5 of 5
Deployment & data custody 4.5 of 5 4.5 of 5
Integrations & extensibility 3.5 of 5 3.5 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 1 of 5 1 of 5

Channels, threads & search

How this is scored

The daily surface: channel model, threading, mentions, files, and whether search can find a decision made eighteen months ago.

0 — Not a team chat: no persistent channels or group conversations, only notifications or one-off messages.

3 — Group chats or channels and direct messages, file sharing, and search over messages.

5 — Public and private channels, threaded replies, mentions and reactions, file sharing with previews, and search across message history.

8 — Cross-organisation or guest channels with clear boundaries, message editing history, pinned and saved items, search with filters by channel, person and date, and unlimited history or a documented history limit per plan.

10 — The archive is a working knowledge base: search that ranks well across years, threads that stay readable, channel lifecycle management (archive, rename, merge) without losing history, and export of a conversation in a form a human can read.

Report an error

The Platform Engineer

Channels come in public, private, password-protected, encrypted, broadcast and read-only flavours with per-channel settings, threads are enabled by default with follow/unfollow, panel filters and search inside threads, and history is unlimited by default because messages are never deleted unless a policy says so. Search is documented as covering public channels and threads, though encrypted rooms are excluded from results, and we found no public information on message edit history or on filtering search by person and date. 4 5 2 7

Report an error

Encryption & access control

How this is scored

What is encrypted and against whom, plus who can reach which room. Judged on documented mechanism, since "encrypted" in this category usually means the vendor holds the keys.

0 — The vendor states that messages are transmitted or stored unencrypted.

3 — Encryption in transit stated, with admin and member roles.

5 — Encryption in transit and at rest stated, admin roles and private channels, guest accounts limited to the channels they are invited to, and SSO or two-factor authentication.

8 — Optional end-to-end encryption for direct messages or private rooms with the trade-offs named, or customer-managed encryption keys; device or session management an admin can revoke, granular permissions per channel, and documented key handling.

10 — End-to-end encryption as a first-class mode — documented or open cryptography, cross-device key management that ordinary users survive, identity verification, and the vendor stating plainly what it cannot decrypt.

Report an error

The Platform Engineer

End-to-end encryption for private and direct conversations is documented down to the algorithms — AES-GCM 256, RSA-OAEP 2048, PBKDF2 at 100,000 iterations — with keys recovered via a mnemonic phrase, push payloads decrypted on the device, and private-room encryption enforceable server-side since release 8.8.0. The trade-offs are named plainly: encrypted content cannot be audited, encrypted messages do not appear in search, federated rooms are exempt, and losing all session keys makes a conversation permanently inaccessible. Granular role-based access control, SSO, LDAP, SAML and MFA round out the access side. 6 7 9 2 7

Report an error

Retention, discovery & co-determination

How this is scored

The archive as a legal object: retention policies, export for discovery, audit, and the monitoring features a works council will ask to have switched off under BetrVG §87(1) no. 6.

0 — A messenger with no organisation-level administration: each user controls their own history, and the organisation has no central export or retention.

3 — Admin export of workspace data or a history setting, with users controlling their own status.

5 — Configurable retention for messages and files, admin export of workspace data in a documented format, and an audit log or activity log of administrative actions.

8 — Per-channel retention executed per policy, legal-hold and eDiscovery export including edits and deletions, a full admin audit trail, and presence, read receipts or activity analytics switchable off organisation-wide.

10 — Built to pass a works agreement and a subpoena on the same day: granular retention with documented deletion, discovery export a lawyer can use, complete audit, and individual productivity scoring stated as not part of the product.

Report an error

The Platform Engineer

Retention is documented at global and per-room levels with exclusions for pinned messages, threads and discussions, files-only mode, cron control over pruning, a 30-day trash collection before permanent removal, admin-only permissions by default and a user-visible warning in affected rooms. Tamper-evident audit logs are claimed including across federated partners, and message search and export appear among the compliance features, but we found no public information on legal hold or eDiscovery export, or on switching read receipts or activity analytics off organisation-wide. 3 1 2 8

Report an error

Deployment & data custody

How this is scored

Whether the customer can hold their own archive: self-hosting, private cloud, open source, federation, and what an exit actually looks like.

0 — The terms state that the customer's messages cannot be exported or are not returned when the account ends.

3 — Cloud service with an admin export of messages and files.

5 — Cloud service with a documented full export of messages, files and channel structure, or a choice of hosting region, a dedicated instance or a private-cloud option.

8 — A self-hosted edition close to feature parity, or an open-source core with a documented upgrade path, plus complete export including files and metadata.

10 — Custody is the customer's: open-source or source-available server, self-hosting supported as a first-class deployment, open protocol or federation, and a migration path in and out that the vendor documents rather than resists.

Report an error

The Platform Engineer

Self-managed is a first-class deployment: Docker Compose, Podman or Kubernetes with a free Starter up to 50 users, a step-by-step air-gapped guide covering image transfer and private registries, and six months of support per release. The core is MIT-licensed on GitHub with premium components behind a licence, and federation is native — the platform is both a Matrix homeserver and an XMPP server with no bridge to deploy. Migration and workspace-merge services plus a documented Starter-to-paid path without data loss give the exit story I want, tempered by the licensed premium tier. 3 10 11 1 14 2

Report an error

Integrations & extensibility

How this is scored

Bots, webhooks, app framework, identity — whether the chat becomes the place work is noticed, and whether that is buildable without a partner agreement.

0 — A closed messenger: no integrations, webhooks, bots or API.

3 — Incoming webhooks or a handful of named integrations.

5 — An app directory or a list of native integrations with common tools, a documented API, incoming webhooks and bots or slash commands.

8 — A proper app framework with interactive components, event subscriptions with retries, SSO and SCIM provisioning, documented rate limits and a sandbox.

10 — A platform: versioned API with a deprecation policy, an app directory or plugin system with permissions a customer can audit, and integrations the vendor maintains rather than lists.

Report an error

The Platform Engineer

Incoming and outgoing webhooks with JavaScript in an isolated V8 sandbox, configurable retries with selectable delay algorithms, event triggers from message sent to room archived, roughly eighteen named integration guides, a marketplace for plugins with custom app development, REST APIs and SDKs, plus SSO, LDAP, SAML and AD syncing. We found no public information on SCIM provisioning or documented API rate limits, and the marketplace terms let the vendor or an app vendor remove an app at any time, which is the kind of dependency I want in writing before building on it. 12 13 1 12

Report an error

European sovereignty

How this is scored

Where the archive and its metadata live, who the contracting entity is, which subprocessors touch it. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.

0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.

3 — One European element proven — EU data residency for message content, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.

5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (notifications, AI features, analytics) is unstated or partly non-EU.

8 — EU hosting on named infrastructure covering content and metadata, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that removes the question.

Report an error

The Platform Engineer

The contracting entity is a US Delaware corporation, and an EU-hosted sovereign cloud is offered as a deployment choice alongside on-premises and air-gapped, with the captured pages not stating where the managed cloud keeps data by default. A data processing addendum is available on request, and a subprocessors document names each entity's purpose without locations, so the chain is only partly visible. For my money the self-managed and air-gapped options are what actually settle the custody question. 3 9 10 13 1 2

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the annual invoice for their headcount — including the retention, compliance and guest features they actually need — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price or one priced tier per user.

5 — Per-user prices public for the main tiers with the billing period stated and the main features per tier listed.

8 — Every tier priced publicly with per-user maths, history and storage limits, feature boundaries (retention, SSO, eDiscovery), minimum term and VAT treatment stated; self-hosted licensing priced too where offered.

10 — Complete price computability: annual invoice derivable for a given headcount and deployment choice, including guest users, storage and any per-instance licence.

Report an error

The Platform Engineer

No per-user prices are public — commercial plans sit behind a "Get pricing" contact — so an annual invoice is not computable from public pages; the public entry point is a free self-managed Starter workspace limited to 50 users and one workspace per organisation. The terms do state that fees are exclusive of taxes, the initial term runs twelve months with automatic renewal and thirty days' notice, and WhatsApp template messages are billed separately on Facebook's pricing. A buyer can price the free tier and nothing above it. 2 3 10 2

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined unverified
Why unverified?

EU hosting is stated only as one deployment choice alongside self-hosted and air-gapped in homepage marketing copy, and the pages never say where Rocket.Chat's own managed cloud stores data by default.

— uncited Report an error
Hosting options Self-hostable unverified
Why unverified?

Air-gapped deployment requires a paid plan and premium features sit behind a license, but a free self-managed Starter workspace still runs on customer infrastructure.

1/1 pts 10 Report an error
Open source Open source (permissive) unverified
Why unverified?

S4 states the codebase 'includes both open-source and commercial components', so the premium parts of the product are not covered by the MIT License.

1/1 pts 3 Report an error
Data processing agreement On request unverified
Why unverified?

The same paragraph also directs customers to the Privacy Center to access 'the latest privacy agreement templates', and the docs navigation lists a 'Data Processing Agreement (GDPR)' article, so the DPA may also be retrievable online.

0/1 pts 3 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Rocket.Chat

Is Rocket.Chat European?

No. whats-best.ai classifies Rocket.Chat as Rest of world.

Where does Rocket.Chat store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does Rocket.Chat have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to Rocket.Chat?

As of 19 Nov 2026, the panel rates Stackfield (3.5/5), Mattermost (3.5/5) and Element (3.5/5) highest among the other 27 Business Instant Messaging products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Stackfield (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Rocket.Chat alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (15)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.rocket.chat Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 5 Oct 2026 Details →
  2. 2 Pricing www.rocket.chat Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 5 Oct 2026, 11 Sep 2026, 31 Aug 2026 Details →
  3. 3 Terms of service docs.rocket.chat Checked 16 Nov 2026 Details →
  4. 4 Channels, threads & search — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
  5. 5 Channels, threads & search — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
  6. 6 Encryption & access control — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
  7. 7 Encryption & access control — found from sitemap docs.rocket.chat Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  8. 8 Retention, discovery & co-determination — found from sitemap docs.rocket.chat Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 5 Oct 2026 Details →
  9. 9 Retention, discovery & co-determination — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
  10. 10 Deployment & data custody — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
  11. 11 Deployment & data custody — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
  12. 12 Integrations & extensibility — found from sitemap docs.rocket.chat Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
  13. 13 Integrations & extensibility — found from sitemap docs.rocket.chat Checked 16 Nov 2026 Details →
  14. 14 Self-hosting / on-premises installation docs — found from the homepage www.rocket.chat Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
  15. 15 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 1 Nov 2026 Details →