# Bitcaster – Self-hosted notification system (looking for feedback) **URL:** \ **Category:** Show & Tell\ **Created:** [May 4, 2026, 10:32am UTC](https://forum.djangoproject.com/t/bitcaster-self-hosted-notification-system-looking-for-feedback/45050 "2026-05-04T10:32:24Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![MoniqueDarby](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/moniquedarby/32/32351_2.png) [@MoniqueDarby](https://forum.djangoproject.com/u/MoniqueDarby)\ **Post date:** [May 4, 2026, 10:32am UTC](https://forum.djangoproject.com/t/bitcaster-self-hosted-notification-system-looking-for-feedback/45050/1 "2026-05-04T10:32:24Z")
Hi everyone! I’ve been working on Bitcaster, an open-source system-to-user notification platform, and I’d love to get some feedback from the community. What it does: Bitcaster receives signals from your applications via a simple REST API and converts them into messages delivered across a wide range of channels: Email (SMTP/Gmail/Mailgun/Mailjet/SendGrid), Slack, Microsoft Teams, Twilio (SMS), and more. Key features: - User can be notified through multiple channels - Flexible template system with per-user/receiver customization - Distribution lists and notification policies - Built with Django + DRF, Python 3.13 - Docker support for easy deployment - SSO support (via django-allauth) - Rate-limited REST API Why I built it: I needed a self-hosted alternative to services like PagerDuty/OpsGenie for notification routing, where users could manage their own delivery preferences without admin intervention. Links: - GitHub: [GitHub - bitcaster-io/bitcaster: System-to-user signal-to-message notification system. · GitHub](https://github.com/bitcaster-io/bitcaster) - Docs: [Documentation - Bitcaster](https://bitcaster-io.github.io/bitcaster/) - Website: [https://www.bitcaster.io/](https://www.bitcaster.io/) It’s still evolving, so any feedback, feature suggestions or collaboration, would be greatly appreciated!