whats-best.ai
Search Sign in

Business Instant Messaging

Troop Messenger

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

by Troop Messenger · www.troopmessenger.com

Report an error on this page Is this your product? →

Link to this page

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

Troop Messenger at a glance

Vendor
Troop Messenger
Headquarters
Not stated on the vendor’s pages as of 27 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 27 Oct 2026
Free plan
Not stated on the vendor’s pages as of 27 Oct 2026
Panel verdict
The AI panel rates Troop Messenger 2/5, the mean of 6 judges. Troop Messenger is a self-hosted business instant messaging product. how scores are made
As of
Vendor pages captured 27 Oct 2026; evaluated by the panel 27 Oct 2026. all sources

Troop Messenger 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 2 of 5 2 of 5
Encryption & access control 3.5 of 5 3.5 of 5
Retention, discovery & co-determination 2 of 5 2 of 5
Deployment & data custody 3.5 of 5 3.5 of 5
Integrations & extensibility 2 of 5 2.5 of 5
European sovereignty 1 of 5 1 of 5
Pricing transparency 0.5 of 5 0.5 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 — Flat group chats with no threads; search covers recent messages only, and history is capped.

3 — Channels and direct messages with basic search, but threading is awkward or absent and file handling is a plain attachment list.

5 — Public and private channels, real threads, mentions and reactions, file sharing with previews, and full-text search across the whole 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 a documented history limit or none at all.

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

Group chats and dedicated rooms exist, and a reply encloses the original message rather than threading a conversation; we found no public information on mentions, reactions, or a public/private channel split. Search is the strong suit — filters by contact, file, image, link, flag and read-receipt state go well past basic. Attachment previews are documented, but we found no public information on history limits or date-filtered search, so finding a decision from eighteen months back is not something I can credit. 2 3 6 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 — Transport encryption only, undocumented; no role model beyond admin, guests indistinguishable from members.

3 — TLS and encryption at rest with vendor-held keys, basic roles, and guest access that mostly works.

5 — The above plus configurable roles per channel, SSO, guest accounts with scoped visibility, and a clear statement of what the vendor can read.

8 — Optional end-to-end encryption for direct messages or private rooms with the trade-offs named, device verification, session management an admin can revoke, 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

An admin chooses per deployment between Plain, Standard AES-256, and end-to-end encryption, and the trade-offs are named in public: end-to-end mode restricts the web client, disables the monitoring tool, and hands private keys to users who lose their account if they lose the key. Multi-factor authentication is unusually deep — five methods, admin enforcement on the app and dashboard, idle timeout, offline validation. We found no public information on device verification, identity verification, or admin-revocable sessions, and the cryptography is described only as a public-private key pair. 4 5 6

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.

0 — No retention policy, no export beyond a manual copy, no audit log, and presence or activity analytics that cannot be disabled.

3 — Manual export of some data and a global history limit, but no per-channel retention, no audit log and no admin control over analytics.

5 — Configurable retention per channel or workspace, admin export in a documented format, an audit log of administrative actions, and status or presence that a user can control.

8 — Legal-hold and eDiscovery export including edits and deletions, retention executed per policy and evidenced, full admin audit trail, and 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 no individual-level productivity scoring anywhere in the product.

Report an error

The Platform Engineer

Every action is logged, exportable, and SIEM-ready via Syslog, which is a genuinely strong administrative audit posture. Retention is framed as a consequence of running your own server — "how long it is kept" is the customer's decision — rather than a documented per-channel policy, and we found no public information on legal hold, discovery export in a lawyer-usable format, or user control over presence and activity analytics. The air-gapped edition ships a lawful-interception monitor, which is exactly the feature a works council will want switched off or contractually bounded. 6 7

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 — Cloud-only, proprietary, with export limited to a partial archive.

3 — Cloud-only, but with a documented full export in an open-ish format.

