OneSignal's free plan now caps mobile push at 1,000 MAU per org. Here's how Courier and OneSignal compare on pricing, channels, and orchestration in 2026.
Updated Sep 2, 2026
Last updated: September 2026
In a Courier vs OneSignal comparison, Courier wins on multi-channel messaging at one flat price, and OneSignal wins on mobile push depth. The OneSignal free plan now caps mobile push and in-app messaging at 1,000 monthly active users per organization. OneSignal is still the stronger pick when push is the product, with the broadest mobile SDK list and iOS Live Activities.
Every fact here comes from each vendor's own pricing page or docs, read on September 2, 2026, and linked inline so you can check it. Claims we couldn't confirm first-party are left out. The weights: delivery and architecture 35, pricing at high volume 25, orchestration and testing 20, in-app and preferences 20. That favors platforms treating every channel as first class, the bias to declare up front. If push is your only channel, reweight and OneSignal moves up.
| Courier | OneSignal | |
|---|---|---|
| Pricing model | $0.005 per send, same rate on every channel | Three meters: per mobile MAU, per web push subscriber, per 1,000 emails (pricing) |
| Free tier | 10,000 sends a month, all channels | 1,000 MAU cap on mobile push and in-app; 10,000 emails a month; web push under existing limits |
| Entry paid plan | $0.005 per send, pay as you go, no volume cap | Growth from $19/mo plus usage |
| Channels | Email, SMS, mobile and web push, in-app inbox, Slack, Microsoft Teams, WhatsApp, webhooks | Mobile push, web push, email, SMS/RCS, in-app, iOS Live Activities |
| Microsoft Teams | Yes, a native Microsoft Teams channel | No Microsoft Teams channel |
| Slack | Yes, a native Slack channel | No Slack channel |
| Provider abstraction | 50+ providers with automatic failover; swap without code changes | No provider abstraction; OneSignal is itself the delivery layer |
| Visual journey builder | Journeys, with Experiments for A/B tests of 2 to 10 variants | Journeys, capped at 3 active on Free and 5 on Growth |
| Drop-in UI components | Inbox and Toasts (React, JavaScript, iOS, Android, React Native, Flutter), plus a preference center as an embeddable web component | In-app messaging and Live Activities; no inbox or preference center |
| Self-hosting | No, hosted service only | No, hosted service only |
| AI tooling (MCP, CLI, agents) | MCP server, CLI, AI Agent node in journeys, AI translations | Hosted MCP server, in open beta with 34 tools; no CLI |
| Best for | Product and lifecycle messages across channels, multi-tenant SaaS, marketers and engineers on one platform | Mobile-first apps where push and in-app are the main channels, with the widest SDK coverage |
Mobile SDK coverage. OneSignal ships SDKs for Android, iOS, Fire OS, Huawei, React Native, Expo, Flutter, Unity, .NET MAUI, Cordova, Capacitor, and web. If your app is built in Unity or .NET MAUI, that's the whole decision. Courier's client SDKs cover React, JavaScript, iOS, Android, React Native, and Flutter, and stop there.
iOS Live Activities and in-app messaging. OneSignal supports Live Activities on iOS 16.1 and up, with push-to-start on iOS 17.2 and SDK 5.2.0 and up. It also has in-app modals and banners on the same targeting rules as push. Courier has neither. For a delivery tracker with a live tile on the lock screen, that's a real gap.
Free web push. Web push stays on OneSignal's Free plan under the existing limits, at up to 10,000 subscribers per send. If web push is your whole strategy, that costs nothing.
Per-user pricing when you send often. At $0.012 per mobile MAU, OneSignal charges the same whether that user gets one push or fifty. A daily marketing cadence is cheap on that model and expensive on any per-send model, including ours.
One platform for both audiences. You don't have to pick between a platform for engineers and a platform for your marketers or success team. Courier is one platform for both. Everything in the UI is on the API: journeys, templates, brands, routing, preferences, audiences, tenants, users, and translations are first-class API objects. A marketer builds a journey by clicking, and an engineer manages the same object as code. An AI agent drives it through the API or the MCP server.
One price, one meter. A push, an email, an SMS, an in-app message, and a Slack message all cost $0.005 to send. No per-seat fee, no channel add-on, and no bill that grows because your app gained monthly users you never messaged. On OneSignal you reconcile three meters plus a custom SMS quote.
Channels past push and email. Slack, Microsoft Teams, and WhatsApp are first-class Courier channels. OneSignal has none of them. In B2B, where the alert your customer actually reads lands in Slack, that matters more than another push SDK.
Your providers stay yours. Courier runs on top of 50+ delivery providers, OneSignal included, with automatic failover. If SendGrid has a bad hour, the message goes out through the backup, and swapping a provider is a settings change rather than a release.
The message a user never got. Some of your users never receive a push at all, because they declined the permission prompt. Courier routing walks a channel list in order and stops at the first one that delivers. A user who declined push still gets the email.
Preferences and an inbox you don't build. Courier gives you a hosted preference page, a preference center as an embeddable web component, and a drop-in inbox that syncs in real time. Preferences are enforced on every send. OneSignal's frequency capping is Enterprise only.
Testing that ships. Experiments run 2 to 10 template variants at one send point inside a journey, with per-variant metrics. OneSignal keeps standard A/B on Free and Growth and reserves multivariate testing for Professional and up.
Twilio, LaunchDarkly, CircleCI, and Nav run their customer messaging on Courier.
Courier, from courier.com/pricing as of September 2026. Three tiers. Developer costs nothing and covers 10,000 sends a month, with Journeys, Broadcasts, the MCP server, the CLI, and every SDK. Business meters at $0.005 a send, the same rate on every channel, billed as you go with no ceiling on volume. It also turns on AI Translations, the AI Agent node, and cross-device email testing. Enterprise is quoted on your volume and adds an SLA, EU data residency, and RBAC. SOC 2 compliance and HIPAA certification are listed on the same page.
OneSignal, from onesignal.com/pricing: Free is $0, Growth starts at $19/mo, and Professional and Enterprise are custom and annual. Growth adds $0.012 per mobile MAU and $0.004 per web push subscriber. It gives you 20,000 emails a month and then charges $1.50 per 1,000, and puts SMS and RCS on a custom quote. Journeys are capped at 5, segments at 10, and reporting history at 90 days.
The two models cross at a fixed point. $0.012 divided by $0.005 is 2.4, so OneSignal's per-MAU rate is worth 2.4 Courier sends per user per month. Send fewer and Courier is cheaper. Send more and OneSignal is. That 2.4 ignores OneSignal's $19 base, which lifts the real crossover slightly at lower MAU counts.
One thing to watch: MAU counts any mobile subscription with at least one session in the billing cycle, opted in or not. With opt-in rates near half, you're paying for users who cannot receive a push.
Worked example, multi-channel at 25,000 mobile users. Each user gets 2 pushes and 1 email a month.
Within a rounding error of each other. The difference isn't the total, it's how many meters you reconcile and what happens the month you add a channel.
The OneSignal free plan now caps mobile push and in-app messaging at 1,000 monthly active users per organization. The count is summed across every app in the org, so three small apps share the 1,000. The cap starts September 1, 2026 for new accounts and October 1, 2026 for existing ones. Above the cap, mobile push and in-app messages pause until you upgrade. Web push, email, and SMS keep working under the existing plan limits. Mobile push used to be uncapped on Free.
Who it hits and how. OneSignal's announcement gives you warnings at 75%, 90%, and 100% of the threshold and 24 hours to upgrade. After that, mobile push and in-app messages stop sending.
Growth is $19/mo plus $0.012 per mobile MAU. Courier's Business rate is $0.005 per send. Comparing them needs a send frequency. Here it is at 4 pushes per user per month and again at 2, with every Courier figure at the full rate:
| Mobile MAU | OneSignal Growth | Courier at 4 pushes/user | Courier at 2 pushes/user |
|---|---|---|---|
| 5,000 | $79 | $100 (20,000 sends) | $50 (10,000 sends, and $0 once the free tier is applied) |
| 25,000 | $319 | $500 (100,000 sends) | $250 (50,000 sends) |
| 100,000 | $1,219 | $2,000 (400,000 sends) | $1,000 (200,000 sends) |
Read that honestly. At a marketing cadence of 4 pushes per user per month, OneSignal Growth is cheaper at all three volumes. The gap widens the more you send. At a product cadence of 2 or fewer, Courier is cheaper at all three. Above 50,000 MAU, OneSignal directs you to its team for custom pricing, so treat $1,219 as a list-price ceiling, not a quote.
Yes. OneSignal is a supported provider in Courier, so your app keeps its OneSignal SDK and device tokens and Courier calls OneSignal to deliver the push. You add routing, preferences, journeys, and the other channels above it. If the October 1 cap is forcing a decision, the smaller invoice is the wrong thing to optimize. Ask which channels you will need next year.
Start free with 10,000 sends a month at courier.com, or book a demo to walk through a migration off OneSignal.
FAQ
Keep exploring
One API, every channel
Courier gives you one API for email, SMS, push, and chat, with templates, routing, retries, and delivery logs built in.
Last updated Sep 2, 2026. Code samples are illustrative; provider APIs and pricing change over time, so check each provider’s docs before relying on them.
© 2026 Courier. All rights reserved.