Story seems pretty much the same with Web push notifications. You send a json to the temporary url provided by the browser push api. 1. From client get a push

Story seems pretty much the same with Web push notifications. You send a json to the temporary url provided by the browser push api. 1. From client get a push url. 2. Pass that to your app server for future use. 3. Send notification json to that url. 4. That url points to the specific browser vendor's Push notification server, and when it recieves a notification from your app server. It relays the message to the client. And that url is different for different browsers. Firefox - https://mozilla-push-service.readthedocs.io/en/latest/ https://mozilla-push-service.readthedocs.io/en/latest/ Chrome - uses FCM Can't configure a custom push server endpoint, like self hosted server without shipping your own browser.