---
title: "Deploy ntfy"
description: "An open-source, self-hostable push notification service."
category: "Queues"
url: https://railway.com/deploy/ntfysh
---

# Deploy ntfy

An open-source, self-hostable push notification service.

**[Deploy ntfy on Railway](https://railway.com/template/ntfysh)**

- **Creator:** alphasec
- **Category:** Queues
- **Total deploys:** 11

## Template content

### ntfy

- **Image:** binwiederhier/ntfy
- **Start command:** `ntfy serve`
- **Health check:** /v1/health
- **Public domain:** Yes

## Documentation

# Deploy and Host ntfy on Railway

ntfy is an open-source, self-hostable push notification service that lets you send notifications to your phone or desktop via simple HTTP requests — no app registration, no vendor lock-in, no API keys required. Publish from any script, app, or CI pipeline in seconds.

## About Hosting ntfy

Hosting your own ntfy server gives you full control over who can publish and subscribe to topics, how long messages are cached, and where attachments are stored. This Railway template deploys ntfy using the official Docker image with a persistent volume mounted at /var/lib/ntfy for cache, auth, and attachment storage — so your data survives restarts and redeploys. The server runs behind Railway's built-in proxy with behind-proxy enabled and is reachable immediately on your Railway-provided domain. From there you can lock down access with user authentication, set message retention policies, and add a custom domain.

## Common Use Cases

- **Developer alerting** — trigger notifications from CI/CD pipelines, cron jobs, or monitoring scripts when builds fail, jobs complete, or thresholds are breached
- **Home automation** — receive push alerts from self-hosted tools like Home Assistant, Uptime Kuma, or Grafana without routing through third-party notification services
- **Team / app notifications** — send internal alerts to teammates or end users from your own backend, with full control over rate limits, topic access, and data retention

## Dependencies for ntfy Hosting

- [ntfy Docker image](https://hub.docker.com/r/binwiederhier/ntfy) (`binwiederhier/ntfy`)
- Persistent volume at `/var/lib/ntfy` (provisioned automatically by this template)

### Deployment Dependencies
 
- [ntfy documentation](https://docs.ntfy.sh/)
- [ntfy server config reference](https://docs.ntfy.sh/config/#config-options)
- [ntfy access control (users & tokens)](https://docs.ntfy.sh/config/#access-control)

### Implementation Details

- [Self-Host Your Own Push Notification Server with ntfy.sh](http://alphasec.io/self-host-your-own-push-notification-server-with-ntfy-sh)

## Why Deploy ntfy on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying ntfy on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

## Similar templates

- [smoothmq](https://railway.com/deploy/AJv-64) — A drop-in replacement for AWS SQS
- [Kafka UI](https://railway.com/deploy/kafka-ui) — Kafbat UI — Open-source web UI to monitor and manage Apache Kafka clusters
- [Hatchet Lite](https://railway.com/deploy/hatchet-lite) — Hatchet Lite with postgres

Open this page in a browser: https://railway.com/deploy/ntfysh