Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

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

by Element (New Vector Ltd) · element.io

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

Link to this page

Element: AI-assisted analysis on whats-best.ai Element: 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.

Element at a glance

Vendor
Element (New Vector Ltd)
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
Yes, per the vendor’s own page source, captured 16 Nov 2026
Panel verdict
The AI panel rates Element 3.5/5, the mean of 6 judges. Element is a business instant messaging platform built on the Matrix open standard, and the highest scores go to encryption and access and deployment control, at 9 to 10. how scores are made
As of
Vendor pages captured 19 Oct 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

Element alternatives, European ones first →

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

The panel's verdict

Element is a business instant messaging platform built on the Matrix open standard, and the highest scores go to encryption and access and deployment control, at 9 to 10. End-to-end encryption is on by default, built on the open Olm and Megolm protocols audited by NCC Group; self-hosting on-premise, in a private cloud or air-gapped is sold with vendor support. Pricing transparency is the weak point at a flat 3: beyond the free-to-use Community edition for up to 100 self-hosted users, the Pro tier reads "Priced per seat/month" and the Sovereign edition "Priced per deployment", both behind "Talk to an expert", so no annual invoice can be computed. Governance and discovery sits at 6 with no spread, while no public information appears on legal hold or eDiscovery export. Sovereignty drew the widest spread, 5 to 7: lower scores weigh the UK-registered controller and subprocessors listed with no locations given; higher ones credit customer-selectable AWS hosting in Amsterdam and Stockholm and the self-hosted, air-gapped route that removes the question.

Report an error

Speaks for it

  • End-to-end encryption is on by default, built on the open Olm and Megolm protocols and positively audited by NCC Group
  • Self-hosting on-premise, in a private cloud or air-gapped is sold with vendor support, official Helm charts and federation on the Matrix open standard
  • Rules-based retention for messages and media is documented, with redacted or deprovisioned data permanently deleted after seven days
  • Spaces build enterprise-wide room hierarchies that can be shared externally with customers and partners over federation
  • Bots for GitHub, GitLab, JIRA and RSS, webhooks and in-room widgets are documented, alongside single sign-on via OIDC, SAML, LDAP and SCIM

Report an error

Held against it

  • Beyond the free Community edition, the paid tiers are listed as "Priced per seat/month" and "Priced per deployment" behind "Talk to an expert", with no amounts shown
  • The Community homeserver is stated as not for use in production environments, and the licence of the subscription server components is not named
  • We found no public information on legal hold, eDiscovery export, or switching read receipts off organisation-wide
  • The data controller is Element Creations Ltd in the United Kingdom with the UK ICO as supervisory authority, and the subprocessor list is published with no locations given
  • We found no public information on message editing history, pinned items, or search filters by channel, person and date

Report an error

Best for

  • You need end-to-end encryption on by default, on openly audited cryptography, for sensitive internal communication
  • You must run your own infrastructure — on-premise, in a private cloud, or air-gapped without internet connectivity — and want vendor support alongside it
  • You collaborate across organisational boundaries and need room hierarchies that can be shared externally over federation
  • You operate in a sector such as government, defence, healthcare or finance where control over infrastructure and communication data is critical

Report an error

Avoid if

  • You need a figure for budgeting before contacting sales — the only public figure is the free Community edition for up to 100 users
  • Your procurement requires an EU data controller — the captured pages name Element Creations Ltd in the United Kingdom as controller, under the UK ICO
  • You want a production-grade deployment on the fully free path — the Community homeserver is stated as not for use in production environments

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Channels, threads & search 3.5 of 5
Encryption & access control 5 of 5
Retention, discovery & co-determination 3 of 5
Deployment & data custody 4.5 of 5
Integrations & extensibility 3.5 of 5
European sovereignty 3 of 5
Pricing transparency 1.5 of 5

Channels, threads & search

Show reasoning
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 Team Lead

