SendForever help
Log in Get started

Help Start

How SendForever works

SendForever is a web app that runs your email on Amazon SES in your own AWS account. This page covers what runs in your account and what runs on SendForever's servers, what SendForever keeps and never keeps, how the app is organized, the terms these docs use, and the plans and prices.

What SendForever is

SendForever sets up and manages Amazon SES in an AWS account you own. You connect the account and add the domains you send from. SendForever creates each domain in Amazon SES the way AWS recommends and checks it against Amazon SES, Gmail and Yahoo best practices. It also gives your app the credentials to send. In the same app you write templates, keep audiences and send campaigns. You can follow every email in the activity log, and you get alerts when your sending reputation drops.

Amazon SES in your account sends every email. AWS bills your account for it at Amazon SES prices. You pay SendForever once for a plan, and you keep it for life.

SendForever is for anyone who sends email from their own domains. The Solo plan is for one person. The Company plan adds colleagues, and a team for each client if you send for clients.

What runs in your AWS account

Everything that sends, stores or delivers your email runs in your account:

  • Amazon SES holds your domains, their configuration sets and tenants, your templates and the suppression list. It sends every email.
  • The CloudFormation stack you create when you connect the account. It makes the IAM role SendForever uses, and an S3 bucket for your activity log, contact imports, campaign results and the images in your email. The activity log runs on its Amazon Data Firehose stream, AWS Glue table and Amazon Athena workgroup. Alerts run on its Amazon SNS topic, CloudWatch alarms and EventBridge rules. It also makes the IAM roles that campaigns and contacts workflows run with, a permissions boundary for sending users, and a ceiling for every role it makes. Its AWS Lambda function runs the page where people unsubscribe and the API your app adds them through. A small Lambda function tells SendForever the role exists when the stack is created or updated. The stack's resources are named sendforever.
  • Resources SendForever creates as you need them: IAM sending users under the path /sendforever/, and the DynamoDB table sendforever-contacts, which keeps who is in each audience. AWS Step Functions state machines send campaigns, change subscriptions, import contacts and count audiences, and they answer the page where people unsubscribe and the subscriptions API. Amazon EventBridge Scheduler schedules start scheduled campaigns. CloudFront distributions and ACM certificates serve your images, your BIMI logo and each domain's links host. An SNS topic sits behind each domain's webhook. Domains where you keep copies get a Mail Manager archive.

See Your AWS account for exactly what the role can and cannot do.

What runs on SendForever's servers

  • The app's pages, the REST API and the MCP server.
  • Reads from your account. When someone in your team opens a page that shows your domains, figures or activity log, SendForever reads them through the role. Each session lasts at most an hour.
  • The changes you ask for in the app, such as creating a domain, saving a template, sending a test email, or starting, scheduling or stopping a campaign. SendForever asks AWS to make them. The email itself always goes out from Amazon SES in your account.
  • Alerts. The SNS topic in your account posts them to SendForever. SendForever shows them and emails the team's owners and admins.
  • DMARC reports. Mailbox providers can send your domains' DMARC aggregate reports to an inbox SendForever runs. This is the one thing SendForever collects, because a report comes once a day per domain and provider, not once per email.
  • Publishing DNS records on Cloudflare, when you authorize it.

SendForever never relays your email. Your app sends straight to Amazon SES with sending credentials that live in your account. It adds people to audiences through an API that also runs in your account. Campaigns run as a workflow in your account, and the webhook posts events from your account to your own URL.

