When. Who. What.
Just answer three questions, and your notification is live.
When to notify
Table + event + conditions
Pick a table and an event (INSERT, UPDATE, or DELETE). Add conditions to fire only when the row matches your rules.
Who to notify
One user, a group, or everyone
Point to the user ID. A direct column, a joined table, or broadcast to everyone. Add filters to narrow it down.
What to send
Title, body, and payload
Write the title and body. Use {{ for dynamic values from the event record. Choose which fields go into the payload.
Setup in minutes.
One-time setup, then notifications run on autopilot.
Databases
Connect Supabase
Connect Supabase securely with OAuth. Add up to 3 projects as environments.
Channels
Set Notification Channels
Add FCM and APNs credentials for Push. Configure SES, Resend, or Mailgun for Email. And you're set.
In your app
A few lines of code
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
Database Access
Not comfortable connecting your database?
We connect to your Supabase via OAuth. Simple, secure, and one-click.
If you don't want to connect your database, there is another way using the Supabase MCP and Entrig MCP servers together. It requires extra setup on your end depending on your use case. Share what you are building and we will guide you through it.
Tell us about your requirements
Boring infrastructure, handled.
Everything you need to send notifications from day one.
No code
Visual creator
Create and manage notifications from the dashboard. No SQL, no backend code.
Devices
Token management
Device tokens are managed automatically. Just call register/unregister from the SDK.
Reliability
Retry system
Transient FCM and APNs failures are retried. Every notification gets another chance.
Alerts
Failure alerts
Get alerted when a notification fails because of a configuration error. Nothing breaks unwatched.
Observability
Delivery report
Track delivery status for every notification you send.
Agentic
MCP server
Connect your AI agent via MCP. Create and manage notifications in natural language.
Math is simple
You're paying for the time and effort saved. That's the value.
Free
The starting point to fall in love.
- 3,000 notifications / month
- Push + email (BYO provider)SES · Resend · Mailgun
- 1 Supabase project
- Visual creator
- Token management
- Automatic retries
- Failure alerts
- MCP server
- 3-day delivery report
Pro
All you need to go without limits.
- Unlimited notifications
- Push + email (BYO provider)SES · Resend · Mailgun
- 3 Supabase projectsConnect up to 3 Supabase projects and deploy notifications across them
- Visual creator
- Token management
- Automatic retries
- Failure alerts
- MCP server
- 30-day delivery report
Custom
Tell us your story.
We built Entrig based on our own pain points while developing apps. We kept doing the same setup across multiple apps and wanted to make it simpler, that's our story. Tell us yours — what do you need more of, or what's the tedious setup you want Entrig to handle?
Frequently Asked Questions
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.
Let's get your first notification live.
Book a 15-minute call. We'll connect your Supabase, configure your first trigger, and answer anything you're stuck on.
Entrig