Publish alerts to an ntfy topic, either on ntfy.sh or on a server you run. For teams who would rather not route operational alerts through a third-party service, this keeps the delivery path on infrastructure you control.
Most push services require trusting someone else with your operational alerts. ntfy is the option that does not.
Running your own ntfy server means alerts never traverse a third-party service you do not control.
Topic-based delivery means there is no per-user account management to maintain alongside your team list.
Anyone who needs the alerts subscribes to the topic from their own device without you provisioning anything.
If you are already running your own infrastructure, ntfy tends to fit the way you work better than a commercial push service.
On a public instance, anyone who knows the topic name can subscribe to it. Choose something unguessable, or self-host.
Like any push notification, delivery depends on a data connection. Keep SMS or a phone call for the critical path.
Point ntfy at your own server, subscribe to the topic, and wire it into a flow.