Push to users,
not devices.

Alrevion Push gives your product reliable push notifications with a single integration. Address users by ID and we fan out to every device across every platform.

See channels

1

channel live

202

async & durable

4+

channels incoming

Push channels

One API, every platform

Integrate once. Web Push is live today. iOS, Android, Windows and desktop slot in behind the same endpoints, no rewrites when they ship.

Live

Web Push

Native browser push to Chrome, Firefox, Safari and Edge. No app required. Reach users on desktop and mobile web.

Try it

In development

APNs (iOS / macOS)

Apple Push Notification service for iPhone, iPad and Mac. Encrypted, reliable, approved by the App Store.

Notify me

In development

FCM (Android)

Firebase Cloud Messaging for Android phones and tablets. The standard delivery path for every Android device.

Notify me

In development

WNS (Windows)

Windows Push Notification Services for native Windows 10/11 apps and PWAs on the Microsoft Store.

Notify me

In development

WebSocket (Linux & desktop)

Realtime delivery via a persistent WebSocket. For Electron, desktop PWAs and Linux environments without native push.

Notify me

Live demo

Feel a real push, right now

This runs entirely in your browser using the same Web Push notification your users receive. No signup, no backend, no tokens.

Notification title Message

Live preview

Alrevion Push now

Your order has shipped

Tap to track your delivery in real time.

Powered by the browser Notification API. This is exactly what the Web Push channel delivers.

See channels

Developer experience

Send your first push in minutes

Register devices with the publishable key from the client. Send from the server with the secret key. One REST call and we handle the rest.

Address users, never raw device tokens
Idempotency, retries and status built in
Per-project VAPID, APNs and FCM credentials

# 1. Register a device (client, publishable key)
curl -X POST https://api.push.alrevion.com/v1/devices \
  -H "Authorization: Bearer $PK_KEY" \
  -d '{"external_user_id":"user-123","channel":"webpush", ...}'
 
# 2. Send a push (server, secret key)
curl -X POST https://api.push.alrevion.com/v1/notifications \
  -H "Authorization: Bearer $SK_KEY" \
  -H "Idempotency-Key: order-456-shipped" \
  -d '{"to":{"external_user_id":"user-123"}, ...}'

import { AlrevionPush } from "@alrevion/push-sdk"
 
const push = new AlrevionPush({ secretKey: process.env.PUSH_SK_KEY })
 
// send to a user, we fan out to all their devices
await push.notifications.send({
  to: { external_user_id: "user-123" },
  notification: { title: "Order shipped", body: "Tap to track →" },
  idempotencyKey: "order-456-shipped",
})

How it works

Live in three steps

From zero to real OS notifications with no infra to run.

1

Provision your project

Call /admin/projects to get a publishable key (pk_) for the client and a secret key (sk_) for your server.

2

Register devices

From your web or app client, call POST /v1/devices with the pk_ key. The user's device is now addressable by their ID in your system.

3

Send by user ID

From your server, call POST /v1/notifications with the sk_ key. We fan out to every active device and retry until delivered.

Why Alrevion Push

Engineered for reliability

Most push failures are silent. We built idempotency, durable retry, and dead-token pruning so pushes actually arrive, not just fire.

01

Idempotent sends

Pass an Idempotency-Key and duplicate sends from retries or race conditions across your services are deduplicated automatically.

02

Durable retry

A Cloudflare Durable Object backs every delivery. Exponential backoff, cap and DLQ mean a temporary APNs outage won't lose your push.

03

Dead-token pruning

When a push endpoint returns 410 Gone or Unregistered, we deactivate the subscription. Your delivery rate stays clean over time.

04

Multi-channel fan-out

One call to /v1/notifications reaches the user on web, iOS, Android and Windows simultaneously. You never touch tokens.

How we compare

Different from OneSignal and Twilio

Most push vendors give you device tokens and per-platform quirks. We give you a user ID and handle the hard parts.

Alrevion Push Typical vendor

Address users by your own ID

Automatic device fan-out Partial

You own the VAPID / APNs keys

Idempotent sends (no duplicates)

Durable retry + dead-token pruning Varies

One API across every channel Per-platform SDKs

Runs on your Cloudflare edge

No per-seat vendor lock-in

Pricing

Start free. Scale when you do.

Transparent pricing with a generous free tier. No credit card to start.

Hobby

For side projects and prototypes

$0 /mo

10,000 pushes / mo
Web Push (all browsers)
Community support

Pro

For growing products

$29 /mo

500,000 pushes / mo
All channels (web + mobile)
Webhooks & delivery analytics
Priority support

Enterprise

For scale and compliance

Custom

Unlimited pushes
SLA, SSO & audit logs
Dedicated support
On-prem options

FAQ

Questions, answered

Web Push (Chrome, Firefox, Safari, Edge) is live. APNs for iOS/macOS, FCM for Android, WNS for Windows and WebSocket for Linux/desktop are in active development behind the same API endpoints.

Push to users, not devices.

One API, every platform

Web Push

APNs (iOS / macOS)

FCM (Android)

WNS (Windows)

WebSocket (Linux & desktop)

Feel a real push, right now

Send your first push in minutes

Live in three steps

Provision your project

Register devices

Send by user ID

Engineered for reliability

Idempotent sends

Durable retry

Dead-token pruning

Multi-channel fan-out

Different from OneSignal and Twilio

Start free. Scale when you do.

Hobby

Pro

Enterprise

Questions, answered

Which channels work today?

How is the user model different from OneSignal?

What happens if my server retries the send request?

What if a push endpoint goes stale?

Do I need to run servers?

Ready to stop managing device tokens?

Push to users,
not devices.