Resend Automations, or fromHello on top of Resend
Resend Automations sends email sequences from your events. fromHello can send through Resend, adding segments updated on every event, SMS, in-app and web push.
The short answer
Updated
Resend Automations and fromHello both send email sequences triggered by events, and they can run together: fromHello can send through Resend, one of its five email providers. Resend Automations lives inside Resend, next to the sending: your app sends an event, and a workflow of delays, waits, conditions and templated emails runs for that contact, with 10,000 runs a month included on every plan. fromHello is open-source marketing automation on top of the provider: first-party tracking, segments re-evaluated on every event, journeys with 14 node types, and channels beyond email, self-hosted under AGPL-3.0 or on fromHello Cloud, in early access. If your lifecycle is a few email sequences your code triggers, Resend Automations is the simpler choice. If you need more than email, or segments that follow behavior, that's fromHello, with Resend still sending.
Choose fromHello if
you want segments that follow behavior and journeys across email, SMS, in-app, web push and ad audiences, with Resend still doing the sending.
Choose Resend Automations if
your lifecycle is email sequences your code triggers, and you want them in the same account, API and bill as your sending.
Sequences inside your sender, or journeys on top of it.
| fromHello | Resend | |
|---|---|---|
| Event-triggered sequences | fromHelloJourneys, 14 node types | ResendDelays, waits, conditions, emails |
| Where events come from | fromHelloFirst-party snippet + API | ResendYour app, via API, SDKs or CLI |
| Segments | fromHelloRe-evaluated on every event, + static | ResendGroups you add contacts to |
| SMS, in-app, web push, ad audiences | fromHelloBuilt in; SMS via your provider | ResendNot offered: email only |
| Replies | fromHelloLand on the profile; can start a journey | ResendInbound email, to your webhook |
| One-off broadcasts and newsletters | fromHelloNot offered | ResendBroadcasts, priced by contact |
| Transactional email API | fromHelloNot offered | ResendIts core product |
| Email sending | fromHelloThrough your provider, Resend included | ResendIts own API and SMTP relay |
| AI — agents, assistant, MCP | fromHello59 MCP tools + assistant | ResendAI builder + MCP server |
| Open source | fromHelloYes — AGPL-3.0 | ResendHosted service; open SDKs |
| Self-hostable | fromHelloYour infrastructure | ResendCloud only |
| Pricing | fromHelloCloud from €39/ | Resend10,000 runs/ |
| Availability | fromHelloCloud in early access | ResendGenerally available |
Resend facts checked on 13 October 2026 against its own pages, listed under Sources; Resend Automations launched on 13 April 2026. fromHello sends email through Resend, Postmark, SendGrid, SMTP or Microsoft 365. fromHello Cloud is in early access through the waitlist. fromHello prices are in euros, excluding VAT.
Automation inside the sender, or a layer on top of it.
Resend Automations puts lifecycle email next to the sending. Your app sends a named event with a contact's ID or email address, and every published automation with a matching trigger runs for that contact: delays of up to 30 days, waits for another event, conditions on event or contact data, and emails built from your Resend templates. You build it in a drag-and-drop editor, from a plain-language prompt, or through the API, SDKs, CLI and MCP server, and every run is logged. For email sequences your code triggers, it's simple and inexpensive, and it sits right beside your sending.
fromHello starts a layer up. A first-party snippet tracks what people do, segments are re-evaluated on every event, and journeys with 14 node types act on them across email, SMS, in-app banners and modals and ad audiences, with web push built into the platform. Replies land on the contact's profile and can start a journey. Your own AI plugs in over MCP, with 59 tools for segments, journeys, templates and analytics, and a journey it builds stays a draft until it is published.
It doesn't replace Resend. fromHello sends email through Resend, Postmark, SendGrid, SMTP or Microsoft 365, and its Core plan runs on your own providers, so the Resend account you already have keeps doing the sending. The choice is where the automation lives: inside Resend, for email, or in fromHello, across channels. If you're also weighing an all-in-one email platform for SaaS, fromHello vs Loops covers that one.
Open source, on top of Resend. What it is, and what it isn't.
Resend's SDKs, React Email and its MCP server are open source; the platform itself runs as Resend's hosted service. fromHello is open-source marketing automation under AGPL-3.0: run it on your own servers, with Postgres, Redis and your own email provider, Resend included, or use fromHello Cloud, in early access.
Running both is the point. Resend keeps your sending domains and delivers the mail; fromHello decides who gets which message, on which channel, and when.
What fromHello is
- Open source under AGPL-3.0: self-host it, or use fromHello Cloud, in early access.
- Journeys with 14 node types, triggered by what people do, on segments re-evaluated on every event.
- Email through Resend, Postmark, SendGrid, SMTP or Microsoft 365, SMS through your own provider, in-app banners and modals, web push, and Meta, LinkedIn and Google audiences.
- A two-way inbox: a reply lands on the contact's profile and can start a journey or wake one.
What it isn't
- Not an email API: password resets and receipts stay on Resend's API.
- No newsletters or one-off broadcasts: Resend sends Broadcasts; fromHello reaches many people through journeys.
- No store, cart or order integration, and no mobile push.
- Not generally available: fromHello Cloud is in early access.
The honest part
Where Resend wins
Resend Automations is young, and it does what it set out to do well. For a lot of teams, it's all the automation they need.
One vendor: sending, broadcasts and automations share one account, one API key and one bill, with no second tool to wire in.
The price of starting: every plan includes 10,000 automation runs a month, the Free plan included, and paid plans pay $0.0015 a run beyond that.
Its developer experience: nine official SDKs, a CLI, a hosted MCP server and React Email, with automations and events created, and runs inspected, through the API.
It's generally available, with SOC 2 Type II, and it also sends one-off broadcasts, which fromHello doesn't; fromHello Cloud is in early access.
Billed by run, or by reachable contact.
Resend Automations comes with every Resend plan: 10,000 runs a month, then $0.0015 a run on paid plans, on top of the plan that pays for your sending. Resend's pricing page, checked on 13 October 2026, lists transactional email free up to 3,000 emails a month, at 100 a day, and Pro from $20 a month for 50,000. Marketing plans for broadcasts are billed by contacts, not sends: free up to 1,000 contacts, then from $40 a month for 5,000. Self-serve plans are billed monthly. fromHello Cloud starts at €39 a month excluding VAT on Core, which sends through your own providers, Resend included, so Resend keeps billing the sending; Team, from €59, adds bundled email and AI credits. Every plan counts billable contacts as a daily mean. fromHello Cloud is in early access through the waitlist, and self-hosting under AGPL-3.0 is free.
fromHello — Cloud from €39/
Resend — 10,000 automation runs a month on every plan, then $0.0015 a run; sending free up to 3,000 emails a month.
Questions
What teams ask before they choose
Does fromHello work with Resend?
Yes. fromHello sends email through Resend, Postmark, SendGrid, SMTP or Microsoft 365. On the Core plan you bring your own email and SMS providers, so the Resend account you already use keeps doing the sending, and Resend keeps billing it. fromHello adds the layer on top: tracking, segments re-evaluated on every event, and journeys across email, SMS, in-app, web push and ad audiences.
What can Resend Automations do?
Start a workflow when your app sends a named event for a contact, then run delays of up to 30 days, waits for another event, conditions on event or contact data, emails from your Resend templates, and contact steps such as adding someone to a segment or updating a field. You build it in a drag-and-drop editor, from a plain-language prompt, or through the API, SDKs, CLI and MCP server. It launched on 13 April 2026, and its messages are email.
Should I use Resend Automations or fromHello?
If your lifecycle is a handful of email sequences your code triggers, Resend Automations is the simpler choice: one vendor, and 10,000 runs a month included. If you need segments that follow behavior, SMS, in-app, web push or ad audiences, replies that land on a profile, or code you can self-host, fromHello does that, with Resend still sending your email.
Is there an open-source alternative to Resend Automations?
fromHello is open-source marketing automation under AGPL-3.0, and it can send through Resend, so it is an alternative to the automation, not to the sending. Self-host it, or use fromHello Cloud, in early access. Resend's SDKs, React Email and MCP server are open source too; the Resend platform runs as a hosted service.
How does pricing compare?
Resend Automations comes with every Resend plan: 10,000 runs a month, then $0.0015 a run on paid plans, plus the plan that covers your sending, free up to 3,000 emails a month. fromHello Cloud starts at €39 a month excluding VAT for 2,500 contacts on Core, which can send through your own Resend account; Team, from €59, adds bundled email and AI credits. Core and Team are month-to-month up to 20,000 contacts, and deleted, anonymous and suppressed contacts never count.
Does the AI send anything without my approval?
No AI tool in fromHello sends a message, but AI actions can change live journeys without a confirmation step. A journey your AI agents build stays a draft until it is published. Publishing, pausing or deleting through an agent takes a confirmation step in your AI client. Other edits, such as changes to a segment or a template, apply when saved. Opt-in send-time personalization rewrites each email without per-message review. If the AI fails, the send waits by default.
How do I get started with fromHello?
Two ways. fromHello Cloud is in early access through the waitlist: spots open in stages, with hands-on onboarding, and we help you get set up and bring your contacts over. Or self-host fromHello under AGPL-3.0, on servers and providers you run.
Sources Checked
- Resend — Introducing Automations, 13 April 2026 (opens in a new tab)
- Resend — Pricing (opens in a new tab)
- Resend — Pricing, Markdown version (opens in a new tab)
- Resend docs — Automations (opens in a new tab)
- Resend docs — Automation steps (opens in a new tab)
- Resend docs — Automation trigger (opens in a new tab)
- Resend docs — Managing Segments (opens in a new tab)
- Resend docs — MCP Server (opens in a new tab)
- Resend — Open source (opens in a new tab)
Keep comparing
All comparisons- Head-to-headfromHello vs LoopsLoops does SaaS email beautifully; fromHello adds SMS, in-app, web push and ad audiences, open source.
- Head-to-headfromHello vs Customer.ioThe same event-triggered journeys, on open-source code you can self-host.
- Head-to-headfromHello vs KnockKnock is closed messaging infrastructure; fromHello is open-source marketing automation.
- Switching toolsHow to switch email platforms without losing deliverability
Early access
fromHello Cloud
You didn’t start this to stay small.
Early access to fromHello Cloud opens in stages. Onboarding is hands-on: we help you get set up and bring your contacts over.
Not ready to join? View on GitHub