Threads, reactions, polls, attachments, search that works even inside encrypted rooms, and unlimited data history — the daily surface is documented and would survive a busy Tuesday. Spaces and subspaces let admins build enterprise-wide room hierarchies and share them externally across organisations, which covers the cross-boundary half. We found no public information on pinned or saved items, message editing history, or search filters by channel, person and date, so I stop short of the top. 2 5 6

Report an error

The Security Officer

Threads, reactions, attachments and search are documented — search even inside encrypted rooms — with unlimited history stated outright, so a decision from eighteen months ago is still there and findable. Spaces build enterprise-wide room hierarchies that can be shared externally, but I found no public information on message edit history, pinned and saved items, filtered search by channel, person and date, or channel lifecycle management, which is what would make the archive a working knowledge base. 2 5 6

Report an error

The Works Council Advocate

Threads, reactions, attachments and search that works inside encrypted rooms are documented, with unlimited history and Spaces that can be shared across organisational boundaries under permissions tied to single sign-on. We found no public information on message editing history, pinned items, or search filters by channel, person and date, which keeps this above the middle but not at the top. 2 5 6

Report an error

The Compliance Counsel

Threads, reactions, attachments, polls and read receipts are documented, with search that works inside encrypted rooms and unlimited data history stated plainly; Spaces build enterprise-wide room hierarchies that can be shared externally over federation. What I cannot find is message editing history, pinned items, search filterable by channel, person or date, or documented channel lifecycle — the pieces that make an archive usable as a working record. 2 5 6 12

Report an error

The Platform Engineer

Threads, reactions, attachments, polls and voice messages are documented, Spaces build enterprise-wide hierarchies that can be shared externally under SSO-assigned permissions, search runs even inside encrypted rooms, and history is stated as unlimited. The captured pages are silent on message editing history, pinned and saved items, and search filters by channel, person or date, which is what keeps this short of the top. 2 5 6

Report an error

The Skeptic

Threads, reactions, attachments and read receipts are listed plainly, search inside encrypted rooms is stated, and "Unlimited data history" is claimed outright — that part I checked for the cap and found none. But the captured pages show no message editing history, no pinned or saved items, and no search filters by channel, person and date, which is how you actually find a decision from eighteen months ago; Spaces shareable externally with customers and partners give real cross-organisation rooms. 2 5 6

Report an error

Encryption & access control

Show reasoning
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 Team Lead

End-to-end encryption is on by default, built on the open Olm and Megolm protocols and publicly and positively audited by NCC Group, and the vendor states plainly that encrypted information is never accessed by its teams or shared externally. Identity verification is in the product via cross-signed device verification with QR code or emoji checks, with SSO, SAML and SCIM around it. This is exactly the first-class end-to-end mode I want to see. 2 3 6

Report an error

The Security Officer

This is what I want to see in writing: end-to-end encryption is on by default, built on open, named cryptography (Olm/Megolm) and positively audited by NCC Group, devices verify by QR code or emoji string, and the vendor states plainly that end-to-end encrypted information is never accessed by its teams or shared externally. Two-factor authentication, OIDC single sign-on, and moderation and anti-virus in the encrypted environment are documented too; the one confirmation I could not find is an administrator explicitly revoking sessions or devices. 6 3 2

Report an error

The Works Council Advocate

End-to-end encryption is the default, built on the open Matrix standard with Olm and Megolm and a public NCC Group audit, with device verification by QR code or emoji and per-device decryption. The vendor states plainly that end-to-end encrypted information is never accessed by its teams and that only conversation participants can decrypt — exactly the posture a works council needs when it discusses things management must not be able to read. 2 3 6

Report an error

The Compliance Counsel

End-to-end encryption is the default on open, independently audited cryptography — Olm and Megolm, positively reviewed by NCC Group — and the vendor states plainly that encrypted information is never accessed by its teams and that only conversation participants can decrypt. Cross-signed device verification by QR code or emoji gives users identity verification they can actually perform, with SSO, OIDC, LDAP and SCIM documented alongside and two-factor authentication available. 2 3 6

