Features · Delivery
A send never touches your server.
Delivery runs entirely on our infrastructure. Watch a campaign go out live, and trust that a large send neither slows your site nor blocks a smaller one behind it.
How delivery behaves under load
The interesting part of a push platform is what happens on a bad day, not a good one.
Sending never touches your server
Your site makes one lightweight call and is done. Everything after that (working out the audience, talking to the browser vendors, retrying what fails) runs on our infrastructure, so a campaign to a million people costs your host nothing.
Big sends never block small ones
Every campaign is broken up and delivered in parallel, with more going out as each part lands. A million-subscriber campaign and a thousand-subscriber one make progress side by side instead of queueing behind each other.
Live progress, not a spinner
Watch the count climb in the dashboard while a campaign goes out, over a private connection scoped to that site. If your connection drops, it reconciles with the server on reconnect rather than leaving you looking at a stale number.
Nothing gets stuck quietly
A send that stops making progress is picked up and either restarted or closed out within minutes, and if one part of a campaign fails outright the rest carries on rather than stalling behind it.
What happens when something goes wrong
Retried, but never sent twice
Anything that fails is retried automatically for up to an hour. Once the push service has accepted a notification it is recorded as sent, so a retry afterwards will not deliver those people a second copy.
Dead tokens reported back
When a browser tells us a subscription has expired or is invalid, that subscriber is deactivated with the reason recorded, so your list cleans itself as a side effect of sending rather than needing maintenance.
Cancel mid-flight
A campaign that is going out can still be stopped. It returns to a pending draft you can edit and send again, though a portion already queued for delivery may still go out before it stops.
What “sent” honestly means
Web push does not work like email. Your notification is handed to the browser vendor’s own push service, and that service decides when to wake the device. A laptop that is shut, or a browser that has not been opened in a month, may never show it. And nothing in the protocol tells anyone whether it did.
So we will not quote you a delivery rate, because the only number available to us is how many messages were accepted for delivery. What you get instead is honest and more useful: views and clicks, recorded when the notification is actually shown and actually opened.
Questions, answered.
Send something and watch it go.
Free forever for up to 300 subscribers.