English
Gotify Hosting
Deliver real-time push notifications to browsers and mobile devices through a simple API.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Gotify’s official links and original website
Gotify Website
More
Tech
- Docker image
- gotify/server:latest
- Default port
- 80
How Gotify works
Gotify separates message senders from message receivers. An administrator creates an application inside the server and receives a token for that sender. A script, monitoring tool, or supported integration submits a message through the REST API, while browsers and compatible clients subscribe to the authenticated user account and receive updates through the server.
Applications are the sending identities, clients are the receiving connections, and users own the associated applications, messages, and clients. The application token must be treated as a credential because anyone holding it can submit messages for that application. Current Gotify guidance also warns that newly generated application tokens may only be displayed once, so they should be copied into a secure store at creation time.
Key Gotify features
The web interface keeps recent notifications available for review and lets administrators organise sending applications. Priorities, titles, message bodies, and optional extras can help receiving clients present different kinds of alerts. The server is a notification relay rather than a monitoring engine, so it does not collect metrics, test services, or decide when an alert should fire unless an external sender performs that work.
The catalogue generates an administrator password and persists the Gotify data directory. External monitoring tools, scripts, mobile clients, reverse integrations, and their API credentials are not supplied. Application email is disabled across hosted services, although Gotify itself is intended for push-style delivery rather than mail.
Who uses Gotify
Infrastructure teams send build results, backup outcomes, health-check failures, and deployment events to a private notification endpoint. Developers use it for test environments and internal tools, while individuals consolidate homelab alerts into one account instead of configuring a separate mail sender for each service.
Gotify is less suitable when recipients need SMS, telephone escalation, a provider-operated mobile network, compliance archiving, or a full incident-management workflow. Delivery still depends on the receiving client, its notification permissions, network connectivity, and the external source that creates the message.
Self-hosting Gotify: requirements and cost
Gotify resource use grows with user count, connected clients, incoming message rate, retained history, message size, and WebSocket activity. Its catalogue stack does not provision PostgreSQL or MariaDB; message history and settings remain in Gotify’s persistent data volume. A modest notification stream fits the entry plan, while unusually high retention or many continuously connected clients can justify a later review.
On AvaHost, Gotify uses Plan 1 at €2. The hosted Gotify package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The plan does not include monitoring checks, mobile-device management, SMS delivery, third-party client software, or sender integrations. Protect administrator and application tokens, retain newly generated tokens when they are shown, and test each external sender with non-sensitive messages before relying on it for operational alerts.
F.A.Q
Gotify starts at €2 on Plan 1. The entry plan suits a small notification service with ordinary message retention and a limited number of connected clients. Incoming rate, stored history, message size, user accounts, application count, and persistent WebSocket connections are the main signals for reviewing capacity later.
Create an application inside Gotify and copy its application token into the trusted script or integration that will send messages. Treat that token as a password because it authorises submissions for the application. Current Gotify versions may show a new token only once, so store it securely and rotate it if exposure is suspected.
A custom domain can point to the Gotify installation, and automated HTTPS protects browser and API connections to that address. Update sender URLs and compatible clients after DNS is active. The certificate secures transport to the server, but administrators must still protect account passwords, application tokens, and every external system permitted to submit notifications.
Gotify accepts and distributes messages, but it does not create monitoring checks, provide SMS delivery, manage phones, or include third-party sender and client applications. Customers configure their own permitted scripts, monitoring tools, and clients. AvaHost applies application updates automatically and includes scheduled backups for the persistent Gotify data directory.