Report an error

The Platform Engineer

End-to-end encryption is the default with decryption restricted to conversation participants, built on the named Olm/Megolm protocols and publicly audited by NCC Group, with cross-signed device verification via QR or emoji and per-device decryption. The vendor states plainly that end-to-end encrypted information is never accessed by its teams, and SSO arrives via OIDC/SAML with SCIM provisioning and granular Space-level permissions. 2 3 5 6

Report an error

The Skeptic

The sentences I hunt for exist verbatim: end-to-end encryption by default, "Messages can only be decrypted by participants in the conversation", and "end-to-end encrypted information is never accessed by our teams or shared externally". The cryptography is open and named — Olm and Megolm on the Matrix standard — publicly audited by NCC Group, with cross-signed device verification by QR code or emoji, single sign-on via OIDC, SCIM and LDAP, and two-factor authentication. What I found no public information on is key backup or recovery for an ordinary user who loses a device, so I stop one short of the top. 2 3 6

Report an error

Retention, discovery & co-determination

Show reasoning
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 Team Lead

Rules-based retention for messages and media, auditing as an official record for compliance, and a documented 7-day window before permanent deletion cover the legal basics. The vendor states it does not profile homeserver users, and analytics run on self-hosted Matomo with opt-in, which a works council will appreciate. We found no public information on legal hold or eDiscovery export, per-channel retention, or switching read receipts and presence off organisation-wide, so the subpoena test stays open. 2 3 6 10

Report an error

The Security Officer

Rules-based retention for messages and media, audit bots, and an official record of conversations for compliance are stated, and the deletion clock is documented — redacted content and deprovisioned servers are permanently deleted after seven days, exactly the plain statement I want beside a deletion claim. I found no public information on legal-hold or eDiscovery export, a documented export format, or organisation-wide switch-off of read receipts and presence, which a works council will ask to have switched off. 2 6 10 3

Report an error

The Works Council Advocate

Rules-based retention for messages and media is documented, deletion is stated as permanent after seven days, auditing and moderation sit in the admin configuration, and the vendor states it does not profile homeserver users, which I welcome. We found no public information on legal-hold or eDiscovery export, and read receipts are listed as a feature while we found no public information on switching them off organisation-wide — that is the first question I would put to the vendor before any works agreement. 2 3 5 10

Report an error

The Compliance Counsel

Rules-based retention for messages and media, a stated seven-day window before permanent deletion, auditing described as capturing an official record of conversations for compliance, and a stated commitment not to profile homeserver users give me the bones of a defensible archive. We found no public information on legal hold, on a discovery export that captures edits and deletions, or on switching read receipts off organisation-wide — until those are documented, the subpoena test is unproven. 2 3 6 10

Report an error

The Platform Engineer

Rules-based retention policies for messages and media, compliance auditing, audit bots and corporate moderation are all documented, and redacted or deprovisioned data is permanently deleted after seven days. I found no public information on legal hold or eDiscovery export, and read receipts appear as a feature without a documented organisation-wide switch-off, so a works council negotiation would start from unanswered questions. 2 3 6 10

Report an error

The Skeptic

Rules-based retention for messages and media is documented, deletion behaviour is documented down to a 7-day purge window before permanent removal, and auditing is sold as capturing "an official record of conversations for compliance". I found no mention of legal hold, a discovery export including edits and deletions, or a full administrative audit trail, and read receipts are offered with no stated organisation-wide off-switch — the works-council question gets half an answer. 2 3 6 10

Report an error

Deployment & data custody

Show reasoning
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 Team Lead

Custody is genuinely the customer's option: Synapse and Element Server Suite Community are AGPLv3, self-hosting on-premise or in a private cloud comes with vendor support, official Helm charts and air-gapped installs, and the federated Matrix protocol keeps the door open. Migration is stated publicly as easy data movement protecting against vendor lock-in, though the export format is not detailed. One caution: the Community homeserver is stated as not for production environments, and the captured pages did not name a licence for the Pro server components. 2 9 11 12 12

