HOW IT WORKS
Permission belongs to the visitor
Browser push requires a secure origin, an appropriate service worker and user consent. Never force a permission request before explaining its value.
From subscription to message
A browser creates a push subscription and shares its endpoint and keys with your backend. PUXIO would securely map that subscription to a project and optional user identity.
Works across modern browsers
Web Push uses browser push services. Platform behavior differs, particularly on iOS where web push is supported for eligible Home Screen web apps, subject to permission and platform rules.
Real-world controls
Support subscription renewal, endpoint expiry, batching, rate limits and delivery TTL rather than pretending every message can arrive at any time.