Notifuse

What Notifuse is

Notifuse (github.com/Notifuse/notifuse) is a self-hosted emailing platform written in Go with a React admin console. It covers three jobs that usually live in three different products: broadcast campaigns to a subscriber list, multi-step automations that decide who gets what and when, and a transactional API your app calls when someone resets a password or finishes a purchase. Contacts, lists, custom fields, open and click tracking and an embeddable notification centre all sit in the same PostgreSQL database.

The thing to understand before you evaluate it is that Notifuse is a control plane, not a mail server. Sending is delegated to a provider you bring, which the repo lists as Amazon SES, Mailgun, Postmark, Mailjet, SparkPost, SendGrid or SMTP. Your per-email cost is therefore that provider's cost rather than a seat price, and your sending reputation is still yours to earn. Templates are authored in a drag-and-drop MJML builder with Liquid variables, so a campaign and a receipt can share the same components instead of drifting into two visual languages.

The automations are a graph rather than a list. Each one is a canvas of nodes hanging off a single trigger, and the node types the repo documents are delay, email, branch, filter, add to list, remove from list, A/B test, webhook, and a branch on a contact's status in a given list. A contact can be enrolled a single time or every time the trigger fires, each enrollment carries its own state and per-node history, and an automation can be edited as a draft and then published — a paused one holds its enrollments rather than dropping them. There is also a paid hosted plan for anyone who would rather not run it.

Where it fits in a founder's stack

The honest way to place Notifuse is against the tools that already do part of its job, because most founders arrive at it already running one of them.

• Instead of a newsletter tool listmonk is the closest single-purpose comparison — lists, campaigns, one Go binary — and it is the simpler thing to operate if broadcasts are all you need. Notifuse adds the automations and the transactional API on top, at the cost of a larger surface to run.
• Instead of a marketing-automation suite Mautic has far more history and a much bigger feature set for segmentation and multi-channel campaigns. Notifuse is the smaller, newer, quicker-to-stand-up option, and it is email only.
• Alongside your product's notifications Novu is notification infrastructure spanning email, SMS, push and an in-app inbox. If you need channels beyond email, that is the different tool. If email is the whole job, Notifuse covers both halves of it.
• Not instead of an editor component React Email Editor drops an email builder into your own product so your users can design. Notifuse's builder is for you and your team, inside its own console.

One recent addition is worth flagging because it is unusual: with the v38.0 release in August 2026 the project absorbed a cookieless web-analytics feature — engaged-time sessions, editable channel-attribution rules, goals and custom dimensions — running on the same PostgreSQL instance rather than a second database. The idea is defensible, since campaign attribution is exactly where email and site analytics meet, but it also means your mail platform now owns a second category of data and a second set of upgrade risks. Treat it as a bonus to test, not as a reason to pull out Umami or PostHog on day one.

Two lines in the repo to read twice

The first is the licence. Notifuse is AGPL-3.0, which is unremarkable if you run it for your own business, but it is copyleft with a network clause: modify it and offer the modified version to others as a service, and those modifications are in scope. That is a decision to make before you build on it, not after you have shipped something that embeds it.

The second is the contributing section, which states plainly that the project does not accept pull requests and that unsolicited ones are closed without review, while issues are welcomed as the way to help. That is an unusual stance for an AGPL project, and naming it is not a criticism — it is a cost to price in. You may fork and modify freely, but a fix you write is unlikely to land upstream, so a bug you care about becomes either an issue you file and wait on, or a patch you carry yourself through every upgrade.

Owning the pipes is not the same as filling them

Self-hosting your email removes a per-message bill and a vendor's data policy from your life. It does not write the welcome sequence, decide which few moments in a customer's first week deserve a message, or notice that your trial-expiry note is going to people who structurally cannot act on it. That work is identical whether the platform is yours or rented, and it is where the results actually come from — lifecycle email is the discipline, and the tool is only where it runs.

Nor does owning the platform make the mail arrive. Deliverability follows your domain and your sending behaviour rather than your software: authentication records, a warmed sending domain, clean lists, and a complaint rate somebody watches. The ladder that keeps outbound out of the spam folder is the same ladder for mail people asked for, and it is laid out in how to write cold emails that don't get marked spam. One transactional message deserves separate attention: if it carries a login link, the failure mode is not delivery at all but who opens it first, which is why magic link logins fail. AgentCeres — the AI Growth Officer at agentceres.com — sits on the execution side of that line: it drafts the sequences and campaigns and routes anything outbound to a human for approval before it sends.