Report an error

The Security Officer

Custody can genuinely be the customer's: the Synapse homeserver is AGPL-licensed with official Helm charts, self-hosting on-premise or in a private cloud is supported by the vendor, air-gapped installation is a first-class offer, and federation plus a stated data export give a documented way in and out. The captured pages do state that the community homeserver is not for production use, and the licence of the subscription enterprise components is not named, so the fully-free path carries a real caveat. 2 8 11 12 12

Report an error

The Works Council Advocate

Custody can genuinely sit with the customer: an AGPL-licensed homeserver, downloadable installation files, official Helm charts, on-premise or private-cloud hosting with vendor support, air-gapped installation, and federation on an open standard. The production-grade Pro components are subscription-sold with their licence not named and the Community homeserver is stated as not for production use, which is the one boundary on an otherwise customer-held archive. 2 8 11 12

Report an error

The Compliance Counsel

Custody is genuinely available to the customer: the Synapse homeserver is released under AGPL-3.0, self-hosting on-premise, in a private cloud or air-gapped is sold and supported as a first-class path with downloadable installation files, and federation plus a stated migration promise remove the exit question. The captured pages temper this: the Community homeserver is stated as not for use in production environments, and the licence of the subscription server components is not named. 2 9 11 12 12

Report an error

The Platform Engineer

Custody is the customer's: AGPL-licensed server components, self-hosting on-premise or in a private cloud with the vendor's own support team, LTS releases every six months with backported security fixes, official Helm charts for GitOps deployment, air-gapped installs, open-protocol federation, and data migration stated as protection against vendor lock-in. The free Community homeserver is flagged as not for production, so the supported self-hosted path is the subscription Pro edition — documented, not a hobby build. 2 8 9 11 12

Report an error

The Skeptic

Self-hosting is the product, not an afterthought: a free self-hosted community edition for up to 100 users, official helm charts, on-premise or private cloud with vendor support, air-gapped installs, federation on an open protocol, and a stated ability to easily migrate data against vendor lock-in. Two caps a buyer should read: AGPLv3 covers "the majority of Element software" with enterprise features on subscription, and the community homeserver is stated as not for use in production environments — the free path stops short of production. 2 8 9 11 12

Report an error

Integrations & extensibility

Show reasoning
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 Team Lead

Bots for GitHub, GitLab, JIRA and RSS, webhooks, and widgets that put Grafana dashboards, Jitsi calls, Etherpad notes and shared spreadsheets right inside the room — this is how the chat becomes where work gets noticed. SSO, SAML and SCIM provisioning are documented, and 148 public repositories with contributed SDKs point to a real developer platform. We found no public information on a sandbox, documented rate limits, or event subscriptions with retries, so I cannot call it a full app framework yet. 2 5 10 12

Report an error

The Security Officer

Webhooks, bots that sit in rooms and respond to commands, and widgets embedding interactive apps are documented, alongside single sign-on, LDAP, SAML and SCIM provisioning — and with 148 public repositories this is buildable without a partner agreement. I found no public information on documented rate limits, event delivery with retries, or a sandbox, which is what separates a list of integrations from a true platform. 10 2 5 12

Report an error

The Works Council Advocate

Webhooks, bots for GitHub, GitLab, JIRA and RSS, and interactive widgets embedded in rooms are listed, alongside identity integration through single sign-on, OIDC, LDAP, SCIM and SAML. We found no public information on documented rate limits, a sandbox, or event subscriptions with retries, so this falls short of the platform tier. 2 5 10

Report an error

The Compliance Counsel

Widgets embed full interactive apps into rooms, with bots for GitHub, GitLab, JIRA and RSS, webhooks, and SSO with SCIM provisioning all documented. We found no public information on event subscriptions with retries, documented rate limits or a sandbox, so the evidence stops short of a fully documented platform. 2 10 12

