Listen, I get it. At one time I was writing a poetry newsletter, a Python newsletter, and a very-niche but high-engagement Miami Heat data science newsletter. Logging in and out every time I wanted to check out a new subscriber or edit a piece was a pain.
Thankfully, Buttondown is a little more friendly. Switch between newsletters easily, get a single bill, and don't worry about anything besides your great content.
Amazing people like Mandy Brown take advantage of this by having two newsletters, one for her personal writing and one for her professional writing and coaching:
I’m also running two newsletters now—the second is for my coaching practice, everything changes—and being able to manage both of them with one tool is very powerful. I’ve been able to take what I’ve learned from doing AWL and apply it to how I’m approaching things with the coaching practice, and vice versa.
I'm not a fan of the "gotcha" pricing model. I don't want to have to worry about how many subscribers I have, or how many emails I send, or how many emails I receive. I just want to pay a fair price for a great product.
We priced multiple newsletters that way, too — you're billed for the total number of unique subscribers across all your newsletters. That's it. No worrying about how many emails you send or receive, no worrying about how many newsletters you have. Just a simple, fair price.
If you're a developer, you might not be thinking about just one or two newsletters — you might be thinking about dozens of newsletters. Buttondown has a full-featured API that lets you do everything you can do in the web interface, but programmatically — including spinning up newsletters.
You can learn a bit more about the API here.