What SendForever keeps

  • Your AWS account ID, the role's ARN and the region.
  • Each domain's settings and its last check: its DNS records and what was found.
  • Campaign settings: template, audience and schedule.
  • Each audience's settings (its name, the name people see and its description) and its last counts.
  • A record of each audience import: the file name, how many contacts, who confirmed that everyone in it asked for the emails, and when.
  • The DMARC aggregate reports for your domains, for 45 days after the period each one covers.
  • Alerts, for 90 days.
  • The access key ID of each sending user, never its secret.
  • The name of each subscription key and a fingerprint of it (a SHA-256 hash), never the key itself.
  • A secret, encrypted, that your links hosts send to the stack's function with each request. The function answers only requests that came through a links host.
  • A Cloudflare authorization, encrypted. It is kept until it expires within the hour or, if you choose to stay connected, until you disconnect it.
  • Your team's name, postal address, members, invitations and API keys.
  • Your own account: your name, email address, sign-in methods and plan.
  • How you arrived when you registered: the site that linked to SendForever, the page you landed on, and your country, city, browser and language.
  • Each sign-in, for a year after it was last used: how you signed in, its IP address, country, city and browser.

What SendForever never keeps

  • Access keys to your AWS account. It holds only the role's ARN.
  • The secret access key and SMTP password of a sending credential. They are shown once, when you create or rotate it.
  • Your contacts. They live in the contacts table in your account. A file you import goes from your browser straight to the bucket in your account, and a workflow there imports it.
  • Subscription keys. They are shown once, when you create one.
  • Your activity log. SendForever reads who you emailed and the subject line from your account when a page shows them, and does not keep them. It keeps only totals, such as how many people an audience has, and only for a few minutes.
  • The content of your email. SendForever reads it only in your templates and in kept copies (for domains where you turn them on). It does not keep it.
  • A Cloudflare API token you paste. It is used once.

How the app is organized

Teams

Everything in SendForever belongs to a team. Your account starts with a personal team named after you. On the Company plan, New team in the team switcher creates more. A team connects one AWS account in one Amazon SES region, and its domains live in that account.

The person who creates a team is its owner. On the Company plan, others join by invitation, as an Admin or a Member. On Solo, the owner is the team's only person. Owners and admins connect the AWS account and manage domains, templates, audiences, campaigns and API keys. Members can open the team's pages but not change them. Only the owner can choose the plan. See Teams and members.

The team's sections are:

  • Overview: the team's plan, how every domain sent over the last 30 days, the issues to resolve, and recent domains. Until Getting started is done, it also shows the next step.
  • Domains: every domain of the team, with its type, status, checks and region.
  • Alerts: every warning from Amazon SES about the account and its domains.
  • Members: who belongs to the team, and the invitations not accepted yet.
  • Settings: General (team name, postal address and Cloudflare), AWS account, and API and MCP (keys for the API and MCP server).

A domain's sections

When you open a domain, the header shows a domain switcher beside the team switcher, and the navigation changes to the domain's sections:

  • Overview: how email from the domain did over the last 30 days.
  • Activity: every email the domain sent in the last 30 days and what happened to it.
  • Campaigns, Audiences and Templates: what the domain sends, and to whom.
  • Suppressions: the addresses Amazon SES skips after a bounce or complaint.
  • Settings: the tabs DNS records, Configuration, SMTP & API, Webhook and, once the domain can send or has DMARC reports, Reputation.

Your account

