Some checks failed
Code scanning / CodeQL (push) Failing after 15s
Zulip production suite / Ubuntu 22.04 production build (push) Failing after 26s
Zulip production suite / Debian 12 production install with custom db name and user (push) Has been skipped
Zulip production suite / Ubuntu 22.04 production install and PostgreSQL upgrade with pgroonga (push) Has been skipped
Zulip production suite / Ubuntu 24.04 production install (push) Has been skipped
Zulip production suite / Ubuntu 26.04 production install (push) Has been skipped
Zulip production suite / Debian 13 production install (push) Has been skipped
Zulip production suite / 7.0 Version Upgrade (push) Has been skipped
Zulip production suite / 8.0 Version Upgrade (push) Has been skipped
Zulip production suite / 6.0 Version Upgrade (push) Has been skipped
Zulip production suite / 10.0 Version Upgrade (push) Has been skipped
Zulip production suite / 9.0 Version Upgrade (push) Has been skipped
Zulip production suite / 12.0 Version Upgrade (push) Has been skipped
Zulip production suite / 11.0 Version Upgrade (push) Has been skipped
GitHub Actions Security Analysis with zizmor / zizmor (push) Failing after 3s
Zulip CI / Debian 12 (Python 3.11, backend + documentation) (push) Failing after 26s
Zulip CI / Ubuntu 22.04 (Python 3.10, backend + frontend) (push) Failing after 3s
Zulip CI / Ubuntu 24.04 (Python 3.12, backend) (push) Failing after 25s
Zulip CI / Ubuntu 26.04 (Python 3.14, backend) (push) Failing after 25s
Zulip CI / Debian 13 (Python 3.13, backend) (push) Failing after 28s
Zulip production suite / Required jobs (push) Has been cancelled
Zulip CI / Required jobs (push) Has been cancelled
API Documentation Update Check / check-feature-level-updated (push) Has been cancelled
API Documentation Update Check / notify-if-api-docs-changed (push) Has been cancelled
93 lines
4.7 KiB
Markdown
93 lines
4.7 KiB
Markdown
## Building software that will always be there for our users
|
||
|
||
When choosing software that will be core to how one’s organization operates,
|
||
such as a team chat platform, there is an important question: “Will this product
|
||
still exist and be responsibly maintained in a few years?”
|
||
|
||
We have designed our governance, community, and technology with the explicit
|
||
goal of Zulip being actively developed for many years to come. This theme cuts
|
||
across many of the decisions described below. It is also reflected in our
|
||
[history](/history/): Zulip's [earliest
|
||
customers](/case-studies/recurse-center/) have enjoyed uninterrupted service
|
||
since 2013.
|
||
|
||
**We’re building software that is easy to maintain,** so it does
|
||
not require a large team to keep the lights on. We have consistently emphasized
|
||
high standards for codebase readability, code review, commit discipline,
|
||
debuggability, automated testing, tooling, documentation, and all the other
|
||
subtle details that together determine whether software is easy to understand,
|
||
operate, and modify.
|
||
|
||
## Commitment to the mission
|
||
|
||
Zulip is stewarded by the [Zulip
|
||
Foundation](https://blog.zulip.com/2026/05/15/announcing-zulip-foundation/),
|
||
with a mission of developing the best possible team chat experience, with a
|
||
particular focus on public-interest organizations and communities. The Zulip
|
||
Foundation fully owns Kandra Labs, the company responsible for hosting,
|
||
supporting, and improving Zulip for use across all industries.
|
||
|
||
This structure, announced in May 2026, formalizes our [longtime
|
||
commitment](https://blog.zulip.com/2021/12/17/why-zulip-will-stand-the-test-of-time/)
|
||
to Zulip’s sustainability and independence. It allows us to fairly compensate a
|
||
talented, dedicated team of core developers, without taking outside investment
|
||
that could put pressure on us to compromise our values.
|
||
|
||
## Doing right by our users
|
||
|
||
We’re fully committed to being a trustworthy, transparent vendor for our
|
||
customers. Kandra Labs has been public about its values for years — including
|
||
our commitments to [protecting customer data
|
||
privacy](https://blog.zulip.com/2024/05/23/self-hosting-keeps-your-private-data-out-of-ai-models/#a-note-on-zulips-approach-to-data-privacy),
|
||
and to keeping our focus on the product, not on whatever’s [commercially
|
||
fashionable](https://blog.zulip.com/2021/11/12/why-not-blockchain/).
|
||
|
||
## Keeping Zulip 100% open source
|
||
|
||
Many modern “open-source” companies use a version of their product with some
|
||
basic functionality intentionally removed as a demo for their non-open-source
|
||
paid product. In contrast, we are committed to keeping Zulip [100% open
|
||
source](https://github.com/zulip/zulip#readme).
|
||
|
||
When you [self-host Zulip](/self-hosting/), you get all the
|
||
[features](/features/) of our cloud offering. We work hard to [make it
|
||
easy](https://zulip.readthedocs.io/en/latest/production/install.html) to set up
|
||
and run a self-hosted Zulip installation without paying us a dime, which is why
|
||
thousands of organizations do so.
|
||
|
||
## Investing in community and mentorship
|
||
|
||
Zulip is developed by a [vibrant open-source community](/team/), and we are
|
||
fully committed to helping bring up the next generation of open-source
|
||
contributors from a wide range of backgrounds.
|
||
|
||
We have invested into making Zulip’s code uniquely readable, well tested, and
|
||
easy to modify. Beyond that, we have written an extraordinary 185K words of
|
||
documentation on [how to contribute to
|
||
Zulip](https://zulip.readthedocs.io/en/latest/overview/contributing.html), with
|
||
topics ranging from [practical Git
|
||
tips](https://zulip.readthedocs.io/en/latest/git/index.html) to [essays on
|
||
important architectural
|
||
decisions](https://zulip.readthedocs.io/en/latest/subsystems/events-system.html).
|
||
|
||
We also welcome and support contributors via [formal internship
|
||
programs](https://zulip.readthedocs.io/en/latest/outreach/overview.html), with
|
||
over 100 participants since 2016. Because of the thousands of hours our more
|
||
senior contributors (including alumni of these programs!) have dedicated to
|
||
mentorship, many of these participants have told us that they learned more
|
||
contributing to Zulip than in their 4-year formal computer science education.
|
||
|
||
## Supporting other worthy organizations
|
||
|
||
An important part of Zulip’s mission is ensuring that worthy organizations, from
|
||
[programming-language developers](/case-studies/rust/) to [research
|
||
communities](/case-studies/lean/), are able to use Zulip whether or not they
|
||
have funding.
|
||
|
||
We sponsor [Zulip Cloud Standard](/plans/) hosting for [open-source
|
||
projects](/for/open-source/), [research groups](/for/research/),
|
||
[education](/for/education/), [non-profits](/for/communities/) and other
|
||
[communities](/for/communities/). This program has grown exponentially since its
|
||
inception; today we are proud to fully sponsor Zulip hosting for hundreds of
|
||
organizations.
|