Consent remains visible
Prompt source, permission state, opt-out history, and website ownership should remain understandable to the account owner.
PushNotifications.org is being built as a web-first notification platform for teams that want control over subscriber data, message quality, frequency, and infrastructure cost.
The open Web Push browser model requires more than a send button to operate well. Permission timing, service-worker behavior, endpoint health, audience policy, quiet hours, accurate destinations, and opt-out handling all affect whether the channel remains useful.
The platform brings those decisions into one workspace without turning subscriber count into the primary billing unit. The goal is to help a small team understand what will happen before it schedules a campaign.
Permission is not permanent attention. A subscription is a request to be useful, specific, and restrained each time a notification is sent.
Prompt source, permission state, opt-out history, and website ownership should remain understandable to the account owner.
Frequency caps, quiet hours, message categories, and inactive-audience policies belong in the delivery system.
A notification should open the exact resource or account state it promises, with no misleading redirect or generic landing page.
Expired endpoints, temporary provider failures, throttling, and suppressed sends need distinct outcomes rather than one vague delivery count.
Registered HTTPS origins, separate VAPID credentials, isolated subscriber records, and exact browser Origin checks during subscription.
Message content, public HTTPS destinations, registered website, draft state, and future schedule time.
Scheduled queues, plan allowances, 24-hour repeat protection, permanent endpoint cleanup, accepted attempts, failures, and manual opt-outs.
Browsers and operating systems own the final permission prompt, notification rendering, device preferences, and vendor delivery infrastructure. PushNotifications.org can make a correct request and report the outcome, but it cannot guarantee that a device displays every message.
Product pages distinguish planned behavior from active features. Research links point to primary sources where possible. Testimonials, performance metrics, certifications, and customer logos are not published without verification.
Review the implemented security controls and the editorial policy for the current evidence boundary. The HTML sitemap and public page directory provides a complete route to every published product, guide, article, and policy page.
This map identifies the party that can actually change each outcome, so a team does not treat every failure as a platform defect.
Start with a registered HTTPS website, or tell us which workflow creates the most friction for your team.