About PushNotifications.org: mission and principles

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.

Why this platform is being built

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.

Operating principles

Permission is not permanent attention. A subscription is a request to be useful, specific, and restrained each time a notification is sent.

Consent remains visible

Prompt source, permission state, opt-out history, and website ownership should remain understandable to the account owner.

Attention has a cost

Frequency caps, quiet hours, message categories, and inactive-audience policies belong in the delivery system.

Destinations must match

A notification should open the exact resource or account state it promises, with no misleading redirect or generic landing page.

Failures must be legible

Expired endpoints, temporary provider failures, throttling, and suppressed sends need distinct outcomes rather than one vague delivery count.

What the current platform controls

Websites and identity

Registered HTTPS origins, separate VAPID credentials, isolated subscriber records, and exact browser Origin checks during subscription.

Campaign decisions

Message content, public HTTPS destinations, registered website, draft state, and future schedule time.

Delivery operations

Scheduled queues, plan allowances, 24-hour repeat protection, permanent endpoint cleanup, accepted attempts, failures, and manual opt-outs.

What we will not pretend to control

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.

Plain-language commitment

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.

Control boundary by system layer

This map identifies the party that can actually change each outcome, so a team does not treat every failure as a platform defect.

Website team
The account owner controls the permission explanation, message purpose, audience rule, destination, schedule, and opt-out path.
PushNotifications.org
The platform validates campaign inputs, protects stored credentials, applies account limits, submits encrypted requests, and records bounded provider responses.
Browser and operating system
The browser controls permission and subscription creation. The browser and operating system control presentation, Focus modes, and device-level notification settings.
Browser push service
The vendor push service accepts or rejects each network request and routes accepted data toward the subscribed browser under its own delivery conditions.

Help shape a practical push platform

Start with a registered HTTPS website, or tell us which workflow creates the most friction for your team.

Create a free account