A OneSignal alternative, now that free mobile push stops at 1,000 users
OneSignal's free plan now stops mobile push at 1,000 monthly users. What it costs to stay, the free alternatives, and how SignOps compares in rupees.
From 1 October 2026, OneSignal’s free plan stops mobile push above 1,000 monthly active users (new accounts since 1 September). Web push and email keep working, but an app with 1,001 users now pays or loses push. If you are deciding whether to upgrade or move, here are the numbers.
What staying on OneSignal costs
The Growth plan is $19 a month plus $0.012 per monthly active user above 1,000.
| Monthly users | OneSignal Growth | SignOps |
|---|---|---|
| 1,000 | Free | Free |
| 5,000 | About Rs 5,900 | Rs 499 |
| 20,000 | About Rs 21,700 | Rs 1,999 |
| 50,000 | About Rs 53,400 | Rs 4,999 |
OneSignal at about Rs 88 to the dollar, before GST. SignOps Starter is Rs 499 for 5,000 devices, then Rs 0.10 a device. The SignOps column counts devices; one user with a phone and a laptop counts twice.
The alternatives
| Option | Free | Paid | What you build yourself |
|---|---|---|---|
| FCM directly | Unlimited | Free | Token storage per user, targeting, scheduling, cleanup, a dashboard |
| Expo push | Unlimited | Free | The same, and it only works for Expo apps |
| Pusher Beams | 1,000 devices | $29 a month for 10,000 | Segments and a composer |
| Truepush | Free | None | Mainly web push for publishers |
| SignOps | 1,000 devices | Rs 499 a month for 5,000 | Nothing for push |
Where OneSignal is still the better choice
- You use journeys, in-app messages and A/B tests heavily. SignOps has topics, scheduling, templates, caps and a composer, not journeys.
- Your marketing team already lives in OneSignal’s dashboard.
Where SignOps fits
- You want push without a per-user dollar bill: Rs 499 a month for 5,000 devices, in rupees with a GST invoice.
- You also need login approvals, passkeys or email OTP. SignOps puts all four on one API key and one user id, so the device that gets your pushes also approves logins.
- You want your own Firebase and Apple keys, so tokens stay in your project and you can leave any time.
Moving from OneSignal
- Export subscribers from OneSignal with their external user id and push token.
- Upload your Firebase service account and APNs key to SignOps once.
- Import the tokens with
POST /v1/devices/importor a CSV in the dashboard. - Change your server’s send call to
POST /v1/pushwith your user ids.
Users keep getting pushes without an app update, as long as your app registers with Firebase, which OneSignal’s SDK already does on Android.
Sources: OneSignal: what’s changing on the free plan, OneSignal pricing guide (Sequenzy), Pusher Beams pricing.