Email for newsletter creatorsA list that grows without a matching jump in the monthly bill.

The moment most creators notice the pricing model is the same moment the newsletter is working: a good week of subscribes pushes the list past a tier boundary, and the next invoice is higher, whether or not an issue went out that month. The list grew because the writing landed. The bill grew for the same reason, which is an odd thing to be punished for.

Per-subscriber pricing is built around the assumption that a bigger list costs the platform more to serve, which is roughly true for storage and mostly untrue for the part that actually costs money: sending. A list of 50,000 people who get one issue a month generates far less sending volume than a list a tenth the size that gets a daily digest, and a per-subscriber plan charges the first one more.

• Campaigns for the issue itself, sent to a segment or the whole list on whatever cadence the creator actually keeps.
• Automation for a welcome sequence when someone subscribes, and for a paid-tier nudge a few issues in.
• List ownership in the literal sense: the rows, the consent record and the unsubscribe history sitting somewhere the creator controls, not only inside the platform's own database.
• Analytics on bounce and complaint rates rather than open-rate vanity numbers that mail privacy features have made unreliable.

None of that is unusual, and none of it inherently costs more as the list grows. What changes the bill on a rented platform is the pricing model, not the underlying work: sending one issue to 10,000 people and sending the same issue to 50,000 costs a rented platform roughly five times as much in most per-subscriber plans, even though the actual sending cost through infrastructure like Amazon SES scales in a straight line, at around $0.10 per 1,000 emails.

1. Export the current list. A CSV with addresses, custom fields, subscription status, and ideally the consent date and source, from whichever tool the newsletter runs on today.
2. Buy and deploy. SendBunny is $199 once. The one-click Create stack link installs the platform into your own AWS account.
3. Verify the sending domain. The app generates the DKIM, SPF and DMARC records; applying them on Route 53 is one click, otherwise they are pasted into the existing DNS provider.
4. Import the CSV. Uploads run in the background, so a large list is not a problem, and a re-import enriches existing contacts rather than overwriting them.
5. Send inside the SES sandbox, then request production access. The sandbox only delivers to verified addresses, enough to proof an issue before the domain clears AWS's routine production review.

The number that does not appear in that table is a subscriber count on its own, because nothing is billed against it directly. A creator who sends monthly and grows the list without sending more often keeps paying for what they actually send, not for the growth.

Growth changes the stakes of a platform review too. A larger list is a bigger asset to lose if an account gets suspended or a policy review pauses sending, and most rented terms reserve the right to do exactly that without much notice. The address rows, the consent record and the unsubscribe history are the three parts of a list that matter most when something goes wrong, and on a rented platform all three sit in a database the creator does not administer.

Installed into your own AWS account, those same three pieces live in DynamoDB tables under your account, and there is no vendor-side switch that turns the sending path off. AWS still controls Amazon SES and still applies its own rules there; owning the install removes the platform's kill switch, not AWS's.

A brand new newsletter with a few hundred subscribers has little to gain from an AWS account yet. The free or cheap tier of a hosted platform gets the first dozen issues out with less setup, and the pricing tax only bites once the list is large enough for the tier jumps to sting.

The same is true for a creator who wants a hosted signup form with drag-and-drop design, a built-in referral program, or a support line to call when something breaks. SendBunny's transactional and campaign tools cover the sending side; contacts arrive by CSV import or the API, and there is no hosted signup form or referral system bundled in today.