Push Notification Platform

Part of the worlds-biggest-software-project initiative.

An open, AI-native push notification platform that unifies iOS, Android, and web delivery behind a single API with built-in segmentation and analytics.

A unified notification infrastructure that abstracts APNs, FCM, and the Web Push Protocol behind one API and SDK layer. Aimed at product and platform engineering teams who need cross-channel campaigns, managed device token registries, and reliable delivery analytics without stitching together multiple vendors. Solves the fragmentation that comes from maintaining separate integrations, segmentation logic, and reporting pipelines for every push surface.

Why Push Notification Platform?

Incumbents like OneSignal, CleverTap, Braze, Courier, and Airship are proprietary SaaS with no open source component, leaving teams with concerns about data ownership and lock-in.
Firebase Cloud Messaging is free but offers basic segmentation, no built-in A/B testing, no omnichannel orchestration, and limited per-user personalisation.
Existing platforms split into either no-code (Braze, OneSignal) or code-first (Knock, Novu) camps; few excel at both for hybrid product and marketing teams.
Token expiration handling — including FCM's 30-day inactivity mark and 270-day expiration — is still left to developers; no platform fully abstracts stale token cleanup.
Compliance automation for GDPR, CCPA, and emerging mobile privacy regimes is largely manual across the field.
Apple's mandatory UISceneDelegate change in the iOS 27 SDK (September 2026) breaks APNs token registration on unmigrated apps; no platform yet ships migration tooling.

Key Features

Unified Multi-Channel Delivery

Single API abstracting iOS (APNs), Android (FCM), and web (Web Push Protocol)
SDKs for iOS, Android, and JavaScript
Provider-agnostic architecture allowing switching between push backends
Optional omnichannel expansion to email and SMS in a single workflow
REST API for server-to-server integration

Device & Token Management

Managed device token registry with automatic refresh and invalidation
Handling of stale tokens to keep audience sizes accurate
Topic and attribute-based routing models
Multi-environment support for staging and production token sets

Audience Segmentation & Targeting

Segmentation by user attributes, device properties, and geography
Behavioural triggers for real-time messages in response to user actions
Frequency capping and quiet-hours / focus-mode enforcement
User preference management for opt-in, channel choice, and do-not-disturb

Campaigns, Scheduling & Analytics

A/B testing across multiple message variants
Scheduling with timezone-aware delivery
Rich media payloads: images, action buttons, deep links
Delivery, open, and click-rate analytics with per-notification logging
Visual workflow builder for multi-step campaigns

Developer Experience & Observability

Delivery logs and debugging interface for per-notification troubleshooting
Embeddable in-app notification centre components
Infrastructure-as-code style workflow definitions
Cost-transparent reporting per channel, user, and message

AI-Native Advantage

AI is applied where today's platforms still rely on rules: per-user send-time optimisation models, LLM-driven content generation from prompts, ML-based channel selection, unsupervised behavioural cohorting, and churn-prediction-driven fatigue management. ML inference can also drive deep-link target prediction and fallback-channel selection when primary delivery fails. These move the platform beyond static frequency caps and template-based personalisation seen in incumbents.

Tech Stack & Deployment

The platform targets self-hosted and cloud deployment modes, mirroring Novu's open-source-first approach so teams with data-ownership or compliance requirements can run their own instance. Integrations build on the standardised APNs, FCM, and Web Push Protocol specifications, with a provider-agnostic layer for swapping backends (FCM, APNS, Expo, OneSignal, Twilio, SendGrid). Client SDKs cover iOS, Android, and JavaScript, with embeddable notification-centre components for React, Next.js, and Vue surfaces.

Market Context

The push notification software market is valued at approximately USD 2.1 billion in 2026 and is projected to reach USD 4.7 billion by 2033 (research.md). OneSignal alone serves over 200,000 apps and handles roughly 1.3 trillion messages per year. Primary buyers are mobile and web product teams, growth and lifecycle marketers, and platform engineering groups at B2C and B2B SaaS companies.

Project Status

This project is in the research and specification phase.
Contributions, feedback, and domain expertise are welcome.

Contributing

We welcome contributions from developers, domain experts, and potential users. See CONTRIBUTING.md for guidelines.

Important: All contributions must be your own original work or clearly attributed open-source material with a compatible licence. Copyright infringement and licence violations will not be tolerated and will result in immediate removal of the offending contribution. If you are unsure whether a piece of code, text, or other material is safe to contribute, open an issue and ask before submitting.

Licence

Licence to be determined. See discussion for context.