Verify before you commit
Use this page to sanity-check Gotify quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.
Evidence
Assessed
Docs reviewed · Mar 20, 2026
Freshness
Updated 2026-03-20T21:49:41.084921+00:00
Mar 20, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 7.0 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 6.5 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 6.8 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
Docs-backed Built from public docs and product materials.
Test-backed Backed by guided testing or evaluator-run checks.
Runtime-verified Verified from authenticated runtime evidence.
Authentication uses application tokens for message sending and client tokens for subscription. User management is fully internal to the self-hosted instance. Teams deploying Gotify for agent notifications should manage application token rotation and ensure the Gotify server itself is secured appropriately since it is internal notification infrastructure.
Gotify is a self-hosted-only open-source notification server with a REST API for sending messages and WebSocket delivery to subscribers. Unlike ntfy (which has a public cloud option), Gotify requires self-hosting — it is for teams that want completely private notification infrastructure with no external service dependency. For agents in environments where notification payloads may contain sensitive operational data, Gotify on self-controlled infrastructure provides the privacy guarantee.
The REST API covers applications (for sending), clients (for subscribing), messages, and users. Applications have tokens used by senders (agents) to POST messages; clients subscribe via WebSocket to receive them in real time. The app/client model provides a structured permission separation between message senders and receivers. The API is complete for managing the full notification infrastructure programmatically.
Reliability for self-hosted Gotify is entirely the team's operational responsibility. The server is lightweight and runs efficiently on minimal resources — it is commonly deployed on Raspberry Pi or small VMs. Teams should implement appropriate backup and high-availability for their Gotify installation if notification reliability is critical for their operations.
Documentation covers the API and self-hosting setup adequately. The notification delivery model (REST POST for sending, WebSocket for receiving) is clearly explained. Teams choosing Gotify for privacy-first notification infrastructure will find the documentation sufficient for both deployment and integration.
Trust shortcuts
This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.
Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.
Overall tier
6.8 / 10.0
No alternatives captured yet.