Pulse Mobile is how your phone connects to Pulse. Pulse Relay is the secure remote transport layer underneath it.
The mobile app is the user-facing product surface. Pulse Relay is the secure bridge that carries mobile traffic between your phone and your Pulse instance without turning Relay into a separate top-level brand that users have to mentally decode.
QR or deep link
Pair your phone to a Pulse instance through a governed onboarding flow instead of typing a pile of secrets into the app.
Relay-backed remote access
Pulse Relay carries the encrypted mobile connection so your phone can reach your Pulse instance remotely.
Works with self-hosted or cloud
The same mobile path can connect to your own Pulse server or a hosted Pulse Cloud tenant.
What Pulse Mobile is for
- Checking Pulse when you are away from the dashboard.
- Receiving push notifications and opening the related work from your phone.
- Keeping a real mobile path to self-hosted Pulse and Pulse Cloud instead of treating mobile as an afterthought.
What Pulse Relay does
- Routes the encrypted mobile connection between the app and your Pulse instance.
- Supports remote mobile access and push delivery.
- Stays an infrastructure capability inside the mobile story rather than a separate top-level product users have to understand first.
How it fits with the rest of Pulse
Pulse Mobile is not a separate monitoring product. It is the mobile access surface for the same Pulse runtime you run yourself or consume through Pulse Cloud.
Self-hosted Pulse
Run Pulse yourself, then pair the app to that instance and use Relay for remote mobile access.
Pulse Cloud
Let me host the Pulse runtime for you, then pair the mobile app to your hosted tenant through the same governed mobile path.
Pulse Mobile deserves a first-class public explanation.
The right public model is simple: Pulse Mobile is the app, Pulse Relay is the transport layer, and both self-hosted Pulse and Pulse Cloud can sit behind that connection. This page makes that relationship explicit.
See Pulse Cloud