Zulip
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 4 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Kandra Labs, Inc. · zulip.com
Report an error on this page Is this your product? →
Link to this page
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.
Zulip at a glance
- Vendor
- Kandra Labs, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Outside the EU by default; pages mention the United States source, captured 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 16 Nov 2026
- Panel verdict
- The AI panel rates Zulip 3/5, the mean of 6 judges. Zulip, an open-source team chat app from Kandra Labs, Inc., scores highest on deployment control — 9, the top mark recorded — where an Apache 2.0 server, self-hosting that runs the same software as the cloud, and documented import, export and static HTML archive make custody genuinely available. how scores are made
- As of
- Vendor pages captured 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Zulip, an open-source team chat app from Kandra Labs, Inc., scores highest on deployment control — 9, the top mark recorded — where an Apache 2.0 server, self-hosting that runs the same software as the cloud, and documented import, export and static HTML archive make custody genuinely available. It scores lowest on sovereignty, 3-4: the cloud service is stated to be hosted and operated in the United States, with Google and Stripe named as processors; the European elements proven are an EU representative in Cork, a UK representative and GDPR rights, and we found no public information on an EU hosting option for the cloud service. Messaging core sits at 7-8 on topic-based threading, and encryption and access at 6, where the only end-to-end encryption claim covers mobile push notifications. The scores spread on governance and discovery, 4-6: retention policies and compliance exports are documented, and the lower scores weigh the absence of a documented administrative audit log and legal hold more heavily. Integrations and pricing transparency hold at 7.
Speaks for it
- Self-hosting under an Apache 2.0 licence runs the same software as the cloud, with documented setup, backup and upgrade scripts.
- Documented way in and out: imports from Slack, Teams, Mattermost and Rocket.Chat, and export to your own server or a static HTML archive.
- Per-user prices published for every tier, including a priced self-hosted Business licence at $6.67 /user/month billed annually or $8 billed monthly.
- Topic-based threading with per-channel, role and user-group permission controls, and SSO plus SCIM user and group sync.
- 130+ native integrations with thousands more via Zapier and IFTTT, a documented REST API and custom webhooks.
Held against it
- The cloud service is stated to be hosted and operated in the United States, and we found no public information on an EU hosting option.
- The only end-to-end encryption statement covers mobile push notifications, and we found no public information on end-to-end encryption of message content or customer-managed keys.
- We found no public information on an administrative audit log, legal hold, or per-channel retention.
- Cloud LDAP sync and Enterprise support sit behind "Please inquire", with no public information on VAT treatment or minimum contract terms.
- Account deletion re-associates messages a user sent to others to a "Deleted User" rather than removing them.
Best for
- You need to hold your chat archive on your own infrastructure, self-hosting on Ubuntu, Debian, Docker or prebuilt Digital Ocean and Render images.
- You are migrating from Slack, Teams, Mattermost or Rocket.Chat and want documented import tools and a human-readable HTML archive export.
- You want to compute most of an annual invoice from public pages, with per-user prices and user minimums stated per tier.
- You run a non-profit, research or education organisation — sponsorship offers free or discounted Standard plans.
Avoid if
- You need vendor-operated cloud hosting in the EU — the cloud service is stated to be hosted and operated in the United States.
- You require end-to-end encryption of message content — the only end-to-end encryption documented covers mobile push notifications.
- Your deletion requirements call for removing content a user has sent to others — account deletion re-associates such content to a "Deleted User".
The scores
| Criterion | Panel median |
|---|---|
| Channels, threads & search | 4 of 5 |
| Encryption & access control | 3 of 5 |
| Retention, discovery & co-determination | 3 of 5 |
| Deployment & data custody | 4.5 of 5 |
| Integrations & extensibility | 3.5 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 3.5 of 5 |
Channels, threads & search
Show reasoningHide 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.
The Team Lead
Topic-based threading is the product's whole pitch, and it is the one that survives a busy Tuesday: messages move between channels and topics, topics can be marked resolved, and history is not lost in the tidying. Search history is unlimited on paid plans with a stated 10,000-message limit on the Free plan, guests get bounded access, and the archive exports to a static HTML archive a human can read. I found no public information on message edit history, pinned items, or search filters by channel, person and date, so I stop where I do. 2 3 4 5
The Security Officer
Public and private channels with topic-based threading, guest access with limited user-list visibility, file sharing, and a documented search-history limit per plan — 10,000 messages on Free, unlimited on Standard — make the daily surface solid. Moving and resolving topics keeps threads readable, and exporting the message history to a static HTML archive gives a conversation in a form a human can read. We found no public information on message editing history or search filters by channel, person and date, which keeps this short of the very top. 2 3 4
The Works Council Advocate
Channels with public and private variants, distinctive topic-based threading, and search history documented per plan — unlimited on paid plans, a stated 10,000-message limit on the free one — is what a record of who-spoke-when needs. Guest access with restricted user-list visibility and moving messages between channels and topics give the archive a managed life, and the static HTML archive export means a conversation can be handed over in a form anyone can read. We found no public information on search filters by channel, person or date, or on message editing history. 2 3 4
The Compliance Counsel
Topic-based threading, channels, guest access with restricted visibility and documented per-plan search-history limits (10,000 messages on the free plan, unlimited on Standard) are stated, and an organisation's message history can be exported to a static HTML archive a human can read — the feature I care most about. I found no public information on message-editing history, pinned or saved items, or search filters by channel, person and date, so I cannot place it higher. 2 3 4
The Platform Engineer
Channels with topic-based threading, message editing and moving between channels and topics, topic resolution, file sharing and guest users are all documented, with a stated search-history limit per plan — unlimited on paid tiers, 10,000 messages on the free one. Export runs to a static HTML archive a human can actually read. We found no public information on channel archiving, renaming or merging without losing history, or on search filters and ranking, so I stop short of the top. 2 4
The Skeptic
Channels with topic-based threading, moving messages between channels and topics, and guests with configurable access are documented, and the search-history cap is printed where I look for it: 10,000 messages on the Free plan, unlimited on Standard. A static HTML archive export means a conversation can leave in a form a human can read. What I did not find is search with filters by channel, person and date, pinned and saved items, or an editing history for messages. 2 3 4
Encryption & access control
Show reasoningHide 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.
The Team Lead
TLS encryption and encryption at rest are stated, SSO covers SAML, Microsoft Entra ID and OpenID Connect among a hundred-plus options, and an admin can revoke and reset any user's credentials. Permissions go unusually deep — customised per channel, by role, by user group, down to individual users. The only end-to-end encryption statement on the captured pages covers mobile push notifications; I found no public information on end-to-end encryption for messages themselves or customer-managed keys. 2
The Security Officer
Encryption in transit and at rest is stated, permissions are granular down to the individual channel and user group, single sign-on comes in many flavours, and an administrator can revoke and reset any user's credentials — the session control I always insist on. But the only end-to-end encryption documented covers mobile push notifications, not message content, and we found no public information on customer-managed keys, documented key handling, or a plain statement of what the vendor cannot decrypt. Self-hosting changes who holds the keys, but the documented cloud mechanism stops at the server. 2 4
The Works Council Advocate
TLS encryption and data encryption at rest are stated, alongside SSO through SAML and OpenID Connect and permissions configurable per channel, per role and per user group — the room-by-room control a council wants. Administrators can revoke and reset any user's credentials, and mobile push notifications are stated as end-to-end encrypted, but that is the only end-to-end claim on the captured pages. We found no public information on end-to-end encryption for messages themselves, customer-managed keys, or device and session revocation. 2
The Compliance Counsel
TLS and encryption at rest are stated, SSO options run past a hundred, guests can be confined, and per-channel permissions are documented down to editing, deleting and moving messages, with revocation and reset of any user's credentials. I found no public information on end-to-end encryption for message content — only mobile push notifications are called end-to-end encrypted — nor on key handling, which is what I would need for privileged conversations. 2 4
The Platform Engineer
TLS encryption and encryption at rest are stated, along with per-channel posting permissions, permissions by role, user group and individual user, admin revocation of any user's credentials, SSO via SAML, OpenID Connect and Microsoft Entra ID, and SCIM sync. The one end-to-end encryption claim covers mobile push notifications, not conversations. We found no public information on end-to-end encrypted messages or customer-managed keys, so the key-custody question the archive raises stays open. 2
The Skeptic
TLS and encryption at rest are stated, permissions are granular per channel with role and user-group controls, and admins can revoke and reset any user's credentials. SSO with SAML sits in the Plus tier on the cloud plans while the self-hosting pages state SAML and LDAP sync are included without extra payment. The only end-to-end encryption claim on these pages covers mobile push notifications; I found no public information on end-to-end encryption of message content, customer-managed keys, or documented key handling. 2 4
Retention, discovery & co-determination
Show reasoningHide 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.
The Team Lead
Message retention policies come with the Standard plan and with self-hosted Business, which also lists full and compliance data exports, and organisation administrators can export all organisation data. I found no public information on an administrative audit log, legal hold, or an organisation-wide switch-off for the usage statistics the pages advertise — the first things my works council will ask about. 2 3 4
The Security Officer
Message retention policies appear on the Standard cloud plan, and the self-hosted Business plan adds data retention policies alongside full and compliance data exports; organization administrators may export all data for archival or backup, with password hashes explicitly excluded. Deletion is at least honest about its limits — content sent to others is re-associated to a “Deleted User” rather than destroyed. We found no public information on an administrative audit log, legal hold, or whether the usage statistics charts can be switched off organisation-wide. 2 3 4
The Works Council Advocate
Message retention policies are named on the paid plans, the self-hosted business plan includes full and compliance data exports, and organisation administrators may export all data with password hashes excluded. For a works agreement I still need what these pages do not show: we found no public information on an administrative audit trail, legal hold, per-channel retention granularity, or an organisation-wide off switch for the usage statistics charts. Account deletion leaves previously sent messages tied to a 'Deleted User' rather than removing them, so deletion behaviour must be negotiated explicitly. 2 3 4
The Compliance Counsel
Message retention policies appear on the Standard plan and, with "full and compliance data exports", on the self-hosted Business licence, and an organisation administrator may export all data for archival purposes — password hashes excepted — importable to a self-hosted server or a static HTML archive. I found no public information on per-channel retention, legal hold, whether exports capture edits and deletions, or any administrative audit trail, and that last unknown is what keeps me from accepting it sight-unseen for litigation. 2 3 4
The Platform Engineer
Message retention policies are listed on the paid cloud tiers and the self-hosted business plan names full and compliance data exports; organisation administrators may export all data for archival or import to a self-hosted server. We found no public information on per-channel retention, legal hold, an administrative audit trail, or switching presence and read receipts off organisation-wide — exactly the points a works council will raise first. 2 3 4
The Skeptic
Message and data retention policies are listed for the Standard and self-hosted Business plans, organisation administrators may export all data with password hashes excluded, and compliance exports are named for self-hosted Business. I found no public information on an administrative audit log, per-channel retention, or a legal-hold export including edits and deletions. Usage statistics charts are advertised with no organisation-wide switch-off stated — the first question a works council will ask. 2 3 4
Deployment & data custody
Show reasoningHide 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.
The Team Lead
Custody is genuinely the customer's option: Apache 2.0 licensed, self-hostable on Ubuntu, Debian, Docker or prebuilt images, running the same software as the cloud service, with documented setup, backup and upgrade scripts. The way in and out is documented rather than resisted — imports from Slack, Teams, Mattermost and Rocket.Chat, export back to your own servers or a static HTML archive. I found no public information on an open protocol or federation, which is what holds it just below the top. 2 4 5
The Security Officer
This is where I relax: the server is 100% open source under Apache 2.0, self-hosting runs the same software as the cloud on Ubuntu, Debian or Docker with documented setup, backup and upgrade scripts, and the vendor documents movement in both directions — import from Slack, Teams, Mattermost or Rocket.Chat, and export back out again. Custody can genuinely be the customer's. We found no public information on federation or an open protocol, which is the one gap at the top. 2 3 4 5
The Works Council Advocate
Custody can genuinely be ours: the software is 100% open-source under Apache 2.0, self-hosting delivers 'the same software as our Zulip Cloud customers', and documented setup, backup and upgrade scripts back the deployment. Export and import tools are stated to move freely between the cloud and your own servers, with imports from Slack, Teams, Mattermost and Rocket.Chat and a static HTML archive for leaving. Only an open protocol or federation is undocumented, which holds this just short of the top. 2 4 5
The Compliance Counsel
Custody is genuinely available: the server is Apache 2.0 licensed, self-hosting is a first-class deployment on documented platforms with setup, backup and upgrade scripts, and the vendor states you get the same software as its cloud customers. Exit is documented rather than resisted — export and import tools move an organisation freely between cloud and its own servers, and imports from Slack, Teams, Mattermost and Rocket.Chat are supported; I found no public information on federation or an open protocol. 2 4 5
The Platform Engineer
Custody is genuinely the customer's: an Apache 2.0 server that is 'the same software as our Zulip Cloud customers' get, self-hostable on Ubuntu, Debian, Docker or prebuilt cloud images, with documented setup, backup and upgrade scripts and export and import tools the vendor says let you move freely between cloud and your own servers. Maintaining a fork with customised features is explicitly supported with 225,000 words of administrator and developer documentation. We found no public information on native federation or an open wire protocol — the documented Slack, Teams and Matrix bridges are bridges, not federation — so I hold a point back. 4 5
The Skeptic
The server is 100% open source under Apache 2.0, self-hosting is documented as the same software cloud customers run, and setup, backup and upgrade scripts plus prebuilt images are provided. The exit is documented rather than resisted: import from Slack, Teams, Mattermost and Rocket.Chat, export and import tools to move freely between cloud and own servers, and a static HTML archive of message history. I found no public information on an open federation protocol for the server itself. 2 4 5
Integrations & extensibility
Show reasoningHide 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.
The Team Lead
130-plus native integrations with thousands more through Zapier and IFTTT, a documented REST API, custom webhooks, bridges to Slack, Teams and Matrix, plus SSO and SCIM user and group sync — enough that the chat becomes where work gets noticed, and API endpoint rate limits are stated. I found no public information on an app framework with interactive components or a published API deprecation policy, so I hold it just below the platform tier. 2 4 5
The Security Officer
Over one hundred and thirty native integrations with thousands more via Zapier and IFTTT, a well-documented REST API, custom webhooks, bridges to Slack, Teams and Matrix, and an AI/LLM integration are all documented. Single sign-on and SCIM user and group sync are listed, and API endpoint rate limits are named in the security features. We found no public information on an app framework with interactive components, event subscriptions with retries, or a sandbox for developers. 2 4 5
The Works Council Advocate
130+ native integrations, thousands more through Zapier and IFTTT, a documented REST API with custom webhooks, and chat bridges to Slack, Teams and Matrix make the chat a place work is noticed. SSO and SCIM user and group provisioning plus documented API rate limits are present too. We found no public information on an app framework with interactive components or event subscriptions with retries, so I hold this a step below full. 2 4 5
The Compliance Counsel
Over a hundred native integrations with thousands more via Zapier and IFTTT, a documented REST API, custom webhooks, bridges to Slack, Teams and Matrix, plus SCIM user and group sync and stated API endpoint rate limits. I found no public information on an app framework with interactive components, event subscriptions with retries, or a sandbox, so the extension story reads as integrations and API rather than a governed platform. 2 4 5
The Platform Engineer
A documented REST API, custom webhooks, 130+ native integrations with thousands more via Zapier and IFTTT, chat bridges to Slack, Teams and Matrix, plus SSO, SCIM user and group sync and documented API rate limits. We found no public information on an app framework with interactive components, a sandbox, or a permission model for third-party extensions a customer could audit — extensions are counted on these pages, not governed. 2 4
The Skeptic
Over 130 native integrations with thousands more through Zapier and IFTTT, a well-documented REST API with stated endpoint rate limits, custom webhooks, chat bridges to Slack, Teams and Matrix, and SCIM user and group sync. I found no public information on interactive app components, a developer sandbox, or an API deprecation policy. 2 4 5
European sovereignty
panel opinion
Show reasoningHide 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.
The Team Lead
The contracting entity is Kandra Labs, Inc. in San Francisco and the cloud service is hosted and operated in the United States, with Google and Stripe named as subprocessors. European elements are real — a named EU representative in Cork, a UK representative, GDPR rights, and a self-serve data processing addendum referenced in the policy index — and self-hosting keeps the archive on the customer's own infrastructure, which is the custody answer my team would take. I found no public information on an EU hosting option for the cloud service or on a transfer impact assessment. 3 4
The Security Officer
The contracting entity is Kandra Labs, Inc. of San Francisco and the cloud services are stated to be hosted and operated in the United States through Zulip and its service providers, with Google for analytics and Stripe for payments named as US subprocessors. A European Union representative in Cork and a UK representative are named and GDPR rights are acknowledged, which is the one European element the evidence proves. Self-hosting on the customer's own infrastructure under the permissive licence removes the hosting question; we found no public information on an EU hosting option for the cloud service itself. 3 4 5
The Works Council Advocate
The captured pages show a San Francisco legal entity, cloud services 'hosted and operated in the United States', and named US subprocessors including Google for web analytics — a chain a council will not accept for cloud use. A European Union representative in Cork and a GDPR rights section are proven, which is the European element the pages establish. Self-hosting keeps the archive on our own infrastructure as the practical remedy; we found no public information on the data processing addendum's actual terms, an EU hosting region, or a transfer impact analysis. 3 4
The Compliance Counsel
The cloud service is stated to be hosted and operated in the United States by a San Francisco entity, with Google and Stripe named as processors; the European elements I can prove are a named EU representative in Cork and a data processing addendum offered self-serve, where the captured excerpt shows only the policy index entry. Self-hosting under a permissive licence is the customer's route to keeping archive and metadata in Europe, but I found no public information on an EU hosting option for the cloud chain. 3 4 5
The Platform Engineer
The contracting entity is Kandra Labs, Inc. of San Francisco and the cloud service is 'hosted and operated in the United States', with Google Analytics and Stripe named as service providers; an EU representative in Cork and a UK representative are named, and GDPR rights are laid out. Self-hosting does put the archive on infrastructure the customer chooses, but the vendor and the cloud chain are American and we found no public information on an EU hosting region for the cloud service. One European element proven against a stated US chain — thin comfort for a European archive. 3 4
The Skeptic
The cloud service states it is hosted and operated in the United States, the contracting entity is Kandra Labs, Inc. of San Francisco, and Google and Stripe are named as processing partners; an EU representative in Cork, a UK representative, and GDPR rights are also documented, which is one European element proven with the rest of the chain pointing across the Atlantic. Self-hosting is the one route these pages show to holding the archive on European infrastructure. I found no public information on an EU hosting option for the cloud service, a subprocessor list with locations, or a transfer impact assessment. 3 4
Pricing transparency
Show reasoningHide 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.
The Team Lead
A buyer can mostly compute the invoice from public pages: the Free plan, Standard at $6.67 /user/month billed annually or $8 billed monthly, Plus at $10 /user/month billed annually or $12 billed monthly with a 10-user minimum, and self-hosted Business at $6.67 /user/month billed annually or $8 billed monthly with a 25-user minimum, each with storage and search-history limits listed. LDAP on cloud plans and Enterprise support sit behind "please inquire", services are billed hourly, and I found no public information on VAT treatment or minimum contract term. 2 4
The Security Officer
Per-user prices are public with billing periods and user minimums: Standard at $6.67 /user/month billed annually or $8 billed monthly, Plus at $10 /user/month billed annually or $12 billed monthly, and the self-hosted Business licence at $6.67 /user/month billed annually or $8 billed monthly, alongside storage and search-history limits per plan and a published $20/month first-year discount. However, LDAP sync on paid cloud plans and custom development work are “please inquire” or “billed hourly” without rates. We found no public information on VAT treatment or minimum contract terms. 2 4
The Works Council Advocate
Free, Standard at $6.67 per user per month billed annually or $8 billed monthly, Plus at $10 or $12, and self-hosted Business at $6.67 or $8 with a 25-user minimum are all public, with storage and search-history limits stated per tier — retention policies named as a Standard feature and compliance exports under the self-hosted business plan. That is enough to compute most of an annual invoice from public pages. We found no public information on VAT treatment or minimum terms, and LDAP sync on cloud plans is 'please inquire'. 2 4
The Compliance Counsel
Per-user prices are public with billing period stated — Standard at $6.67 /user/month billed annually or $8 billed monthly, Plus at $10 /user/month billed annually or $12 billed monthly — alongside history and storage limits, user minimums per tier and a priced self-hosted Business licence at $6.67 /user/month billed annually or $8 billed monthly. What the public pages leave open is VAT treatment, the price of the Enterprise support tier, and cloud LDAP sync, which is "Please inquire" on paid cloud plans. 2 4
The Platform Engineer
Every tier is public with the billing period stated — '$6.67 /user/month billed annually or $8 billed monthly' for both the paid cloud plan and the self-hosted business licence, '$10 /user/month billed annually or $12 billed monthly' on Plus — plus storage and search-history limits per plan, minimum user counts, a '$20/month off for the first year!' discount, and sponsorship programmes. Self-hosted licensing is priced, which most vendors keep behind sales. We found no public information on VAT treatment or minimum contract term, and cloud AD/LDAP sync and the hourly-billed consulting services sit behind 'please inquire'. 2 4
The Skeptic
Per-user prices are public for the Free, Standard and Plus cloud plans and the self-hosted Business plan, with monthly and annual billing stated, search-history and storage limits printed, and feature boundaries visible: retention from Standard, SAML SSO in Plus on cloud, while LDAP sync on paid cloud plans says "Please inquire". A "$20/month off for the first year!" discount and sponsorship pricing are also stated. I found no public information on VAT treatment, contract minimum terms, Enterprise plan pricing, or the hourly rates for consulting and training. 2 4
European sovereignty — proven facts
4 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?Statement covers the Zulip Cloud service; self-hosted customers keep their data on their own infrastructure, so the U.S.-server default does not apply to them. |
0/4 pts | 3 Report an error |
| Hosting options | Self-hostable | 1/1 pts | 4 Report an error |
| Open source | Open source (permissive) | 1/1 pts | 5 Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?Only the policy index entry is present in this excerpt; the addendum's text and how it is concluded are not shown. |
1/1 pts | 3 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Zulip
Is Zulip European?
No. whats-best.ai classifies Zulip as Rest of world.
Where does Zulip store data?
Zulip stores customer data outside the EU by default, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention the United States as hosting location, per the vendor’s page captured 16 Nov 2026.
Does Zulip have a free plan?
Yes. Zulip has a free plan, per the vendor’s page captured 16 Nov 2026.
What are the best alternatives to Zulip?
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: Zulip alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Only the policy index entry is present in this excerpt; the addendum's text and how it is concluded are not shown.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Hosting location. Statement covers the Zulip Cloud service; self-hosted customers keep their data on their own infrastructure, so the U.S.-server default does not apply to them.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 3 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 product fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (5)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage zulip.com Checked 16 Nov 2026 Details →
- 2 Pricing zulip.com Checked 16 Nov 2026 Details →
- 3 Privacy policy zulip.com Checked 16 Nov 2026 Details →
- 4 Self-hosting / on-premises installation docs — found from the homepage zulip.com Checked 16 Nov 2026 Details →
- 5 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 Details →