Questions, answered

Same engine, new front door. The API sends transactional and marketing email programmatically. Publish gives you a blog, a subscribe flow, and a newsletter on top of that same permission and reputation engine.

Because deliverability is what we do. GoodSender comes from the team behind SendGrid, and it sends on Laneful, enterprise infrastructure from that same team, so the deliverability is ours to own rather than rent. Every list is double opt in and self cleaning, which is what keeps one shared pool healthy enough to carry every sender on it.

Yes, over the same API. Receipts, password resets, and alerts go out on the same engine and the same sending reputation as your newsletter, from a catalog of ready templates you can brand with your own colors. Transactional mail is not marketing, so it does not run through the subscribe flow. It is one vendor and one integration instead of two.

Ghost rents its email and prices per member and per seat. We own the deliverability, price in flat send based bands (free for most, then $10 a month), and there's nothing to self host. Ghost is built for paid publications. We're built to get your marketing, and your transactional email, into the inbox.

Claude Code, Claude Cowork, Codex, or any other AI agent. Connect it over the GoodSender MCP server or the API, and every action in the app becomes a tool it can call. Nothing separate to learn.

Just GoodSender, over the MCP server or the API, with the same permissions you have. It can draft, publish, manage subscribers, and send. Every agent post carries its provenance: which agent, which repository, which commits. One action takes it down.

Yes, with autosend on. Your agent drafts, publishes, and sends the issue end to end. It reaches confirmed subscribers only, and every post keeps its provenance: which agent, which repository, which commits.

No. The editor, subscribe forms, and sending all work by hand, and plenty of teams start that way. The agent is how the blog keeps running when you stop finding the time.

Because the audience and the SEO equity should be yours from the first post. There are no goodsender subdomains. Connect your domain, publish under your name, and take everything with you if you ever leave.

They can read them, which is the part we control. Every post is served as fast, server rendered HTML on your own domain, with clean URLs, canonical tags, a sitemap, and an RSS feed, so a crawler gets the text itself rather than a JavaScript shell it has to run first. That is what both classic search and AI search ingest, and because the domain is yours, whatever authority builds up stays with you.

No, and that's deliberate. We're for businesses that make money from their product, not from the newsletter. If you want paywalls and ads, another tool will fit you better.

Either. Write in the editor, or publish and send over the API or MCP. The product is fully programmable.

After 120 days of no engagement we ask them to re confirm. People who don't are suppressed. That's how your list stays clean and your reputation stays high.

Your list, yes: import your subscribers in bulk. Engaged subscribers come straight into our permission and engagement model, and the quiet ones get a re opt in before we send them anything, so an old list gets re confirmed rather than blasted. Your posts: the editor is markdown, so a post pastes in cleanly, but a bulk post importer is not built yet.

Per subscriber pricing was always a packaging choice, not a cost. We charge for what you send, in flat bands, and the free tier covers most businesses. Even our paid rate is well under raw infrastructure like Amazon SES.