iglo.email

Email to your users, from your own server.

iglo.email is planned to send newsletters, transactional email and event-triggered sequences from one executable. Today it is a skeleton: an HTTP server and a SQLite database.

iglo.email is an independently maintained rewrite derived from listmonk v7. It keeps listmonk's product model (subscribers, lists, campaigns, templates, transactional email) and adds what listmonk does not plan to have: event-triggered email sequences, unsubscribe-aware transactional email, a per-subscriber frequency cap, a send log and outbound webhooks.

Built and planned.

1. 01
   One executable, an HTTP server with /health, and a SQLite database.
2. 02
   Planned Subscribers, lists, single and double opt-in, segmentation queries.
3. 03
   Planned Campaigns with scheduling, throttling, tracking and bounces.
4. 04
   Planned A transactional email API that respects unsubscribes and returns message IDs.
5. 05
   Planned An events API and email sequences (wait 3 days, then send X if Y did not happen).
6. 06
   Planned A server-rendered admin UI.

Run it.

There is no stable release. To try the skeleton, install Bun 1.4 or newer and build from source:

git clone https://github.com/iglo-tech/iglo.email.git
cd iglo.email
bun install --frozen-lockfile
bun run build
./dist/iglo.email serve

It listens on 127.0.0.1:9000 by default. Flags: --port, --host, --data-dir, --root-url. For production, backups and restores, see the operations guide in the repository.

Read more.

• Operations guide ↗
• Why iglo.email exists ↗