Gotify
Private push notification server, ready to run as a private service.
| Setting | Value |
|---|---|
| Image | gotify/server:2 |
| Port | 8080 (HTTP, private) |
| Storage | Volume at /app/data |
| Minimum size | 0.5 vCPU · 512 MiB |
Create it
In your project, choose Create, then Gotify from the templates. Raseef creates the service with the settings below, generates its secrets and deploys it. Its data lives on its own volume.
Connect from your app
Gotify is a private service: it has no public address. Other services in the same environment reach it on its private address and port, which Raseef offers as variables you can reference.
Reference its address and port from your app, using the name you gave the service (here gotify):
GOTIFY_HOST=${{ gotify.RASEEF_PRIVATE_DOMAIN }}
GOTIFY_PORT=${{ gotify.RASEEF_PRIVATE_PORT }}Its credentials are generated when the service is created (see below). Reference them the same way, for example
${{ gotify.GOTIFY_DEFAULTUSER_PASS }}.
See Variables for how references work.
Variables
Generated once, when the service is created, and stored encrypted:
| Variable | Value |
|---|---|
GOTIFY_DEFAULTUSER_PASS | A random password, 64 hex characters |
Set by the template:
| Variable | Value |
|---|---|
GOTIFY_SERVER_PORT | 8080 |
GOTIFY_DEFAULTUSER_NAME | raseef |
Every variable of a template service is managed by Raseef and cannot be edited. The workspace owner can reveal the secrets from the service panel; each reveal is recorded in the audit log.
Data and backups
The data directory /app/data is a persistent volume: it survives restarts and deploys. A service with a
volume runs a single replica, and a deploy stops the old replica before starting the new one, so expect a short
interruption. See Volumes for sizes and backups.
Version
The service runs gotify/server:2, pinned by digest when the service is created and kept on that
exact image afterwards. Template catalog version 2026-10-19.1.
Upstream documentation: gotify/server.