This repository will be archived and marked as read-only on September 1, 2025. After this date, no further changes, issues, or pull requests will be accepted.
Since the first commit on February 10, 2020, Dispatch has grown into a sophisticated incident and signal management platform, thanks to the dedication and passion of its community. We are deeply grateful to the 80 contributors who have shared their time, expertise, and creativity over the years. Your support has made Dispatch what it is today.
- The codebase will remain publicly available in a read-only state.
- No new issues, pull requests, or discussions will be accepted.
- Existing issues and pull requests will be closed.
- We encourage users to fork the repository if they wish to continue development independently.
Thank you again to everyone who has contributed, used, or supported Dispatch over the years!
— The Dispatch Team at Netflix
Put simply, Dispatch is:
All of the ad-hoc things you’re doing to manage incidents today, done for you, and a bunch of other things you should've been doing, but have not had the time!
Dispatch helps us effectively manage security incidents by deeply integrating with existing tools used throughout an organization (Slack, GSuite, Jira, etc.,) Dispatch is able to leverage the existing familiarity of these tools to provide orchestration instead of introducing another tool.
This means you can let Dispatch focus on creating resources, assembling participants, sending out notifications, tracking tasks, and assisting with post-incident reviews; allowing you to focus on actually fixing the issue!