The profile menu at the top right has Profile and Security (your own settings, separate from the team's), the theme, and Log out.

Getting started

A new team opens on Getting started: six steps that take about 10 minutes of your time. You connect the AWS account, choose a plan, add the domain you send from, publish its DNS records, send yourself a test email, and ask AWS to let you email anyone. The rest of the app opens once the AWS account is connected and a plan is chosen. See Getting started.

Glossary

  • Team: the unit everything in SendForever belongs to. A team has one connected AWS account in one Amazon SES region, and its own domains, members, settings and API keys.
  • Domain: a domain or subdomain you send from. SendForever creates it in Amazon SES with 2048-bit DKIM and a custom MAIL FROM domain, then shows the DNS records to publish. If a domain is already in Amazon SES, SendForever adopts it instead of creating it again. See Domains.
  • Transactional and Marketing: a domain's type. Transactional is for receipts, password resets and notifications. Marketing is for newsletters, campaigns and announcements. Use a subdomain such as news.example.com for marketing, so mailbox providers score it separately from your transactional email.
  • DNS records: the DKIM, MAIL FROM, SPF and DMARC records a domain needs, on its DNS records tab. See DNS records.
  • MAIL FROM domain: the subdomain your email uses as its envelope sender, mail.example.com by default. It has its own MX and SPF records.
  • Configuration set: the Amazon SES settings an email is sent with, and where its events go. A domain SendForever creates gets one of its own, named after the domain. It records the domain's events in the activity log and holds its choices for open and click tracking, kept copies and TLS. A domain that already had a configuration set keeps it until you choose Apply recommended settings.
  • Isolation: giving a domain its own Amazon SES tenant, with its own reputation, pause switch and suppression list. Trouble on one domain then does not stop the others. SendForever isolates a domain when you add it. Emails count toward the domain only when they carry its X-SES-TENANT header, which the SMTP & API tab shows.
  • Sending credential: an IAM user that SendForever creates in your account for one domain, under the path /sendforever/. It can only send email as that domain. It gives your app an SMTP user name and password, and an access key for the API. See Sending email.
  • Subscription key: a key your app uses to add people to one domain's audiences, through the subscriptions API on the domain's links host. It cannot send email. See Audiences and contacts.
  • Template: an Amazon SES email template that you write once and send many times, from campaigns or by name from your app. It lives in Amazon SES, so changing it also changes what your app sends with it. See Templates.
  • Audience: a list people sign up to on one of your domains, such as a weekly newsletter. The contacts table in your AWS account keeps who is in it. Your app adds people through the subscriptions API on the domain's links host, or you import a file. See Audiences and contacts.
  • Campaign: a template sent to an audience from a domain, now or at a time you schedule. It runs as an AWS Step Functions workflow in your account. SendForever only starts, schedules, stops and reads it. See Campaigns.
  • Activity log: every email your domains send and what happened to it. Amazon SES writes the events through Amazon Data Firehose to the S3 bucket in your account, which keeps them for 90 days. SendForever queries them with Amazon Athena. Activity shows the last 30 days. See Activity.
  • Suppression list: the addresses Amazon SES skips after a bounce or spam complaint. The account has one, which you turn on in Settings > AWS account. An isolated domain keeps its own. See Suppressions.
  • Alert: a warning about your sending reputation. It comes when the account's bounce rate reaches 5% or its complaint rate reaches 0.1% (the levels at which Amazon SES places accounts under review), or when Amazon SES pauses or flags an isolated domain. See Alerts.
  • Webhook: a URL in your app that receives the events of every email a domain sends, posted by Amazon SNS from your account. See Webhooks.
  • Sandbox: where a new Amazon SES account starts. It only delivers to addresses you verified, up to 200 emails a day.
  • Production access: AWS's approval to email anyone, which takes the account out of the sandbox. You request it from SendForever and AWS reviews it. It does not carry over to other regions. See Production access.
  • Deliverability insights: Amazon SES's Virtual Deliverability Manager, with delivery, bounce and complaint figures per domain and per mailbox provider. It is one switch for the whole account, in Settings > AWS account, because Amazon SES charges for it on every email the account sends.
  • Kept copies: a copy of every email a domain sends, which Mail Manager keeps in your account for three months. Turn on Keep copies for a domain to get them.
  • Links host: a host of your own, such as links.example.com, that answers a domain's unsubscribe links, the subscriptions API and the domain's tracked opens and clicks. A CloudFront distribution and an ACM certificate that SendForever creates in your account serve it.
  • DMARC report: an aggregate report a mailbox provider sends about a domain, about once a day. SendForever collects them and shows who sends as the domain on its Reputation tab.
  • Stack: the CloudFormation stack you create in your AWS account to connect it. From version 17, SendForever applies new versions of the stack itself, within the ceiling that every role of the stack has. A version that needs more than that asks you to update the stack by hand. Deleting the stack revokes SendForever's access.
  • API key: a key for the REST API and the MCP server, made in Settings > API and MCP, with read-only or full access. It acts as whoever made it, in that team only. See API and MCP.

Plans and pricing

Plan Price What it covers
Solo $99 Everything SendForever does, for your own domains, from one account.
Company $299 Everything in Solo, with colleagues in your team and a team for each client.
  • Each plan is one payment, and you keep it for life. VAT is added where applicable.
  • You pay in a Paddle checkout. Paddle is the seller, so the charge and the invoice come from Paddle. The checkout may show the price in your local currency.
  • Solo is one team, your personal one, for you alone. It has no other teams and no members. Company lets you create as many teams as you need and invite people into each.
  • You can upgrade from Solo to Company at any time for the difference, $200, paid once. New team and Invite member offer the upgrade (see Teams and members).
  • Only a team's owner can choose the plan. It belongs to the owner's account and covers every team they own.
  • AWS bills your account directly for what Amazon SES sends and for the options you turn on. Settings > AWS account shows an estimate under "What AWS bills you".

Common questions

How much does SendForever cost?

Solo costs $99 and Company costs $299, plus VAT where applicable. Each is a single payment that you keep for life.

What do I pay AWS, and what do I pay SendForever?

You pay SendForever once for the plan. AWS bills your AWS account directly for sending, at Amazon SES prices. It also bills for the options you turn on, such as Deliverability insights, isolation and kept copies. The activity log, the webhook, alerts and campaigns add cents at most, mostly within AWS's free tier. Settings > AWS account estimates your monthly AWS bill from what you sent over the last 30 days.

Do I need an AWS account?

Yes. SendForever sends with Amazon SES in your own AWS account, and connecting it is the first step. If you do not have one, create one first. AWS asks for a card and a phone number, and a new account can take up to a day to be ready. Whoever connects it must be allowed to create CloudFormation stacks and IAM roles, such as the root user or an administrator.

Can SendForever read my email?

SendForever can read who you sent email to and the subject line, from the activity log in your account. It can read the content of your email only in your templates, and in kept copies for domains where you turn them on. It reads these when someone in your team opens a page that shows them, and does not keep them.

Does my email pass through SendForever's servers?

No. Your app sends straight to Amazon SES in your account with its sending credentials. Campaigns run in your account, and webhook events go from your account to your URL.

What happens to my sending if SendForever is down or goes away?

Your app keeps sending, because it talks to Amazon SES in your account directly, with credentials that live there. It keeps adding people to audiences, because the subscriptions API runs in your account too. People can still unsubscribe from the page on your links host. Your domains, templates, contacts, suppression list and activity log are in your account as well. You lose only what runs on SendForever's servers: the app, the API and MCP server, alert emails, and the analysis of DMARC reports.

How is this different from using the Amazon SES console?

SendForever uses the same Amazon SES in your account, so everything it creates is yours. It sets up each domain the way AWS recommends, with 2048-bit DKIM, a custom MAIL FROM domain, its own configuration set and isolation. It checks the domain against Amazon SES, Gmail and Yahoo best practices, and can publish its DNS records on Cloudflare. It also adds an activity log, alerts, a template editor, audiences, campaigns and a webhook, for your whole team in one app.

I already send with Amazon SES. Does connecting change anything?

Connecting changes nothing in Amazon SES, and your app keeps sending as it does today, with the same domains and credentials. 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. See Your AWS account.

How do I revoke SendForever's access?

Delete the CloudFormation stack in your AWS account. Access ends at once. The bucket with your activity log is kept, since it is your data.

Which plan do I need?

Choose Solo if you send from your own domains and work in SendForever alone. Choose Company if colleagues work with you, or if you send for clients and want a team for each one. You can start on Solo and upgrade to Company later for the difference.

Still stuck?

, which answers from these pages.

No page or section has those words.

Ask AI

ChatGPT or Claude answers in a new tab, from the SendForever docs. Only your question goes with it, nothing about your team.

Or read the help center

ChatGPT Claude