Send Email, Push and In-App messages, deep-link users to any screen, and automate conditional sends — from one multi-tenant dashboard. Bring your own FCM and SMTP.
A developer-first alternative to MoEngage, OneSignal & Braze.
Five channels, one platform
Email, push, in-app, deep links and automation — behind clean adapter interfaces so you're never locked in.
Your own FCM credentials
Reach Android and iOS devices through your own Firebase project — FCM relays to APNs for iOS. Engage batches sends, prunes dead tokens automatically, and never owns your deliverability.
Any SMTP, provider-agnostic
Send through any SMTP provider with nodemailer. Rich HTML with plain-text fallback, throttled to your provider's rate. SPF/DKIM guidance built in.
Five layouts, rendered for you
Modal, banner, full-screen, bottom-sheet and custom HTML — all rendered by the SDK, styled from the dashboard. Or take the payload yourself and draw it however you like.
Route users to any screen
Every message can carry a route — a screen name plus key/value params. Your app maps it to its own navigator, so a tap lands users exactly where you want them.
Segments, schedules & triggers
Target saved segments or inline filters, then fire on a schedule, on an event (with delay + cooldown), or manually. Caps and quiet hours are enforced for every recipient.
From zero to first send
No infrastructure to stand up, no delivery costs to Engage. Connect your own providers and go.
Spin up an isolated, multi-tenant workspace and grab a public + secret API key pair.
Paste your FCM service account and SMTP details. Engage verifies with a test send and stores only an encrypted reference — never the raw secret.
Identify users and track events with ~20 lines. Web, React Native (+ Expo), Node — one core, many targets.
Compose push, email and in-app content, pick an audience, set a trigger, and ship — from the dashboard or the API.
~20 lines to integrate
A TypeScript core with thin wrappers for Web, React Native and Node. You keep full control of rendering and navigation — Engage just hands you the message and the route.
import { Engage } from "@engage/react-native";
const engage = Engage.init({
publicKey: "pk_live_…",
userProvider: () => auth.currentUser?.uid,
});
// Identify + track
await engage.identify(uid, { trial_days_left: 3, locale: "de" });
engage.track("opened_paywall");
// Render in-app messages + handle deep links, your way
engage.onInApp((msg) => showModal(msg));
engage.onNavigate((route) => router.push(route));Built right
The principles that shape every line — so you can trust it in production and leave whenever you want.
The Project is the isolation boundary. Every write is scoped by projectId; nothing about one tenant is ever reachable by another.
Each project connects its own FCM and SMTP. Engage sends on your behalf and never owns delivery cost or deliverability.
Credentials never touch the database in plaintext — only a reference, backed by Secret Manager + per-project KMS envelope encryption.
Store and Channel adapter seams mean Firestore→Postgres and Functions→Run are swaps, not rewrites.
FAQ
A project, your own FCM service account and SMTP details, and the SDK. You can be sending push, email and in-app messages the same day — the Starter plan is free up to 1,000 monthly tracked users.
Engage is developer-first and it uses your own FCM and SMTP credentials — so Engage never owns your delivery cost or deliverability, and nothing about one tenant is reachable by another.
A TypeScript core powers thin wrappers for Web and React Native (with an Expo config plugin), plus a Node server SDK. iOS, Android and Flutter wrappers are on the roadmap.
They never touch the database in plain text. Each connection stores only a reference; the secret lives in Secret Manager, encrypted with a per-project KMS key using envelope encryption.
Yes. Engage mirrors the common in-app renderer + deep-link + route-resolver contract, so you can dual-run behind a feature flag and cut over once you're confident.
Start free on the hosted dashboard. Your data, your credentials, your rules.