Zulip is an open source real-time chat application like Slack, but with an email-like threading model. The email threading model allows you to catch up on important conversations while ignoring irrelevant ones. Zulip’s features include:
- Highly configurable notifications.
- Keyboard shortcuts.
- Mobile and desktop apps.
- Integrations with Trac, Nagios, GitHub, and more.
- Restful API with Python bindings.
- and more!
Use the button below to deploy Zulip on Render.
It uses the github.com/render-examples/zulip repository to create the following components on Render:
- Zulip web/application server: contains Nginx, Django, Tornado, and Supervisor.
- Memcached instance: used to cache database model objects.
- Redis instance: used for short-term data stores.
- RabbitMQ instance: used as a queuing system and to communicate between Django and Tornado.
- PostgreSQL instance: used to store all persistent data.
More details on Zulip’s architecture here.
The 1-click button launches the following components on Render:
|Cost per month
|4 of up to 10 GB each
|< $10 ($0.25 per GB used)
|$53-$63 per month for unlimited members!
Zulip recommends deploying the main application/webserver with more than 2 GB RAM (ideally 4). The Standard instance type gives you 2 GB of RAM, but we recommend upgrading to the Pro instance type for production use. Zulip has documentation on how resource needs scale with the number of users on the app.
You only need one environment variable to test your Zulip install:
|email address of the Zulip administrator
You will be able to set up your account and use all of Zulip’s features as a single user. Inviting other users to join your realm (Zulip’s term for organization) requires setting up email-related environment variables, which are explained below.
zulip service is deployed and live, navigate to the
Shell tab and type in:
Visit the link generated by the command and create your Zulip administrator account with the email you used for
Zulip requires a mail server to send emails to users. Reliable mail delivery requires more work than just running the mail server, so we strongly recommend using a third-party email provider.
These are the environment variables you will need to set for production use:
|hostname your users will use to connect to your Zulip server; leave empty to use onrender.com domain
|address of your SMTP provider (ex. smtp.mailgun.org)
|your SMTP provider username (ex. firstname.lastname@example.org)
|your SMTP provider password
|port your SMTP provider uses to connect (ex. 587)
SETTING_EMAIL_PORT is using SSL;
SETTING_EMAIL_PORT is using TLS;
Other environment variables you might change:
False sets Zulip to run in multithreaded mode, which is ideal for lower memory instances. Set to
True if Zulip is run in a Pro instance or larger
EmailAuthBackend supports email and password authentication, but Zulip also supports other authentication methods