Serverless email campaigns as Python code, SQL and Markdown

Motivation

Who is this product for?

Benefits

Next, you can jump straight to the offer or read about the system’s capabilities.

Capabilities

Available campaign types

Broadcast and Sequence can target the entire mailing list only. Additional segments can be implemented by writing YQL queries.

Other types of events can be implemented.

Available email providers

Console-based admin tool

There is a minimalistic admin UI written with Textual that works in a terminal:

Terminal-based UI

Sent messages log

View plain text and HTML versions of sent email messages:

View email message

Push notifications

Get push notifications via Pushover or ntfy when someone subscribes or unsubscribes to your mailing list:

Push notification

Any links in an email body can be wrapped in a tracking tag:

{{ track_link("https://mailgit.app") }}

Clicking on such a link will generate an event, based on which a segment or trigger campaign can be created.

Subscription topics

In addition to the usual subscription status (yes/no), there is support for opt-in and opt-out topics, allowing subscribers to more flexibly manage what they are interested in receiving:

Subscribe to [{{ get_topic("promotion").name }}]({{ topic_subscribe_link("promotion") }}) topic if you want to hear more

Unsubscribe from [{{ topic.name }}]({{ topic_unsubscribe_link(topic) }}) topic, but continue receiving regular emails

There is also the concept of transactional topics for important messages that cannot be unsubscribed from.

Custom subscriber attributes

You can define your own Pydantic class with an arbitrary set of subscriber properties to use for segmentation.

Technical details

Architecture

List of Yandex Cloud services used

Yandex Cloud Services

Codebase stats

The amount of code is quite small:

─────────────────────────────────────────────────
Language                 Files     Lines   Blanks
─────────────────────────────────────────────────
Python                      30      4190      311
Terraform                   12      1227      149
HTML                         9       581       19
Markdown                     4       125       27
YAML                         3       262        4
Autoconf                     1        12        0
Plain Text                   1       103        0
SQL                          1        64        4
gitignore                    1        27        5
─────────────────────────────────────────────────
Total                       62      6591      519
─────────────────────────────────────────────────
Estimated Cost to Develop (organic) $176 285
Estimated Schedule Effort (organic) 7,11 months
Estimated People Required (organic) 2,20
─────────────────────────────────────────────────

Limitations

The offer

There is no formal offer yet, so here are some bullet points:

Here’s how the process of obtaining the product will look like: