Builders

Ship the notification.
Not a vendor per channel.

Product teams send signup codes, dunning, and “approve this Chrome on Lagos” from one SDK. Docs, MCP, WordPress, an afternoon, not a quarter. You keep the mailbox and the WhatsApp session.

Auth, invoices, PushMirror in app.

Developer in a denim jacket approving a new device on her phone

What you send

SaaS & product teams

Auth, invoices, PushMirror in app.

Auth

Product alerts

Welcome, invoice, dunning, flags. Your SMTP. Our templates and logs.

PushMirror

1 tap, emoji, or digit inside your app. Not a hosted login page.

On the ground

New Mac in Lagos, 1 tap, not a hosted login page

The user signs in from Chrome. PushMirror opens in your app: device, city, approve or deny. WhatsApp OTP if they have no push token yet. Invoice failed? Email from your SMTP, WhatsApp only if they opted in for billing chat.

Signup, reset, new device, one template slug
PushMirror inside the product you already ship
Invoices and dunning on the mailbox you pay for

9:41

●●●

Northwind

New device

Security

Connexion Chrome · Mac · Lagos. Approuver cet appareil ?

09:41

Approuver

09:41

Appareil ajouté. Prochaine connexion sans challenge pendant 30 jours.

09:41

How it works

Three steps. Same API.

Link the desk, map the templates, send when the file moves. One POST /send on every channel.

Step 01

Create a project

Key, templates, optional WhatsApp QR.

Step 02

Drop the SDK

Node, Python, PHP, Java, .NET. MCP if you want a guided setup.

Step 03

Wire PushMirror

Device token + challenge. OTP stays the fallback.

new device.ts · TypeScriptAuto

const challenge = await zindua.pushMirror.create({  userId: user.id,  type: "approve",  purpose: "login",  context: {    device: "Chrome on Mac",    city: "Lagos",  },  fallback: { channel: "whatsapp", to: user.phone },});