Delivery providers
Configure Firebase Cloud Messaging or Apple Push Notification service for each app.
Integrations
Meet the systems already responsible for your game.
Connect PushHub to app-owned delivery providers, trusted backend services, client platforms, and the operational infrastructure that keeps dispatch observable.
Illustrative system mapBoundaries verified
Overview
Audience
Messages
Delivery
Settings
Live workspace
Production request path
Ingress
REST APIDispatch
PostgreSQLDelivery
FCM + APNsCurrent flow
Game servicesIdentity and events
PushHubTarget and orchestrate
Player devicesReceive and respond
Example data for product illustration. Not customer performance.
PushHub should fit around your source of truth.
The platform receives trusted player context and events, manages messaging operations, and sends through customer-owned provider projects without becoming the game database.
How it works
Connect the boundary, not the whole company.
Game services
Use REST and scoped keys from the backend that owns player state.
Game clients
Register tokens, handle deep links, and optionally report receipt and open events.
Operations stack
Run durable data, wake-up queues, health checks, logs, and deployment controls.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
FCM and APNs
Send Android and iOS notifications through credentials owned by each customer app.
REST API
Connect any trusted backend or engine that can make authenticated JSON requests.
Client SDKs
Use the Beta Android and iOS SDKs, or the Preview JavaScript and engine SDKs, while coverage expands.
Data destinations
Planned connectors will export event and delivery context to selected analytics and warehouse systems.
In the game
A composable role for every system.
Firebase and Apple
Remain the native delivery networks and app credential authorities.
Game backend
Remains authoritative for player identity, progression, economy, and events.
PushHub
Provides campaign operations, audiences, automation, delivery recovery, and reporting.
Integration lists should distinguish product from infrastructure.
Public pages label what customers connect, what PushHub runs internally, and what is planned instead of presenting every technology as a turnkey connector.
Customer integrations
FCM, APNs, REST, and the Beta and Preview client SDKs are customer-facing paths.
Platform infrastructure
PostgreSQL and Redis support durable operation but are not customer data connectors.
Planned destinations
Analytics and warehouse connectors remain Roadmap until implemented.
Questions teams ask before they commit.
Send only the identity and properties needed for messaging. Your game services remain the broader player source of truth.
Give your backend a calmer push boundary.
Start with one app, one meaningful moment, and one audience worth reaching.