Github Ntfy
Self-HostedOpen-source GitHub event notifications via ntfy
Overview
A self-hosted tool that bridges GitHub webhooks to ntfy, delivering real-time alerts for repo events (pushes, PRs, issues, releases) to your ntfy topics. Deployable via Docker or standalone binary, it supports custom event filtering, topic mapping, and secure webhook signature verification. Ideal for teams/individuals wanting privacy-focused GitHub notifications without relying on third-party SaaS.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
github_ntfy:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: github-ntfy
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Real-time alerts for GitHub events (pushes, PRs, issues)
- Custom event filtering and ntfy topic mapping
- Easy deployment via Docker or standalone binary
- Secure webhook signature verification
Frequently Asked Questions
? Is Github Ntfy hard to install?
No—It deploys quickly via Docker (simple run command) or standalone binary. You just need to set up a GitHub repo webhook pointing to the service and configure ntfy topic mappings.
? Is it a good alternative to Zapier for GitHub notifications?
Yes—If you prefer self-hosted, cost-free tools with privacy. Unlike Zapier (SaaS), it keeps data in your control but lacks Zapier’s wide third-party integrations.
? Is it completely free?
Yes—Github Ntfy is open-source under MIT License, so it’s free to use, modify, and self-host without any charges.
Top Alternatives
People Also Ask about Github Ntfy
Tool Info
Pros
- ⊕ Privacy-focused (self-hosted data control)
- ⊕ No subscription fees
- ⊕ Flexible event customization
- ⊕ Seamless ntfy integration
Cons
- ⊖ Requires a ntfy instance (self-hosted or public)
- ⊖ Technical setup (webhook config in GitHub)
- ⊖ Limited to ntfy notifications (no other channels out of box)