5 — A private-cloud or dedicated-instance option, or a self-hosted edition that lags the cloud significantly; full export documented.

8 — A genuine self-hosted edition close to feature parity, or 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-hosting here is a supported deployment, not a hobby build: Docker or Windows installers, named Linux distributions, MySQL 8+, high-availability and disaster-recovery configurations, a fully air-gapped variant with defence customers, and dedicated deployment support under a custom SLA. The vendor positions the on-premise edition against open-source platforms rather than on source availability, and we found no public information on federation or an open protocol. What holds it back is the exit: we found no public information on export of files and metadata, or on an upgrade path that says what happens to a customised install. 6 7

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 — No API, no webhooks, no bots.

3 — Incoming webhooks and a handful of native integrations; no bot framework, no documented limits.

5 — Documented REST API, incoming and outgoing webhooks, slash commands, a bot account model, and SSO.

8 — A proper app framework with interactive components, event subscriptions with retries, 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

Backend APIs for administrative tasks, users and groups, JavaScript SDKs, and a genuinely bidirectional Zapier link with ready-made templates — alongside LDAP, Active Directory and SSO — clear the documented-API bar. The chat-API offering is really an embed-our-messaging product, which is adjacent to extensibility rather than proof of it. We found no public information on a bot framework, slash commands, SCIM provisioning, documented rate limits, or an app directory whose permissions a customer could audit. 7 8 9

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.

0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.

3 — EU data residency offered for message content while metadata, search indexes or support tooling remain non-EU, or the contracting entity sits outside the EU.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — notifications, AI features, analytics — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, full subprocessor list published, 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

Vendor jurisdiction, ownership, data residency and subprocessor exposure are all unevidenced, and we found no public information on certification. The one real mitigation is deployment choice: the on-premise and air-gapped editions put the archive on infrastructure the customer owns, with the vendor stating that no vendor, cloud provider or outsider can reach the communication. For the SaaS edition specifically we found no public information on where data or its metadata is processed. 6 7

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 per-user headline exists, but the tier where retention control, SSO or compliance export begins is unstated.

5 — Per-user prices public with billing period stated, but at least one commonly needed capability (unlimited history, SSO, eDiscovery) sits in an unpriced enterprise tier.

8 — Every tier priced publicly with per-user maths, history and storage limits, feature boundaries, 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

The captured pages contain no price figure at all; the pricing route is a tailored quote returned within one business day, topped by a custom SLA. The only published commercial terms are a fifteen-day full-featured trial and no credit card required. A buyer can evaluate without a conversation but cannot compute any invoice from public pages. 6 7

Report an error

European sovereignty — proven facts

0 of 4 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.

Ownership Not determined — uncited Report an error
Data residency Not determined — uncited Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

Questions about Troop Messenger

Is Troop Messenger European?

Not determined: the vendor’s pages as captured do not say where Troop Messenger is based.

Where does Troop Messenger store data?

Not stated on the vendor’s pages as of 27 Oct 2026.

Does Troop Messenger have a free plan?

Not stated on the vendor’s pages as of 27 Oct 2026.

What are the best alternatives to Troop Messenger?

As of 27 Oct 2026, the panel rates Element (3.5/5), Mattermost (3.5/5) and Stackfield (3/5) highest among the other 23 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 Element (UK / wider Europe). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Troop Messenger 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.

Do you know more about Troop Messenger? Tell us Report an error on this page

Sources (9)

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

  1. 1 Vendor page www.troopmessenger.com Checked 27 Oct 2026 Details →
  2. 2 Channels, threads & search — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
  3. 3 Channels, threads & search — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
  4. 4 Encryption & access control — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
  5. 5 Encryption & access control — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
  6. 6 Deployment & data custody — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
  7. 7 Deployment & data custody — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
  8. 8 Integrations & extensibility — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →
  9. 9 Integrations & extensibility — found from sitemap www.troopmessenger.com Checked 27 Oct 2026 Details →