Transactional email that actually arrives.

Free covers 5,000 emails a month (up to 200 a day) with no card. Starter is $15 a month for 50,000, Growth is $29 for 100,000, and Scale runs from $129 for 200,000 to $899 for 2,500,000. It is a separate subscription from Warmerly's outreach plans: you can have either, both or neither.

One email is one recipient. A message sent to one address counts once; the same message to one address in to and two in cc counts three times. Recipients skipped because they are on your suppression list do not count, and neither does an email that fails on Warmerly's side before it is handed to the recipient's mail server.

Nothing is charged unless you switch overage on. Without it, you can go 10% past your monthly allowance free, so an unexpected spike does not stop password resets mid-month; past that, sends are refused until the next month or until you upgrade. With overage switched on, extra email costs $0.60 per 1,000 on Starter and Growth, falling to $0.35 on the largest Scale plan.

Inbox providers judge mail partly by where it comes from and by the domain behind it. If password resets shared a sender with a cold campaign that drew complaints, the resets would pay for it. Warmerly's outreach and warmup run on your mailboxes; your app's email runs on separate transactional infrastructure, and the two never share a sending server or a domain.

On price, yes: at every published volume Warmerly costs less (for example $29 against $35 for 100,000 emails a month, as of September 2026), the free plan is larger, and overage is cheaper and opt-in. Resend is the better pick today if you need an SMTP relay, delivery webhooks, templates or open and click tracking, which Warmerly does not have yet, or official SDKs in many languages; Warmerly is a REST API.

Yes. The transactional email API is covered by a 99.9% monthly availability commitment. If Warmerly misses it, you get a service credit on that month's transactional fee: 10% below 99.9%, 25% below 99.0%, 50% below 95.0%. Request it within 30 days by emailing support@warmerly.com. The full terms, including what is excluded, are in section 18A of the Terms of Service.

Email your application sends to one person because of something they did: a password reset, a sign-in link, a receipt, a notification. It is expected and time-sensitive, unlike marketing or cold outreach, which is why it should never share sending reputation with them.

Transactional sending infrastructure in the EU, separate from everything else in Warmerly: it never carries cold outreach or warmup. Each workspace is isolated, so a workspace whose bounce or complaint rate gets too high is paused on its own without affecting anyone else.

A few, all shown in the dashboard ready to copy: three DKIM CNAMEs, an MX and an SPF TXT on bounce.yourdomain (where bounce reports are received), and a DMARC TXT. None of them touch your domain's own inbound mail. The only MX is on bounce.yourdomain, so your mailboxes keep receiving exactly where they do today, and your existing SPF record is left alone.

Use a domain or subdomain you don't send cold outreach from, such as mail.yourcompany.com. Warmerly refuses a domain that is already used for anything else in Warmerly. A subdomain of a domain that already receives mail is ideal.

The complaint is reported back to us, the email's status becomes complained, and the address is added to your workspace's suppression list, just like a hard bounce. Later sends to it are skipped and recorded as suppressed.

Yes, on any Scale plan, for $29 a month. Most apps don't need one: a dedicated IP's reputation rests on your own sending alone, so it suits senders with high, steady volume. Everyone else is better served by the shared sending infrastructure, where each workspace is still isolated from every other.

3 on Free, 10 on Starter, 25 on Growth and unlimited on Scale. Every domain has to pass SPF, DKIM and DMARC before it can send, and its records are re-checked automatically after that.

If you want to send without building the parts around the sending yourself, yes: domain verification with ready-to-copy DNS records, bounce and complaint handling, a suppression list, retries and a delivery timeline for every email come with it. If you only need raw sending at the lowest possible price and have engineers to build that plumbing, sending through SES directly, at $0.10 per 1,000 emails, is cheaper.

Not yet. Sending is through the REST API, which any language that can make an HTTP request can call. An SMTP relay, delivery webhooks to your app, templates and open/click tracking are on the roadmap.