PUSH NOTIFICATIONS
Push is part of the platform. Not a paid add-on.
Native iOS and Android SDKs. The same visual flow builder, the same template language, and the same analytics surface you already use for email — extended to push, on every plan including Free.
Every channel, every tier
The Free tier ships with push. So does every paid tier.
One subscription, one bill, one platform. No per-channel surcharge, no MAU multiplier, no quiet step-up when traffic spikes. The price you see on the pricing page is the price you pay.
Free
$0
Email plus push. Up to 1,000 active devices and 10,000 pushes per month.
Paid tiers
$29 to $599
Email, push, and in-app — the same bundle, scaled. No add-on SKUs.
Enterprise
Custom
Every channel including SMS and WhatsApp. Custom contract, dedicated SLA.
Limits and channel bundles per tier are documented on the pricing page. The Free allocation is honest: 1,000 devices and 10,000 pushes is enough to evaluate the product, not a trial flag.
What ships with push.
Native iOS and Android SDKs
Swift on iPhone (iOS 14+, SPM + CocoaPods). Kotlin on Android (API 21+, Maven Central). No SDK wrapping a third-party vendor — Synapse calls APNs and FCM directly.
Bring your own credentials
Upload your own APNs .p8 key and your own FCM service account. Pushes go out from your Apple Developer and Firebase projects — the bundle ID and sender ID your users already trust. Credentials are KMS-encrypted at rest.
One flow engine, every channel
The same visual flow builder you use for email now sends push. Add a send_push step, branch on push opens and clicks, chain push with email and waits in a single sequence.
Same template language
Push templates use NLT — the plain-English template engine. Title, body, subtitle, image, and deep link all support variables, conditions, and filters. If you wrote an email template, you already know how.
Transactional API
POST /v1/push/send for OTPs, security alerts, and other one-shot deliveries. Priority routing, idempotency keys, per-tenant circuit breakers — the same operational primitives behind email send.
End-to-end telemetry
Every send, delivery, open, and click writes to push_logs and streams through the same analytics pipeline as email events. One delivery log, one analytics surface, one replay tool.
Sender of record
The push comes from your app. Not from us.
Upload your APNs .p8 token-auth key and your FCM service account JSON. From then on, push notifications go out from your Apple Developer team and your Firebase project — the bundle identifier and sender ID your users already see in their notification settings.
Credentials are encrypted at rest with envelope encryption. The dashboard, the API, and every other service hold metadata only — the key material is decrypted inside the push send worker and nowhere else. Rotation keeps the prior credential available for thirty days so you can roll back without dropping deliveries.
Push credentials
APNs
Production · Team ABC123XYZ
FCM
Production · project-foo
APNs
Sandbox · Team ABC123XYZ
Illustrative — your dashboard, your credentials.
Where push runs today.
iOS and Android are available now on their public registries. Web Push, React Native, and Flutter follow as a single contract — the same init, identify, and track surface across every client.
iOS
Available now
PYRXSynapse 0.1.0 on Swift Package Manager and CocoaPods Trunk. iOS 14 and newer. Event tracking with a disk-backed offline queue, identity merge, push registration, and cold-start attribution from a single Swift actor.
Android
Available now
tech.pyrx.synapse:synapse-core and synapse-push 0.1.2 on Maven Central. Android 5.0 (API 21) and newer. A two-artifact split so apps that only need event tracking pay zero footprint for push.
Web Push
On the roadmap
VAPID-based web push extends the existing @pyrx/synapse-browser package — no new SDK to install. Ships alongside iOS and Android as a follow-on.
React Native and Flutter
On the roadmap
Thin wrappers over the native SDKs above. Identical public API — init, identify, track, push.requestPermission, push.registerToken. Targeted for the next phase of platform work.
Built once, every channel
One pipeline. Email and push share the durability story.
Push opens, push clicks, and push failures emit into the same event log that carries every customer action through the platform. The same consumers persist them, route them into BigQuery, fan them out to your webhooks, and re-trigger flows. One replay tool. One delivery surface in the dashboard. One mental model.
When you branch a flow on a push open, you are branching on the same event envelope you would branch on for an email open. Not because the marketing copy said so. Because the architecture is actually shared.
Add push to the flows you already run.
Free tier ships with email plus push. 2,000 contacts, 1,000 active devices, 10,000 pushes per month. Bring your own APNs and FCM credentials. No credit card.