Reach readers on web and mobile
Send to readers who chose to hear from you. Bring them back to a story on your website or a screen in your app.
Web & mobile push for publishers
Bring readers back to your website and app. Send, schedule, and track push notifications from one workspace.
Public signup is coming soon. Explore our launch plans below.
Create, schedule, and review your messages.
Web and mobile notifications, scheduling, and reporting in one workspace. Built for newsrooms, independent publishers, and growing audiences.
Send to readers who chose to hear from you. Bring them back to a story on your website or a screen in your app.
Send now, schedule a message, or trigger one when you publish. Set the timing to suit your readers.
Review delivery, receipt, and click counts for each message. Add UTM tags to web links to follow visits in your analytics.
Connect your website and app. Prepare one message, choose your platforms, and follow the results.
Add web push to your website, or integrate the mobile SDK with your app.
Write your message, choose web, mobile, or both, and set the destination and send time.
See how each message performs, from delivery to notification clicks.
A first look at the new paths, public spaces, and places to stop.
Read the storyConnect your CMS to the Sending API. Your integration chooses the articles and whether to reach web, mobile, or both. Notirabbit skips a new message when its intended send time falls within your app’s quiet hours.
Explore the Sending APIChoose your monthly audience size. All three channels share one allowance.
Monthly billing · Prices in USDStart publishing to a small audience.
Shared across web, iOS & Android
For your daily stories and your team.
Shared across web, iOS & Android
For larger audiences and publishing networks.
Shared across web, iOS & Android
Push notifications to readers who have opted in on your website or mobile app. Send now, schedule for later, or connect your publishing workflow through the API. Delivery depends on the reader’s device, permissions, and notification settings.
No. Independent publications, blogs, and other content-led businesses can use it too. Reach readers on the web and in your apps, with or without a CMS integration.
For web push, add the JavaScript snippet and service worker to your HTTPS website. For mobile push, integrate the mobile SDK and configure your platform credentials. Then choose which enabled platforms each message should reach from your workspace.
For web push, Notirabbit can help migrate previously opted-in readers on the same domain. As those readers return to your site, compatible subscriptions can be renewed without another permission prompt. The migration is gradual and depends on browser support, site visits, and available browser storage.
Web push reaches subscribed browsers, including supported mobile browsers. Native mobile push reaches your iOS and Android apps. Every plan includes all three channels with one shared MAU allowance across your workspace.
Up to 1,000 MAU shared across web, iOS, and Android, with one website and one mobile app. Free includes 1,000 messages per month across your workspace. Manual, scheduled, and API sends share this limit. Its MAU count covers the last 30 days.
Yes. Give mobile notifications an app destination so a tap opens the relevant story or screen. Web subscribers can open the website version of the same story. Your app must be set up to handle that destination.
Paid plans include unlimited messages, subject to fair usage. Normal publishing to opted-in audiences is included; excessive, repetitive or abusive sending may be limited to keep delivery reliable. Free includes 1,000 messages per month; paid plans have no fixed daily or monthly message quota. Repeated sends to the same subscription or installation do not increase its MAU count.
One message sent to web, iOS, and Android together counts as one message, regardless of audience size. Separate messages count separately. Manual, scheduled, and API sends share the monthly limit across your workspace.
For pricing, MAU counts anonymous browser subscriptions and app installations with at least one successful push send during your billing month. Repeat messages to the same subscription or installation count once. Stored subscriptions with no successful send during that period do not use the allowance. Free uses the last 30 days.
Each browser subscription and app installation counts separately. One browser subscription plus one app installation uses 2 MAU, even if both belong to the same person. All three channels share one workspace allowance.
Choose the next shared MAU capacity as your monthly audience grows. Contact us for more than 200,000 MAU. Public signup is coming soon; viewing a plan does not start a subscription or payment.
Plan your next campaign across web and mobile.