Push notifications · facts read November 18, 2026
Apple Push Notification service (direct)
Sending straight to Apple's APNs from your backend over HTTP/2 with a token signing key, with no service in between. No vendor in between: your backend signs a token and sends to Apple.
- Free plan
- Apple lists no per-notification price; sending needs an Apple Developer Program membership ($99 a year).
- Paid from
- Not stated on the pricing page
- Monthly cost at 1,000 users
- $0/month Apple lists no per-notification price; the $99/year Apple Developer Program is listed with the store fees.
- Free plan allows commercial use
- Not stated
- Open source
- No
- Self-hostable
- Yes
Source: Apple Push Notification service (direct) pricing, read November 18, 2026. Prices change; check the vendor's page before you commit.
Best for
- iPhone-only Swift apps
- Keeping user data out of another vendor
- Time-sensitive alerts and Live Activities
Watch out for
- iOS only; Android needs FCM alongside it.
- You write the sender: a JWT signed with your .p8 key, HTTP/2 requests, and deleting tokens APNs reports as no longer valid.
How Cuely scores Apple Push Notification service (direct)
The published scores, from −3 to +3, that decide when Cuely picks it. Method
- +3an iPhone app in Swift with Xcode. Apple's own service, with nothing between your backend and the phone.
- +1native iOS or Android app. Reaches iPhones and iPads; Android needs FCM too.
- +1keep costs as low as possible. No vendor fee beyond the Apple Developer Program.
- +1fewer vendors. No push vendor to sign up for.
- +1regulated or compliance-sensitive. No third party holds your users' device tokens or message contents.
- −2marketing or re-engagement campaigns to segments of users. A raw send API; segments and scheduling are yours to build.
Apple Push Notification service (direct) alternatives
Recipes with Apple Push Notification service (direct)
- Native iPhone app in Swift · the pick