Report an error

The Platform Engineer

Webhooks, named bots for GitHub, GitLab, JIRA and RSS, interactive widgets embedded directly in rooms, and full identity plumbing through OIDC, SAML, LDAP and SCIM; the open Matrix standard plus 148 public repositories means extensibility is buildable without a partner agreement. The captured pages are silent on documented rate limits, a sandbox, and app permissions a customer could audit. 2 10 12

Report an error

The Skeptic

Webhooks, bots for GitHub, GitLab, JIRA and RSS, and widgets that "embed full-blown interactive apps" into rooms are all documented, alongside single sign-on via OIDC, SCIM and LDAP for identity. I found no public information on a documented API statement, rate limits, a sandbox, or any API versioning and deprecation policy. 2 10 12

Report an error

European sovereignty panel opinion

Show reasoning
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 Team Lead

Hosting is named: admin in an AWS data centre in Amsterdam, deployments in Stockholm, and customer deployments can choose their geographical location, with a self-hosted and air-gapped option that removes the custody question entirely. The contracting chain is Element Creations Ltd in London with named French and German subsidiaries, and subprocessors are listed by name and purpose — Cloudflare, Twilio, Salesforce, Hubspot among them — but without locations, and the captured pages reference a data processing agreement without publishing its terms. European hosting plus the self-hosted escape hatch earns a strong score; unnamed subprocessor locations and a UK rather than EU controller keep it off the top. 2 3 4

Report an error

The Security Officer

Hosting is European-selectable on named AWS regions (Amsterdam, Stockholm) with customer choice of deployment location, and the subprocessor chain is published by name — Cloudflare, Twilio, Salesforce and others, partly non-European, but without stated locations. The controlling entity is Element Creations Ltd in the United Kingdom with French and German subsidiaries, a data processing agreement is referenced, and the self-hosted, air-gapped option can remove the question entirely. 3 4 2 8

Report an error

The Works Council Advocate

Hosting runs on AWS in Amsterdam and Stockholm with customer region choice, the group has French and German subsidiaries alongside a UK parent and a US entity, and subprocessors are named with their purposes while we found no locations stated for them; the data processing agreement itself was not among the captured pages. Self-hosting and air-gapped deployment let a customer take the whole question into its own hands, which is why this lands mid-scale rather than low. 2 3 4 8

Report an error

The Compliance Counsel

EU hosting is selectable on named AWS regions in Amsterdam and Stockholm with the customer choosing the location, the group includes French and German entities alongside the London controller, a data processing agreement is referenced by name, and self-hosting can remove the question entirely. Against that, the subprocessor list is published with purposes but without locations, and the named controller is UK-registered under the ICO rather than an EU entity. 2 3 4

Report an error

The Platform Engineer

Customer deployments can select their geographical location on named AWS infrastructure, with the vendor's own servers in Amsterdam and Stockholm, and the subprocessor list is published with purposes — Cloudflare, Twilio, Salesforce, Hubspot, MapTiler, Quaderno, LiveKit — though without locations. The stated controller is the UK entity with French and German subsidiaries and the UK ICO as supervisory authority, and the self-hosted plus air-gapped options remove most of the custody question for a buyer who runs it themselves. 2 3 4

Report an error

The Skeptic

Hosting for the managed service sits on named AWS regions in Amsterdam and Stockholm with customer region choice, and the subprocessor list is published by name and purpose — Cloudflare, LiveKit, MapTiler, Twilio, Salesforce, Salesloft, Hubspot, Quaderno — but with no locations given. The data controller on the captured pages is the UK company Element Creations Ltd with the ICO as supervisory authority, in-house analytics are hosted in London, and the German and French subsidiaries exist but their contracting role is unstated. Self-hosting and air-gapped deployment let a customer remove the question entirely, which keeps this above the middle. 3 4 11

Report an error

Pricing transparency

Show reasoning
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 Team Lead

