Connect the game
Create apps, protect provider credentials, and register player devices.
The PushHub platform
One operating layer for every player return.
Bring audiences, campaigns, automation, delivery, and learning into one workspace built around the rhythm of living games.
Illustrative portfolio view3 apps ready
Overview
Audience
Messages
Delivery
Settings
Live workspace
World operations
Reachable players
148kLive campaigns
04Automations
12Current flow
Season launchScheduled for 19:00
Guild rescueEvent trigger active
Delivery fleetHealthy
Example data for product illustration. Not customer performance.
Player context should travel with every message.
PushHub keeps the audience, decision, delivery path, and outcome together so LiveOps and engineering work from the same evidence.
How it works
A shared loop from game signal to player outcome.
Understand the audience
Use device context and game attributes to define reusable segments.
Operate the moment
Compose campaigns or respond to authenticated server events.
Learn together
Review delivery evidence, experiment results, and operational history.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
Multi-app workspace
Keep titles, environments, credentials, roles, and usage within one company boundary.
Durable delivery engine
Process campaign and event work with leases, retries, attempt history, and operator recovery.
Audience, messaging, and config tools
Build segments, campaigns, templates, triggers, experiments, remote config, and delivery reports.
Cross-channel journeys
Planned journey orchestration will coordinate more than mobile push across a player lifecycle.
In the game
Built for the work between releases.
Launch a season
Align announcements, reminders, and final-hour messages without a client update.
Respond to play
Turn a trusted backend event into a delayed, personalized push.
Protect attention
Apply quiet hours, caps, eligibility, and cancellation before provider submission.
Control stays visible at every layer.
Company and app boundaries, scoped credentials, audit trails, and secret-free operations keep the platform understandable as teams grow.
Tenant isolation
Company and app ownership is enforced in the data model.
Protected credentials
Provider secrets use encrypted storage and never enter dispatch jobs.
Operational recovery
Keme administrators can inspect, retry, or dismiss failed work with an audit reason.
Questions teams ask before they commit.
No. PushHub is the operating layer above FCM and APNs, while each customer keeps control of their provider projects and credentials.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.