Zulip — Threaded Team Chat That Actually Scales to Thousands of Topics

What it is

Zulip is a team chat platform built around threaded topic conversations. Every message belongs to a topic (like an email subject line), so instead of a single chronological channel scroll, Zulip channels have multiple active topics, each with its own threaded history.

Zulip targets teams and open-source communities where async communication matters. Its topic-first model scales to thousands of active discussions where Slack or Discord would devolve into noise. It is used by Wikimedia, the Rust project, Lean, and Recurse Center.

How it saves time or tokens

Zulip's topic model eliminates the cost of catching up on missed conversations. In Slack, you scroll through interleaved messages from multiple discussions. In Zulip, you read each topic independently, skip irrelevant ones, and mark them as read. The catch-up workflow is fundamentally faster. Full-text search across all topics and streams means finding past decisions takes seconds. Email gateways let team members participate without opening the app.

How to use

1. Deploy Zulip with Docker Compose:

git clone https://github.com/zulip/docker-zulip.git
cd docker-zulip
# Edit docker-compose.yml: set SETTING_EXTERNAL_HOST and secrets
docker compose up -d

1. Visit your Zulip instance and create the first organization and admin account through the web UI.

1. Create streams (channels) and start conversations with topics. Every message you send requires a topic, which keeps discussions organized from day one.

Example

Zulip's topic-based organization compared to Slack's flat channels:

# Slack channel: #engineering
10:01 Alice: Anyone reviewed the auth PR?
10:02 Bob: The deploy to staging failed again
10:03 Alice: PR #342 needs security review
10:04 Carol: What error on staging?
10:05 Bob: Connection timeout to the DB
# All interleaved, hard to follow

# Zulip stream: engineering
# Topic: auth PR review
  Alice: Anyone reviewed the auth PR?
  Alice: PR #342 needs security review
  Dan: Reviewed, LGTM with one nit on line 45

# Topic: staging deploy failure
  Bob: The deploy to staging failed again
  Carol: What error on staging?
  Bob: Connection timeout to the DB
  Carol: Checking the DB connection pool now
# Each topic is a separate, followable thread

Related on TokRepo

• Self-hosted tools — Browse more self-hostable communication and infrastructure tools.
• Featured workflows — Discover curated tools and frameworks on TokRepo.

Common pitfalls

• Not enforcing topic usage from the start leads to messy 'no topic' messages. Configure Zulip to require topics on all messages in your organization settings.
• Migrating from Slack without a topic convention confuses new users. Publish a short guide on how to name topics (e.g., 'verb + noun: review auth PR').
• Running Zulip on a server with less than 2GB RAM causes poor performance. The recommended minimum is 4GB for teams of 50+ users.