A pricing page exists and Element Server Suite Community is free-to-use for up to 100 self-hosted users, which is one publicly priced tier. But Element Server Suite Pro is listed only as "Priced per seat/month" and the Sovereign edition "Priced per deployment", both behind "Talk to an expert", with no figures, VAT treatment or minimum terms shown. A buyer cannot compute the annual invoice for a given headcount from the public pages. 2 1 12

Report an error

The Security Officer

Only the Community edition carries a public figure — free to use for up to 100 users — while the professional edition is 'Priced per seat/month' and the Sovereign edition is 'Priced per deployment', both behind 'Talk to an expert', with server price minimums mentioned but never stated. A buyer cannot compute an annual invoice from these pages. 2 8 1

Report an error

The Works Council Advocate

The Community edition is fully priced at zero for up to one hundred users with tier boundaries and server minimums public, but the Pro seats and the per-deployment Sovereign edition carry no figures and point to talking to an expert. A works council could not compute the annual invoice for its headcount from these pages. 2 1 12

Report an error

The Compliance Counsel

One tier is publicly priced — the self-hosted Community edition at no cost, supporting up to 100 users — with user bands of one to a hundred, from a hundred, and per deployment, plus stated server minimums. Every paid tier reads 'Talk to an expert' with 'Priced per seat/month' and 'Priced per deployment' but no figures, so no annual invoice can be computed from public pages. 2 8 12

Report an error

The Platform Engineer

The free self-hosted Community edition up to 100 users is public, but the Pro edition is labelled per seat per month and the Sovereign edition per deployment, both without figures and both behind a talk-to-an-expert conversation, with price minimums referenced but not stated. I cannot compute an annual invoice for a headcount from these pages. 2 8 1

Report an error

The Skeptic

The only figure on any captured page is the free-to-use self-hosted community edition for up to 100 users; the professional tiers say "Priced per seat/month" and "Priced per deployment" with no amounts, route commercial buyers to "Talk to an expert", and reference unspecified "price minimums" for additional servers. A buyer cannot compute an annual invoice for any paid deployment from these pages. 2 8 12

Report an error

European sovereignty — proven facts

2 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 — uncited Report an error
Hosting options Self-hostable 1/1 pts 2 Report an error
Open source Open source (copyleft) unverified
Why unverified?

The AGPL licence is stated for the Community edition; enterprise components (Synapse Pro, Element Server Suite Pro) are sold on subscription and their licence is not named.

1/1 pts 2 Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Element

Is Element European?

Yes, though not from the EU. whats-best.ai classifies Element as UK / wider Europe.

Where does Element store data?

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

Does Element have a free plan?

Yes. Element has a free plan, per the vendor’s page captured 16 Nov 2026.

What are the best alternatives to Element?

As of 19 Nov 2026, the panel rates Stackfield (3.5/5), Mattermost (3.5/5) and Wire (Messaging) (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: Element 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 (12)

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

  1. 1 Vendor homepage element.io Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  2. 2 Pricing element.io Checked 16 Nov 2026 Details →
  3. 3 Privacy policy element.io Checked 16 Nov 2026 Details →
  4. 4 Legal notice element.io Checked 16 Nov 2026 Details →
  5. 5 Channels, threads & search — found from sitemap element.io Checked 16 Nov 2026 Details →
  6. 6 Encryption & access control — found from sitemap element.io Checked 16 Nov 2026 Details →
  7. 7 Encryption & access control — found from sitemap element.io Checked 16 Nov 2026 Details →
  8. 8 Deployment & data custody — found from sitemap element.io Checked 16 Nov 2026 Details →
  9. 9 Deployment & data custody — found from sitemap element.io Checked 16 Nov 2026 Details →
  10. 10 Integrations & extensibility — found from sitemap element.io Checked 16 Nov 2026 Details →
  11. 11 Self-hosting / on-premises installation docs — found from the homepage element.io Checked 16 Nov 2026 Details →
  12. 12 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →