Push gateway
APNs and FCM for every app, each with its own credentials.
Apps with no accounts still get reached: one topic send per app covers every install. When an app does gain authentication, the same campaign targets registered devices by platform and tag.
Start free trial
14 days, no card
One send, two transports, every kind of install.
The gateway holds each app's APNs key and FCM service account, chooses the transport per platform, and carries the provider's own error codes back so a failure is diagnosable rather than silent.
The same key reaches the AI gateway and the storage gateway. See plans and limits.
push pipeline
a campaign, or one API call
Penstoke gateway
- Apple APNs
- Firebase FCM
- iOS
- Android
- Web
Each app carries its own APNs key and FCM credentials, held server-side. A topic send reaches every install without a device ever registering.
Penstokenow
Delivery finished
Sent to every install on iOS, Android and Web.
What the push gateway does
- Credentials per app
- Each app holds its own APNs key and FCM service account, encrypted at rest. One app can never send through another's, and a key is rotated in one place.
- Reach every install, with no accounts
- A topic send reaches every install of an app without a single device registering. Apps with no sign-in are the hardest to reach and the most common; this is the path for them.
- Or target what you know
- Once devices do register, the same campaign targets them by platform and by tag, combined as criteria rather than as separate sends.
- Campaigns, templates, schedules
- Compose once, reuse as a template, send now or on a schedule, including recurring ones in a timezone you set.
- Copy written for you
- The gateway can draft notification variants in the tone you choose, through the same AI gateway your own keys sit behind.
- Counted per app and per campaign
- Deliveries and opens are recorded per app and per campaign, with failures carrying the provider's own error code.
Sending one notification
curl -X POST "$PENSTOKE_URL/push/v1/send" \
-H "Authorization: Bearer $PENSTOKE_KEY" \
-d '{
"appId": "app_7f3c…",
"title": "Order shipped",
"body": "On its way.",
"target": { "platforms": ["IOS", "ANDROID"], "tags": ["vip"] }
}'Push gateway questions
- What is a push notification gateway?
- A push gateway is one API in front of the platform services that actually deliver notifications — Apple's APNs and Google's Firebase Cloud Messaging. It holds each app's credentials, picks the right transport per platform, handles retries and error codes, and records what was delivered.
- Can I send notifications without registering devices?
- Yes. One topic send per app reaches every install through FCM, with no device token stored and no account needed in your app. That covers iOS, Android, Web apps that have no sign-in at all. When an app later gains authentication, the same campaign can target registered devices by platform and tag instead.
- Does it work with React Native, Flutter and native apps?
- Yes. The gateway speaks APNs and FCM, so any client that can receive a notification on iOS, Android or Web works — native, React Native, Flutter or anything else. Devices register against a public SDK key that can only register, never send.
- How are scheduled and recurring campaigns handled?
- A campaign can be sent immediately, scheduled for a moment, or made recurring. Recurrence is computed in the timezone the deployment sets, and a plan caps how many schedules you hold at once rather than how many sends you make.
- What does a send cost?
- Nothing from Penstoke. APNs and FCM are free services from Apple and Google, and you use your own credentials for both. The subscription caps how many apps, campaigns a month and schedules you keep, not how many notifications you deliver.