Send emails when your data changes—no code, no Zapier.
Connect your database, set rules, pick a schedule. Emails go out via your existing provider. Built for product and ops teams who own the data and want to own the automation.
Join early access — free during beta
You're stuck in the middle
You need to email users when something happens in your product or ops—trial ending, threshold hit, shipment delayed. Engineering is backlogged. Marketing tools are for campaigns, not product events. So you either wait on a ticket, pay for complex workflows, or hack something in a spreadsheet. Result: slow rollout, brittle processes, and you don't fully own the logic.
Sound familiar?
- "We need to notify users when X happens—dev said two sprints."
- "We're using Zapier but our source of truth is the DB."
- "We built a one-off script; now nobody wants to touch it."
Emails from your database, on your terms
This is product- and ops-driven email: trigger sends from your own data and rules, not from a CRM or campaign calendar.
How it works:
- Connect — Read-only access to your database (Postgres, MySQL, etc.).
- Define — Conditions in SQL or a simple visual rule builder.
- Schedule or trigger — Cron, webhook, or event.
- Send — Through your current provider (SendGrid, Postmark, SMTP, etc.). You keep deliverability and branding.
No custom backend code for "notify when X." No dragging nodes for something that's really "when this query returns rows."
"If you can query it, you can email on it."
Built for product and ops workflows
Typical uses:
- Product: Trial ending soon, feature adoption milestones, usage thresholds, activation nudges.
- Ops: Order/shipment status, approval requests, inventory or capacity alerts, SLA reminders.
- Internal: Daily/weekly digest from a query, anomaly alerts, report-to-inbox.
One tool: read from the DB, evaluate rules, send via your stack. No duplicate "source of truth" in a marketing platform.
Right fit, wrong fit
For
- SaaS founders and product managers who want to ship "email when X" without a dev ticket.
- Lean teams that treat the database as the source of truth.
- Teams that already have an email provider and want to keep using it.
Not for
- Newsletter or broadcast campaigns (use a marketing tool).
- Full CRM and lifecycle campaigns (use a CRM).
- Teams that need writes back to the DB or complex multi-step workflows (consider automation platforms or custom code).
If "when this query has results, send this email" is your mental model, this is for you.
Why not Zapier, custom code, or a marketing tool?
| Option |
Limitation |
| Zapier / no-code automation |
DB isn't the native source; you sync or poll. Complexity and cost add up when the real logic is "run this query." |
| Custom backend |
Works, but every new trigger is code, tests, and deploy. Slow and ties you to engineering. |
| Marketing / CRM tools |
Built for campaigns and lists, not "when a row in our DB matches this." You end up pushing data in just to trigger one email. |
| This |
Read-only DB → your conditions (SQL or rules) → your schedule/trigger → your email provider. You get speed (no backlog), ownership (rules in one place), and leverage (one setup, many use cases). |
Get early access
We're onboarding a small group of teams to shape the product. Early users get:
- Free during beta — No charge while we're in early access.
- Direct input — Roadmap and features influenced by your workflows.
- Setup support — We help you connect and get your first automation live.
No credit card. We'll reach out within a few days.
Quick questions (optional)
Help us build what you need. Two minutes, optional.
- What's the first "email when X" use case you'd set up? (e.g. trial ending, threshold, shipment update)
- Where does your product/ops data live today? (e.g. Postgres, MySQL, BigQuery, Snowflake, other)
- Which email provider do you use or plan to use? (e.g. SendGrid, Postmark, Resend, AWS SES, other)
- Team size: just you / 2–10 / 11–50 / 50+
Thanks. This directly influences what we build next.