Just answer three questions, and your notification is live.
When to notify
Pick a table and an event (INSERT, UPDATE, or DELETE). Add conditions to fire only when the row matches your rules.
Who to notify
Point to the user ID. A direct column, a joined table, or broadcast to everyone. Add filters to narrow it down.
What to send
Write the title and body. Use {{ for dynamic values from the event record. Choose which fields go into the payload.
One-time setup, then notifications run on autopilot.
On the web
Connect Supabase, add your FCM and APNs credentials, and you're set. Nothing else to wire up.
In your app
Install, initialize, register on login, unregister on logout, listen for events. That's the code part.
npm install @entrig/react-native
# iOS setup
npx @entrig/react-native setup ios
Everything you need to send push notifications from day one.
No code
Create and manage notifications from the dashboard. No SQL, no backend code.
Devices
Device tokens are managed automatically. Just call register/unregister from the SDK.
Reliability
Transient FCM and APNs failures are retried. Every notification gets another chance.
Alerts
Get alerted when a notification fails because of a configuration error. Nothing breaks unwatched.
Agentic
Connect your AI agent via MCP. Create and manage notifications in natural language.
Observability
Track delivery status for every notification you send.
Start sending for free. Scale as your user base grows.
Get started with push notifications
notifications / month
No credit card required
For growing apps with more users
notifications / month
For apps at scale
notifications / month
No. We designed Entrig around the tables you already have. Select the table that represents the event (likes, comments, orders, messages, whatever it is), and a trigger will call Entrig the moment a row changes. No new tables, no extra writes from your code.
If you prefer to have a notifications table, that works too. Make it your event table, and we send a push every time a row lands in it.
What about data from related tables? This is usually where developers end up writing backend logic. Joining the user, fetching the post title, looking up the team. Entrig handles it for you. Configure the foreign key paths in the dashboard and we follow them at send time. You configure once, we resolve the data on every send.
Book a 15-minute call. We'll connect your Supabase, configure your first trigger, and answer anything you're stuck on.