Unlimited tags
Their free plan caps tags at 6. At PushMesh, tags have no limit on any plan — not even on Free. Segment by behavior, plan or city: the ruler is yours, not ours.
The compatibility API speaks the classic push format: on the server, you swap the endpoint and the key. And every send comes back with a real receipt from the device — proof of delivery, not an estimate.
OneSignal told its customers: the free plan will cap mobile push at 1,000 monthly active users — anyone above the ceiling is invited to pay. If your base is past that, this page is the way out.
Only what their announcement tightened — no inflated numbers, no asterisks.
Their free plan caps tags at 6. At PushMesh, tags have no limit on any plan — not even on Free. Segment by behavior, plan or city: the ruler is yours, not ours.
The market standard is to report “sent”. PushMesh confirms the message reached the device: every send comes back with a signed receipt, and your delivery metric becomes a fact, not an estimate.
No base subscription: you pay per monthly active user, in blocks, with the public price frozen on the invoice. The first 1,000 monthly active users are free every month, on any plan — and that ceiling is dynamic: we change it in the console, with no deploy.
The honest picture of the effort: low on the server, medium in the app — and one stage nobody automates.
PushMesh's /api/v1 accepts the classic format — include_player_ids, contents, included_segments and company. Sending, querying and reports use the format you already know.
The package changes and the initialization changes — the rest of your code stays the same. Tags, triggers and permission have direct equivalents in our SDK.
Nobody migrates a device base with an API key: devices come in as users update the app. It's a period, not a command — and the guide shows how to get through it.
Create the account, register the app and send the first push with a receipt. Up to 1,000 monthly active users are free.
Create a free account