Self-host ntfy for your own alerts and scripts.
ntfy is a lightweight push notification server for personal automation, cron jobs, deploy alerts and admin workflows. VibeNest launches a prepared adapter on your own subdomain with free SSL.
Alerts you control
Send notifications from scripts, servers and internal tools without relying on a shared public relay.
VibeNest-ready adapter
The adapter uses the official ntfy image, port 80, persistent cache/auth storage and Docker-friendly environment config.
Private by default
Anonymous access is denied by default. Create users and set the final base URL before using private topics.
Deploy ntfy in one click
- 1. Launch the adapter VibeNest opens the deploy flow with the ntfy adapter repo and branch pre-filled.
- 2. Confirm hardware Use a free or paid server slot so ntfy has RAM, CPU and persistent storage.
- 3. Finish setup Set
NTFY_BASE_URLto your VibeNest subdomain and create ntfy users before publishing private topics.
Push notifications for scripts and self-hosted services
ntfy turns a simple HTTP PUT or POST into a notification. Shell scripts, backup jobs, monitoring checks and home automation can publish to a topic, while the web or mobile client subscribes to it. There is no vendor-specific SDK required for the basic workflow.
A self-hosted notification server is valuable when topic names, access rules and delivery history belong to your infrastructure. The VibeNest recipe starts from deny-by-default access so a guessed topic cannot become an anonymous public relay.
Create users before publishing
Set the final base URL, create an administrator and scoped publishing users, then grant topic permissions deliberately. Test one private notification before connecting production scripts. Keep the auth database and cache volume persistent across upgrades.
Source, VibeNest recipe and live proof
Original open-source project
Review the upstream source, release notes and Apache-2.0/GPL-2.0 license before you deploy or update the app.
Original GitHubVibeNest-ready recipe
VibeNest adapter uses the official ntfy image, port 80, a persistent cache/auth volume and deny-by-default auth settings via NTFY_* environment variables.
Deploy repositoryPublic deployment proof
Public URL returned HTTP 200 and opened the real ntfy web UI.
Open live deploymentFrequently asked questions
Is ntfy open source? +
Yes. ntfy is open-source software. VibeNest launches it through a small adapter that keeps the upstream project intact and adds deploy-safe defaults.
Why should I run my own ntfy instance? +
Push topics can include operational signals and private automation events. Your own instance gives you isolated auth, rate limits and storage.
Does ntfy fit the free tier? +
The adapter passed a VibeNest free-tier smoke deploy. Very high message volume may need a paid hardware slot.
Does it need persistent storage? +
Yes. The adapter keeps ntfy cache and auth data on a persistent volume so users and message cache survive redeploys.
What was fixed for VibeNest? +
The adapter uses environment-based ntfy config instead of a bind-mounted server.yml, then passed a fresh compose deploy with the public URL opening ntfy web.
Deploy your personal notification server
Start with a tested ntfy adapter, then wire your scripts and admin alerts to your own VibeNest subdomain.
Deploy ntfy