Choose the stack somebody will actually maintain
listmonk is a free open-source application distributed as a binary with PostgreSQL. Sendy is a commercially licensed, self-hosted newsletter application commonly deployed on PHP and MySQL. Both let you run the audience application yourself while sending through an external service.
A team already operating PostgreSQL and containers may find listmonk straightforward to add. An agency familiar with PHP hosting may find Sendy easier to own. That existing knowledge is more valuable than a generic claim that one installation takes five minutes.
Model a 10,000-subscriber newsletter
Assume four campaigns per month, each sent to all 10,000 subscribers: 40,000 recipient deliveries. At Amazon SES's base outbound rate of $0.10 per 1,000, the delivery component is $4/month before data and optional charges.
| Cost | listmonk | Sendy |
|---|---|---|
| Application license | Free, open source | Paid license; check current purchase and upgrade terms |
| 40,000 SES outbound deliveries | $4 base usage | $4 base usage if using the same SES rate |
| Hosting/database | Your deployment cost | Your deployment cost |
| Backups, upgrades and monitoring | Your responsibility | Your responsibility |
Sendy's website advertises a different all-in sending figure per 10,000; do not combine that headline with AWS base pricing as if they are the same cost model. The $4 calculation above is explicitly SES base outbound usage only. Add the exact license, infrastructure and provider bill for your installation.
Segmentation and campaign creation
listmonk exposes SQL-expression segmentation and supports several authoring formats. That can be powerful for a technical team, but someone must own the query logic and validate its recipient set. Sendy provides newsletter, brand and client-account workflows that may suit an agency operating several senders.
Give the person who will send campaigns the same task in both: create a segment of recently active subscribers, exclude unsubscribes, preview the audience and send a test. Confirm that the workflow remains safe when a field is missing or a subscriber belongs to several lists.
Delivery is still a separate operational system
Before sending at production scale, confirm SES production access, regional quotas and domain authentication. Wire bounce and complaint handling back into the application and test it with the provider's supported test facilities. A working SMTP connection does not prove that bad addresses will stop receiving future campaigns.
Back up the database and uploaded assets. Rehearse a restore before an urgent campaign depends on the service. Record which scheduled tasks or long-running processes must be alive and how you will notice if a send stalls.
Migration details that affect real recipients
Transfer subscribed status and suppression records separately from profile attributes. Reconcile list memberships and duplicate addresses. Preserve unsubscribe behavior in old messages, including links tied to the old installation, until you know the destination handles those recipients correctly.
Choose the platform your team can operate for years. If no one wants that responsibility, a managed platform such as Sequenzy is a different ownership choice, even when the visible sending price is higher.
Match the deployment to the person who owns it
listmonk and Sendy both let you operate your own newsletter application, but the maintenance paths differ. listmonk uses a compiled application with PostgreSQL, while Sendy runs in a PHP and MySQL environment. If the team already maintains one stack well, that experience can matter more than a small difference in license cost or interface preference. Identify the actual owner before installing either tool.
Ask that owner to describe an upgrade, a database restore and recovery after the server stops unexpectedly. The answer should include credentials, backups and where operating instructions live. A system that only its original installer understands is fragile even if normal campaign creation feels simple. Choose the stack somebody can keep healthy during an ordinary workweek, including when the main developer is away.
Separate the newsletter application from delivery
The interface selects an audience and prepares messages; the transport provider handles the onward sending path. Sendy is closely associated with SES, and listmonk can be connected to an appropriate delivery configuration. In both cases, validate the actual provider account, sending eligibility, authentication and capacity. Installing the newsletter application does not establish that your provider will accept a 10,000-contact campaign at the required rate.
Document where bounces and complaints are received and how they affect future audience selection. Test that path using controlled examples before sending a production list. If a processing job or webhook fails, make the failure visible and recoverable. A successfully completed campaign in the application should not be mistaken for evidence that every receiving mailbox accepted the message or that every recipient saw it in the inbox.
Compare costs using an operating budget
At 10,000 subscribers and four newsletters a month, the baseline is 40,000 recipient deliveries. Using the published SES base rate of $0.10 per 1,000 outbound emails gives $4 of base sending usage for that workload. It excludes applicable data charges, optional services, hosting, the database and the time spent operating the application. Use that calculation as a component, not a complete monthly invoice.
Add Sendy's current commercial license and upgrade terms where relevant. For listmonk, include the infrastructure and operating work even though the software is free and open source. If your team already has a maintained environment, the incremental cost may be modest; if not, the first deployment has a real setup cost. Record those assumptions explicitly so an apparent saving does not depend on treating engineering time as free.
Rebuild a real audience segment in both tools
Choose a segment you use today, such as active customers who opted into updates and have not received a particular announcement. In listmonk, evaluate the benefit and maintenance implications of SQL-driven segmentation. In Sendy, reproduce the same business rule using its available data and workflow. The important result is that the same intended people are selected and exclusions remain intact.
Inspect the audience before sending, including a small set of contacts deliberately placed near the rule's boundary. A recently cancelled customer, a person missing an attribute and someone who unsubscribed should behave predictably. If the source data comes from an application sync, document how often it updates. A sophisticated segment over stale attributes can target people less accurately than a simple, well-maintained list.
Evaluate the current editor with actual campaign work
Do not base the decision on an old screenshot or a description that predates the current product. Build your regular newsletter with reusable sections, a long headline, mobile images and the unsubscribe area. Send test messages and inspect the result on the clients your readers use. Ask the campaign owner to make a last-minute correction and understand what must happen before sending.
Record which parts require HTML knowledge and which can be handled by the editor. If branded templates are maintained separately, identify where the canonical version lives and how updates reach the application. The team should be able to prepare an issue consistently without copying an outdated version from the previous month. Editor preference matters most when evaluated through the actual recurring task, not an ideal demonstration.
Treat maintenance and privacy as concrete procedures
Self-hosting gives control over the application environment but does not automatically make the complete data flow private or local. Email still passes through delivery providers and recipient servers, and tracking can add additional data collection. Decide what you store, who can access it and how backups are protected. Review the configured behavior rather than assuming the license or deployment model determines the whole privacy posture.
Test a database restore into a non-production environment and confirm that it does not accidentally resume a live campaign. Keep sending credentials separated appropriately and make it clear which environment can email real subscribers. During an upgrade, preserve a recovery path and check scheduled work before allowing sends. Operational discipline is part of the cost of both choices, regardless of how quickly the initial installation completes.
Make migration and rollback recipient-safe
Export custom fields, lists and all relevant exclusion states. Map them explicitly rather than importing only active addresses. Test an unsubscribe after the export but before the new application sends, and decide how that change reaches the destination. Disable the old scheduled campaign before enabling its new equivalent so a normal weekly issue does not get sent twice.
Prefer listmonk when its stack and data-oriented segmentation match your technical ownership. Prefer Sendy when the PHP/MySQL deployment and its newsletter workflow fit the people operating it. If nobody wants to own upgrades, restores and delivery troubleshooting, compare a managed newsletter product as a separate option. A cheap self-hosted application is most useful when running it is a deliberate capability, not an unassigned task discovered after the first failure.
A handover exercise before the first campaign
Have someone other than the installer prepare a draft, identify the intended audience and locate the last backup. They should also be able to explain how the delivery provider reports a permanent failure and where scheduled campaigns are visible. If those tasks require undocumented knowledge, complete the operating instructions before using either application for a significant audience.
Use the exercise to choose between stacks as well as interfaces. A team comfortable with PHP and MySQL may maintain Sendy more confidently; a team already operating PostgreSQL and compiled services may prefer listmonk. Neither preference establishes that the application will take care of itself. Record the upgrade owner, restore procedure and delivery-provider dependencies. With that ownership in place, the comparison becomes a useful decision about data control and editing workflow rather than a gamble that self-hosting will remain effortless after installation.
Sources and scope
Updated November 3, 2026. We publish Sequenzy and have a commercial interest in this comparison. This is a documentation-based evaluation, not a hands-on benchmark or independent ranking. Prices are USD list prices or explicitly labeled calculations; taxes, promotions and optional services can change the total. Confirm the selected plan before purchase.

