Question 1

Can mailtani run a developer newsletter?

Accepted Answer

Yes. Send broadcast issues to your full subscriber list, set up a welcome sequence for new subscribers, embed a signup form on your site or documentation, and manage everything via API if you prefer programmatic control over the UI.

Question 2

Does mailtani have an API for programmatic subscriber management?

Accepted Answer

Yes. The mailtani API lets you create contacts, trigger sequence enrollment, update contact fields, and manage your subscriber list programmatically — useful for integrating with your own tools or automating subscriber management from a CI pipeline or custom dashboard.

Question 3

Can I connect my own AWS SES account?

Accepted Answer

Yes. That is the core of how mailtani works — you bring your own SES, Resend, or any SMTP provider. Your emails go through your infrastructure, your domain, and your IP reputation. No black-box sending pool.

Question 4

How is mailtani different from Buttondown or Substack for developers?

Accepted Answer

mailtani gives you full SMTP control, API access, no revenue cut, and a one-time payment. Buttondown charges monthly; Substack takes 10% of paid subscriber revenue. For developers who want to own their infrastructure, mailtani is the only tool in this space with lifetime pricing.

Question 5

Can I monetise my developer newsletter?

Accepted Answer

mailtani handles the sending layer. For paid subscription tiers, use Stripe or Gumroad and tag paying subscribers in mailtani to send members-only issues to the right segment. There is no platform cut on revenue.

Question 6

What email deliverability controls do I get?

Accepted Answer

Full DNS control: you set your own SPF record to authorise your SES account, configure DKIM for message signing, and set a DMARC policy for your domain. Every technical deliverability decision is in your hands — not delegated to a shared platform.

Question 7

Can I self-host or white-label mailtani?

Accepted Answer

mailtani is a hosted platform, not self-hosted. However, because you bring your own SMTP provider and domain, your subscribers see your domain in every email — not mailtani branding. The sending infrastructure is yours.

Question 8

Is there a free trial for developer newsletters?

Accepted Answer

Yes. mailtani offers a 14-day free trial — credit card required to start, but you won't be charged until the trial ends and you can cancel anytime. Connect your own SES account, import a small subscriber list, and send a test issue to see the full sending experience before committing to the one-time payment.

Question 9

Can I use the same SES account for my newsletter and transactional emails from my product?

Accepted Answer

Yes. This is one of the key reasons developers choose mailtani. Connect your AWS SES account to mailtani for newsletter sends. In your product code, use the SES SDK to send transactional emails — sign-up confirmations, password resets, billing notifications — from the same verified domain. One infrastructure setup covers both, and your domain reputation benefits from all sends combined.

Question 10

Should I use a subdomain for transactional emails vs my newsletter?

Accepted Answer

Yes, as a best practice. Send your developer newsletter from a subdomain like hello.yourdomain.com and transactional emails from mail.yourdomain.com. Both subdomains are verified under the same SES account. This isolates the reputation of each — if transactional volume spikes, it does not affect newsletter deliverability, and vice versa.

Newsletter Platform Built for Developers

Up and Running in Minutes

Transactional + Newsletter SMTP

Newsletter Broadcasts

Welcome Sequences

Deliverability Tools

The Math is Simple

Before & After

mailtani vs the Alternatives

Tired of Paying Monthly?

Not Sure Which Tool Wins?

From the Blog

Common Questions

See How Others Use mailtani

Ready to Get Started?