One shared push service delivers messages, channel posts and call rings to backgrounded and locked devices — APNs and FCM handled for you, from the same realtime SDK you run on your own servers.
Device tokens and delivery to Apple and Firebase are handled for you — no push pipeline to build.
High-priority pushes trigger native ringing through CallKit/PushKit and Android full-screen intents.
Messages, channel posts and call signalling all ride the same shared push service.
Deliver when your app isn’t in the foreground — backgrounded, closed or locked.
Ring and message pushes are prioritised so time-sensitive events arrive without delay.
Token storage and delivery config live inside the platform you self-host.
No. The platform manages device tokens and delivery through Apple Push Notification service and Firebase Cloud Messaging, so a message, channel post or call ring reaches the device without you building the push pipeline.
Yes. Call rings are delivered as high-priority pushes that trigger native ringing — CallKit/PushKit on iOS and a full-screen incoming UI on Android — even when the app is closed or the device is locked.
Yes — one shared push service carries chat messages, channel and story posts, and call signalling, so you configure delivery once for the whole platform.
That is the point. Push exists to reach users when your app isn’t in the foreground — backgrounded, closed or locked — so they never miss a message or a call.
On infrastructure you control. Push runs inside the platform you self-host.
One platform for messaging, streaming and calls — talk to us and we'll help you scope it for your product.
Pool