zulip/zulip

Zulip server and web application. Open-source team chat that helps teams stay productive and focused.

View on GitHub ↗Jump to charts ↓Open shareable report →

zulip/zulip has 26k+ stars and 10k+ forks on GitHub, is written in Python, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 51 minutes ago
Added to GitGenius on September 2nd, 2026
Created on September 25th, 2015
Open Issues & Pull Requests: 2,051 (+0)
GitHub issues: Enabled
Number of forks: 10,418
Total Stargazers: 26,055 (+0)
Total Subscribers: 362 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.6 hours
Mean response time: 113.3 days
90th percentile: 136.7 days
Tracked items: 2,854

Maintainer activity

620 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 6% of issues opened in the past year have never received a reply. 66% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "area: popovers and tooltips" is answered fastest, typically in about 5 hours, while "feedback wanted" waits about 2 days. 51% of tracked open issues have had no activity in three months. Only 56% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 871
New in 7 days: 4
Closed in 7 days: 6
Avg open age: 1,235 days
Stale 30+ days: 707
Stale 90+ days: 473

Recent activity

Opened in 7 days: 4
Closed in 7 days: 6
Comments in 7 days: 24
Events in 7 days: 101

Top labels

  • help wanted (950)
  • bug (757)
  • in progress (681)
  • priority: high (568)
  • area: left sidebar (334)
  • new feature (317)
  • feedback wanted (237)
  • area: settings (admin/org) (154)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Zulip is an open-source team chat application that organizes conversations through topic-based threading rather than linear channels.

The core problem Zulip addresses is that traditional chat platforms like Slack optimize for synchronous, real-time conversation but struggle with asynchronous communication and information discovery. Zulip's topic-based threading model combines email-like organization with chat immediacy, allowing teams to maintain focused conversations within streams while keeping discussions discoverable and easy to follow across time zones. This design makes it possible for remote teams to work productively without requiring constant real-time presence.

Zulip suits organizations that value asynchronous work, need strong searchability and conversation history, or want to self-host their infrastructure. The project offers multiple deployment paths: self-hosting on Ubuntu or Debian, Docker containers, or managed cloud hosting. Teams already invested in Slack-like workflows should understand that Zulip's threading model represents a different conversation paradigm rather than a direct replacement. The tool is particularly valuable for distributed teams, open-source projects, and organizations that cannot use proprietary SaaS platforms.

The project maintains a large, active contributor base with sustained development momentum. The codebase emphasizes readability and testability, supported by extensive contributor documentation. The project actively welcomes contributions across code, translations, bug reports, and feature feedback, with participation in formal outreach programs. Development occurs transparently in the open-source community, with a dedicated development chat where contributors collaborate.