Note: this isn’t the technical guide for the stack, if you want to see the nitty-gritty technical aspect head to the dev.to guide I’ve created 🚀
A few months ago I decided to pull the trigger and start a newsletter. I’ve been reading trends.vc for a while and found it to be an amazing information source for general business-related trends. The problem was, that I couldn’t find a good resource for developer trends. I knew about daily.dev and a few others, but none of them gave a value-packed drill-down of one specific developer trend each time, every few weeks.
So I decided to create one. If by any chance the newsletter sounds interesting, you should probably check it out here: unzip.dev (oh, and it’s totally free 💝)

Back to our topic, creating the newsletter.
To run unzip.dev I wanted to create a sustainable way to produce my newsletter and not worry about consuming my life with deployment IT. And, all this had to happen fast. I wanted to get something out the door quickly to check the viability of my idea.
Most known newsletter providers did not appeal to me pricing-wise. They can cost over > $100s of dollars a month for a relatively modest amount of subscribers. I needed something that would cost $5-30 a month, as I just quit my job to start unzip and a few other services.
The following setup includes:
✅ An Open-source newsletter system
✅ Zero-downtime, CI & CDN for the newsletter website
✅ $7/mo (can be $0 if you can bear a shared cpu)
✅ Mail link tracking for analytics
✅ Open-source website analytics
✅ Automatic welcome email for new subscribers
To achieve all this goodness, I converged on the following stack:
If you want to check out the nitty-gritty implementation, head on over to dev.to, where I wrote a more in-depth guide on how to tie all of those systems together so you can run your own newsletter.
If you just want to start out and don’t want to waste time on the technical aspect or you don’t feel comfortable configuring it, you might want to check out:
I’d be happy to retweet any newsletter you create using this stack, so don’t hesitate to mention me and I’ll publish it along :)
If you have any other question, please comment or contact me via Twitter @agammore.
Really well documented post. I'll be sure to try out this stack in the future.
Thank you! A small thing to note, use MySQL instead of SQLite as Ghost are deprecating SQLite from production usage.
Ah, thanks for the heads up!
Sometimes I do not understand why there is no response... especially when it is a solid, elaborate and well-documented post. Like this one 👆🏻
Love your reasoning and decision-making. Think that indeed there is room for this, it's a good niche. Trust that the
dev.tocommunity is helping the growth of the readership.Only path you also could have considered, especially with the topic is Hashnode, which has a built newsletter service as well.
Yeah, I just found out about it after already committing to my stack. They look great, but I still like that I control all of my deployment (with the ups and downs). But, I'll look about migrating if they tick my boxes (custom landing page, integromat and reasonable future pricing).
P.S. Thanks for the reply, I really appreciate it!
More than welcome!
Forgot to mention: Your main/signup page is 🔥🔥🔥🔥🔥!!!
Thank you! <3 I've put too much work into it :)