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 Firebase credential, 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. On the same platform, with nothing routed through it, is app analytics.

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 Firebase credential, encrypted at rest. One app can never send through another's, a key is rotated in one place, and an app with neither of its own falls back to the gateway-wide pair.
Registered out of Firebase
Sign in with Google, pick the Android or iOS app out of the project, and the registration arrives with its name, platforms, package name and bundle id already filled in — linked to the project it came from.
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 send targets them by platform and by tag, combined as criteria rather than as separate sends.
Templates and 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 send
Deliveries and opens are recorded per app and per send, with failures carrying the provider's own error code.

Two ways in, and the difference is who the credential belongs to.

Both are offered on the same screen, for an app's own Firebase credential and for the gateway-wide one every app without its own falls back to. Which you want depends on whether the credential should outlive whoever set it up. APNs is a .p8 key, a team ID and a key ID either way.

Sign in with Google

Choose the Firebase project out of the ones that account can see. No file to download and nothing to paste, and the same sign-in can register the app for you.

It borrows one person's access, so sends stop the day that Google account is closed or loses the project.

Or paste a service account JSON

The credential Firebase hands out for servers to send with. It belongs to the project rather than to a person, so it keeps working after whoever added it has gone.

A trip through the Firebase console, and a file with a private key in it to move around safely.

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.
How do I connect Firebase Cloud Messaging?
Two ways, side by side on the same screen. Sign in with Google and choose the Firebase project out of the ones that account can see — no file to download and nothing to paste. Or paste the project's service account JSON, which is what Firebase hands out for servers. The difference is who the credential belongs to: a service account belongs to the project and keeps working after whoever added it has gone, while signing in borrows one person's access, so sends stop the day that Google account is closed or loses the project. APNs takes a .p8 key, a team ID and a key ID either way.
Can I register an app from its Firebase project?
Yes. Sign in with Google, pick the Android or iOS app out of the project, and the registration arrives with that app's name, platforms, package name and bundle id already filled in — the things the credentials step used to ask for straight after somebody had typed them. The new app is linked to the project it came from, so its Firebase credential is in place the moment it is registered; an iOS app still needs its APNs key.
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.