SendForever manages Amazon SES in your AWS account: one app for domains, templates, audiences, campaigns, activity and alerts.
Pay $99 once. AWS bills $0.10 per 1,000 emails.
Each provider’s cheapest plan for the volume. SendForever adds $99 once, not every month.
Compare prices
Compare SendGrid, Mailgun, Postmark, Mailchimp and MailCheap with your own Amazon SES. Each provider is priced on its cheapest plan for your volume; SendForever is one payment plus what AWS bills each month.
Over 2 years, against SendGrid, the cheapest of the five
You save $485.40 more
The plan pays for itself in 5 months.
$99 once, then AWS each month
$353.40
$10.60 a month
Essentials 100K
$838.80
$34.95 a month
Foundation 100K
$1,800
$75.00 a month
Pro 200K
$1,896
$79.00 a month
4 blocks of 25K + Standard
$2,400
$100.00 a month
Basic 125K
$2,760
$115.00 a month
List prices billed monthly, before tax, checked in October 2026. SendForever’s total is the plan’s one payment plus what Amazon SES bills on the plan chosen above, and $0.12 per GB. Dedicated IPs are left out everywhere.
How it works
A page walks you through each one and moves on by itself while AWS and your DNS do their part.
Your test emails go out while AWS reviews your request to email anyone.
Open a CloudFormation link with everything filled in and create the stack. It makes an IAM role only SendForever can assume, so no access keys change hands.
SendForever creates each one in Amazon SES with 2048-bit DKIM, MAIL FROM and DMARC, and adds its records to Cloudflare or sends them to your DNS admin.
Your app sends over SMTP or the Amazon SES API with credentials that live in your AWS account. Campaigns run there too, as an AWS Step Functions workflow.
Features
Amazon SES delivers the email. SendForever sets it up properly, watches it and gives your team the tools to send, in one app.
2048-bit DKIM, a custom MAIL FROM domain, a configuration set of its own and isolation from your other domains, checked against Amazon SES, Gmail and Yahoo requirements.
One click adds every record on Cloudflare. Anywhere else, copy them all at once or send a link to whoever runs your DNS. Each record shows what the DNS publishes now.
Delivered, bounced, complained, opened and clicked, for the last 30 days, searchable and exportable. The events stay in an S3 bucket in your account.
Owners and admins hear when the bounce rate nears 5% or complaints near 0.1%, the levels where Amazon SES reviews an account, and when a domain is paused.
Write in the visual editor, Markdown or HTML, from starting points built on Postmark’s open templates. Images are served from CloudFront in your account.
Import CSVs with a record of consent, schedule sends, set the pace, and let a campaign stop itself when bounces or complaints climb. Unsubscribes are handled for you.
Manage domains, audiences, templates and campaigns from code, or connect Claude Code and other MCP clients. Keys are read-only or full access, per team.
Invite owners and admins to manage, and members who can only view. On Agency, each client gets a team of its own, with its own AWS account, domains and people.
A webhook to your app, DMARC report analysis, your own tracking host, a BIMI logo, kept copies of sent emails, suppression lists, passkeys and two-factor.
Your AWS account
Everything that sends, stores or delivers your email runs in your AWS account, and AWS bills it to you at Amazon SES prices. Already sending with Amazon SES? Connecting changes nothing until you add a domain, and then only that domain.
How SendForever reaches your AWS accountSendForever reaches your account through an IAM role a stack you create makes. Delete the stack and its access ends at once.
Your app sends straight to Amazon SES, campaigns run in your account and webhook events go from your account to your URL.
Contacts, templates, the activity log and the images in your email live in your AWS account, not on our servers.
If SendForever went away tomorrow, your app would keep sending with the same domains and credentials, because they are yours.
Pricing
No subscription and no price per email from us. AWS bills your account for what you send, at $0.10 per 1,000 emails.
Everything SendForever does, for your own domains.
$99once
Everything in Solo, with a team for each client.
$299once
VAT is added where it applies. Paddle is the seller, so the charge and the invoice come from Paddle, and the checkout may show the price in your currency. A plan covers every team its owner creates.
FAQ
What people usually ask before they connect their AWS account.
Solo costs $99 and Agency costs $299, plus VAT where it applies. Each is one payment, and you keep the plan for life. There is no monthly fee, and SendForever does not charge by volume: what you send is billed by AWS, at Amazon SES prices.
You pay SendForever once for the plan. AWS bills your own AWS account for what Amazon SES sends: $0.10 per 1,000 emails on pay-as-you-go, plus $0.12 per GB of data. New AWS accounts start on the Essentials plan, at $0.16 per 1,000 with deliverability insights included, and can switch to pay-as-you-go at once. The activity log, the webhook, alerts and campaigns add cents at most, mostly within AWS’s free tier.
Yes. SendForever sends with Amazon SES in your own AWS account, and connecting it is the first step. If you have none, AWS asks for a card and a phone number, and a new account can take up to a day to be ready.
No. Your app sends straight to Amazon SES in your account with sending credentials that live there, campaigns run as a workflow in your account, and webhook events go from your account to your URL.
Your app keeps sending, because it talks to Amazon SES in your account directly. Your domains, templates, contacts, suppression list and activity log are in your account too. What you would lose is the app itself, the API and MCP server, alert emails and the DMARC report analysis.
No. A CloudFormation stack you create makes an IAM role that only SendForever’s AWS account can assume, with an external ID unique to your team. The role cannot reach EC2, RDS, Lambda, DynamoDB or any S3 bucket but its own. SendForever keeps only the role’s ARN, never access keys, and deleting the stack ends its access at once.
Connecting changes nothing in Amazon SES, and your app keeps sending as it does today. A domain only changes once you add it to SendForever, and only that domain. Choose the region you already send from, because production access does not carry over to other regions.
It is the same Amazon SES, so everything SendForever creates is yours. It sets each domain up as AWS recommends, with 2048-bit DKIM, a custom MAIL FROM domain, its own configuration set and isolation, checks it against Amazon SES, Gmail and Yahoo requirements, and can publish its DNS records on Cloudflare. On top it adds an activity log, alerts, a template editor, audiences, campaigns, a webhook, an API and an MCP server, for your whole team.
About 10 minutes of your own time. AWS creates the stack in a few minutes, Amazon SES usually sees your DNS records within minutes, and AWS answers a request to leave the sandbox within 96 hours. Your test emails go out meanwhile.
Solo, if you send from your own domains. Agency, if you send for clients and want a team for each one, with its own AWS account, domains and members.
Connect your AWS account in about 10 minutes, pay $99 once, and send from your own Amazon SES for as long as you like.