Gem devopsgo

Gotify

A simple self-hosted server for sending and receiving push notifications.

Would you recommend Gotify?

No votes yet. Tried it? Be the first to say.

One vote per person. No account needed.

Overview

Gotify lets you send messages through a REST API and receive them in real time over WebSocket, with a web UI, a CLI and an Android app. It is a tiny Go server that is easy to self-host, so scripts, cron jobs and CI pipelines can ping your phone without a third-party push service.

Instead of

Paid push services, Telegram bots or emailing yourself from scripts

Reach for it when

You want a backup job, deploy or long-running script to notify your phone when it finishes or fails.

Key features

  • Send with one request

    POST a message to the REST API with an application token, from any script, cron job or CI pipeline.

  • Real-time delivery

    Clients receive messages instantly over WebSocket.

  • Apps and clients

    Separate tokens for sending applications and receiving clients, with per-app icons and priorities.

  • Android app and web UI

    Notifications on your phone (Google Play or F-Droid) and in the browser.

  • CLI

    gotify push sends messages from the command line with stored config.

  • Extras

    Markdown messages, click URLs, and a Go plugin system for custom behaviour.

In depth

Running it

bash
docker run -d --name gotify -p 8080:80 -v gotify-data:/app/data gotify/server

Open the web UI (the default login is admin/admin, so change it immediately), create an Application, and copy its token.

Sending notifications

bash
curl "http://localhost:8080/message?token=<apptoken>" \
  -F "title=Backup finished" \
  -F "message=Nightly backup completed in 4m12s" \
  -F "priority=5"

From a cron job, notify only on failure:

bash
0 3 * * * /usr/local/bin/backup.sh || curl -s "https://gotify.example.com/message?token=<apptoken>" -F "title=Backup FAILED" -F "message=Check the server logs" -F "priority=8"

Markdown formatting is enabled by sending JSON with "extras": {"client::display": {"contentType": "text/markdown"}}.

Good to know

  • Put it behind your reverse proxy (Caddy, Traefik or nginx) with HTTPS, and make sure WebSocket upgrades are passed through.
  • Priorities control how loudly the Android app notifies you, so use high values only for genuinely urgent alerts.

Strengths

  • Self-hosted and private: your notifications don't pass through a third-party service.
  • Tiny and simple to run: one Go binary or container, with SQLite by default.
  • Sending is a single curl, so anything can notify you.
  • A mature project (since 2018) that does one job well.

Watch out for

  • There's no official iOS app; iOS users usually prefer ntfy or Pushover.
  • The Android app keeps a persistent connection to your server, so the server must be reachable from your phone.
  • Protect the web UI and API with HTTPS and strong passwords if it's exposed to the internet.

Try it in a few minutes

Terminal
docker run -p 80:80 -v /var/gotify/data:/app/data gotify/server
# create an application in the web UI to get a token, then:
curl "http://localhost/message?token=<apptoken>" -F "title=Backup" -F "message=Nightly backup finished"

Alternatives

ntfy

Topic-based push over plain HTTP, with Android and iOS apps; self-hostable or hosted.

Pushover

A paid hosted service with polished apps on every platform.

Apprise

A library and CLI that sends to dozens of notification services through one interface.

Telegram / Slack webhooks

Use a chat app you already have, but your messages go through their servers.

Related tools

Other tools that share topics with Gotify.

LibreTranslate

libretranslate.com
Gem

A free, open-source machine translation API you can host yourself.

Instead of Google Translate, DeepL or Azure Translator APIs

Testcontainers

testcontainers.com
Gem

Spin up real databases and services in Docker from inside your tests.

Instead of Mocked database layers, shared test databases, hand-written docker-compose setup

act

nektosact.com
Gem

Run your GitHub Actions workflows locally in Docker.

Instead of "fix ci" commit after "fix ci" commit