whats-best.ai
Search Sign in

Business Instant Messaging

Pumble

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 CAKE.com · pumble.com

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

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

The Security Officer

Weighted verdict

Assumes the archive will one day be read by someone it was not meant for. Wants end-to-end encryption that ordinary users survive, device verification, sessions an admin can revoke, and a plain statement of what the vendor cannot decrypt.

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

Scored by The Security Officer

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 Security Officer

Channels, real threads, direct and group messaging, and file sharing are all stated, and unlimited message history with search that finds any message, whenever it happened, removes any history cap. Mentions, reactions, message edit history, search filters, and channel lifecycle are things I found no public information on, which keeps this short of the working-knowledge-base standard. 1

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 Security Officer

On what I weigh first — what is encrypted and against whom — I found no public information: no statement on transport or at-rest encryption, no key handling, and no plain statement of what the vendor can or cannot read. Guest access is described as limited for external people, and that is the only access-control detail captured. I found no public information on per-channel roles, SSO, device verification, or sessions an admin can revoke. 1

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 Security Officer

For the archive as a legal object I found no public information on retention policies, admin export in a documented format, audit logs, or whether presence and activity analytics exist and can be switched off. Unlimited message history is a user-facing feature, not a retention regime. 1

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 Security Officer

Mac, Windows, Linux, Android, iOS and Web are clients, not custody. I found no public information on self-hosting, a dedicated private instance, source availability, federation, or a documented exit export, so nothing captured speaks to a customer holding their own archive. 1

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 Security Officer

An API is confirmed available and MCP is offered, with named integrations including Google Drive, Clockify and Plaky. I found no public information on webhooks, a bot account model, SSO, documented rate limits, or a sandbox, so the question of a buildable platform stays open. 1

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 Security Officer

The sovereignty record is empty: the contracting entity is CAKE.com Inc., and I found no public information on where hosting or metadata sit, or which subprocessors touch the archive. No element of an EU chain — hosting, entity attributes, certification, subprocessor list — is evidenced. 1

Report an error

Pricing transparency not rated — the vendor publishes no price

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 Security Officer

The plan ladder is public — Free, Pro, Business, Enterprise — and the free tier is unusually clear: unlimited users, unlimited channels and unlimited message history at no cost. I found no public information on per-user prices for the paid tiers or on where SSO, retention and compliance capabilities begin, so a buyer cannot compute an annual invoice from the captured pages. 1

Report an error

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 Pumble? Tell us Report an error on this page

Sources (8)

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

  1. 1 Vendor page pumble.com Checked 22 Sep 2026 Details →
  2. 2 Channels, threads & search — found from sitemap pumble.com Checked 1 Oct 2026 Details →
  3. 3 Channels, threads & search — found from sitemap pumble.com Checked 1 Oct 2026 Details →
  4. 4 Encryption & access control — found from sitemap pumble.com Checked 1 Oct 2026 Details →
  5. 5 Retention, discovery & co-determination — found from sitemap pumble.com Checked 1 Oct 2026 Details →
  6. 6 Retention, discovery & co-determination — found from sitemap pumble.com Checked 1 Oct 2026 Details →
  7. 7 Integrations & extensibility — found from sitemap pumble.com Checked 1 Oct 2026 Details →
  8. 8 Integrations & extensibility — found from sitemap pumble.com Checked 1 Oct 2026 Details →