[tommasoamici]

I run a few instances of listmonk [0], what makes fertit different/better?

One thing I don’t particularly like about listmonk is that it doesn’t really support multitenancy. It’s lightweight enough that I can spin up multiple instances for different domains, but it’d be nice not to.

https://listmonk.app/

[rasadov]

Multi-tenancy is exactly what Fertit was built to solve. But it is available only in Fertit hoster service, not the open-source version at the current moment. Listmonk is excellent - we actually considered building on top of it initially. The main differentiators: Multi-tenancy (your pain point): Native support for multiple newsletters/domains in one instance Unified management across all your properties

Positioning differences: Listmonk: Power-user tool with SQL segmentation, advanced templating, high-throughput queues Fertit: Simplified interface targeting small businesses who want "just works" newsletter management

Architecture approach: Listmonk: Single binary + PostgreSQL (requires more ops knowledge) Fertit: Docker Compose setup with Redis for caching, designed for easier deployment

Business model: Open-source version addresses your self-hosting needs Hosted service ($5-10/month) for users who want zero ops

When you'd choose Fertit over Listmonk: You manage newsletters for multiple clients/domains (multi-tenancy) You prefer simpler UI over advanced segmentation features You want commercial support option You're hitting operational complexity with multiple Listmonk instances

When you'd stick with Listmonk: You need the advanced features (SQL queries, high-throughput queues) Current multi-instance setup works fine for your scale You prefer the mature, battle-tested codebase

Would love your thoughts on the multi-tenancy approach - is that the main friction point you're hitting with multiple instances?