Service
Trigv — "real-time events, instant alerts for developers." Single HTTP POST delivers native push alerts to phone/desktop when your stack needs attention. Notification content stays on-device; Trigv's servers only keep metadata (timestamps, delivery status, usage counts). Backed by Firebase (push delivery) and Pusher (dashboard realtime) — it's a managed service, not self-hostable itself, but it's a current favorite target for self-hosted stacks to alert through.
Why now
One of the newest (2026) developer-alerting services gaining traction alongside ntfy/Gotify/Pushover in this space.
Apprise comparison
Not supported by Apprise. No Trigv plugin in Apprise's service catalog as of this writing.
Proposed scope
Mirror providers/pushover or providers/ntfy shape:
providers/trigv packageConfig{ APIKey, ... } (confirm exact auth/payload shape against current Trigv API docs before implementing)New(cfg, wrapper) *Client, (*Client).Send(ctx, notify.Message) error via transport.Wrapper
Note
Per CLAUDE.md, this repo's near-term policy is to keep the provider list to what's ported from Charon and not add new integrations without an explicit go-ahead. This issue is tracking/backlog only — do not implement without maintainer sign-off.
Service
Trigv — "real-time events, instant alerts for developers." Single HTTP POST delivers native push alerts to phone/desktop when your stack needs attention. Notification content stays on-device; Trigv's servers only keep metadata (timestamps, delivery status, usage counts). Backed by Firebase (push delivery) and Pusher (dashboard realtime) — it's a managed service, not self-hostable itself, but it's a current favorite target for self-hosted stacks to alert through.
Why now
One of the newest (2026) developer-alerting services gaining traction alongside ntfy/Gotify/Pushover in this space.
Apprise comparison
Not supported by Apprise. No Trigv plugin in Apprise's service catalog as of this writing.
Proposed scope
Mirror
providers/pushoverorproviders/ntfyshape:providers/trigvpackageConfig{ APIKey, ... }(confirm exact auth/payload shape against current Trigv API docs before implementing)New(cfg, wrapper) *Client,(*Client).Send(ctx, notify.Message) errorviatransport.WrapperNote
Per
CLAUDE.md, this repo's near-term policy is to keep the provider list to what's ported from Charon and not add new integrations without an explicit go-ahead. This issue is tracking/backlog only — do not implement without maintainer sign-off.