Self-host ntfy with Levelrail

Verified

A simple pub-sub push notification service you can send alerts to from any script or app.

  • AuthorbinwiederhierVerified by Levelrail
  • LicenceApache-2.0
  • Memory128 MiB
  • Archarm64
  • Services1

How to self-host ntfy

  1. Pull the images

    One image is pulled on your server.

    Show images
    • binwiederhier/ntfy:v2.11.0
  2. Create the app

    One service starts in a single Compose app, with 2 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    2 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

ntfy requirements

Memory
About 128 MiB
Architectures
amd64 image published, arm64 tested
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Verified. Verified on arm64 with image tag v2.11.0. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then ntfy. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the ntfy docs page.

Deploy ntfy your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy ntfy from the CLI

levelrail-cli templates deploy ntfy --name my-ntfy

Deploy ntfy with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/ntfy/deploy

ntfy configuration

ntfy services

ServiceImagePortsVolumes
ntfy binwiederhier/ntfy:v2.11.0 80 ntfy_cache -> /var/cache/ntfyntfy_data -> /etc/ntfy

ntfy environment variables

VariableServiceValue
NTFY_BEHIND_PROXY ntfy Preset by the template
NTFY_LISTEN_HTTP ntfy Preset by the template

Ports and volumes

Ports
80
Volumes
2 named mounts: ntfy_cache -> /var/cache/ntfy, ntfy_data -> /etc/ntfy

ntfy FAQ

How much memory does ntfy need?

The catalog lists about 128 MiB of memory for ntfy.

Does ntfy run on arm64?

For ntfy, arm64 is tested; amd64 is image published.

What licence is ntfy under?

ntfy is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does ntfy need configuration before it starts?

No. The template fills in its own defaults.

Which ports does ntfy use?

ntfy listens on port 80 inside the stack.

Where does ntfy keep its data?

In named volumes: ntfy_cache mounted at /var/cache/ntfy and ntfy_data mounted at /etc/ntfy.

Can I deploy ntfy on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id ntfy for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image binwiederhier/ntfy:v2.11.0 is what you deploy there.

levelrail-cli templates deploy ntfy --name my-ntfy