A control plane for transactional email you send yourself.
Fortsend is an API and dashboard for managing sender domains, mailboxes and API keys. It is for teams that send system email from their own product and want to control the sending setup.
What it does
Fortsend manages the setup around transactional email. You add a sender domain, publish the DNS records it gives you, and create mailboxes and API keys. You then send mail with one HTTP request. Messages go out through a mail backend.
- Sender domains. Add a domain, receive its DNS records, and re-check them from the dashboard or the API.
- Mailboxes. Create mailboxes on a domain once it is provisioned.
- API keys. Create and revoke keys. A key can send mail and nothing else.
- Send endpoint. One POST request sends a message. Responses are JSON with standard status codes.
- Limits. Each workspace has a send rate limit and a monthly quota, plus size caps on the subject and body.
Who it is for
Fortsend suits teams that send receipts, password resets and other system messages from their own product. It fits developers who want a plain HTTP API and control over the sending domain and mail host. If you need help fitting it into an existing system, contact us.
How it works
- Sign in to the dashboard and add your sender domain.
- Publish the DNS records shown for the domain. They cover ownership, mail routing, SPF, DMARC and DKIM.
- Run the DNS check. Ownership and mail routing must resolve before the domain is provisioned.
- Create a mailbox and an API key. The key secret is shown once.
- Send mail with a bearer-key request to the send endpoint.
How it handles data
These are design facts from the product's own documentation. They are not certifications or guarantees.
- API keys. By design, key secrets are stored only as SHA-256 hashes and are shown once. A lost key is revoked and replaced, not recovered.
- Key scope. API keys work only on the send endpoint. Managing domains, mailboxes and keys requires a signed-in session.
- Browser requests. State-changing requests from a signed-in session must come from a trusted origin.
- Message content. Message bodies are handed to the mail backend for delivery and are not stored in the control plane. The send log keeps sender, recipient, subject, status and time.
Optional DNS assistant
When enabled, an Explain button appears on domains that are not yet provisioned. It re-checks the domain's DNS and asks an AI model to describe failing records in plain language. It runs only in the management side of the product, and nothing on the send path calls a model.
DNS values it reads are treated as untrusted input. They are length-limited and passed to the model as data, and the answer is shown as plain text. Without the feature configured, the endpoint returns an error and the button is hidden. Calls are rate limited per workspace.
Plans
The product describes three plans named Starter, Scale and Dedicated. Starter is for evaluation and small projects. Scale is for usage-based sending. Dedicated is for teams that want a separate mail host.
Fortsend FAQ
What can an API key do?
A key carries the email:send scope only. It can send mail. It cannot add domains, create mailboxes or manage other keys.
What happens when a workspace reaches its limit?
The send endpoint returns HTTP 429. A rate-limit response includes a Retry-After header. Requests are not silently dropped.
What if the mail backend rejects a message?
The send endpoint returns HTTP 502 and the activity log records the message as failed.
Does the AI assistant touch my email?
No. It only explains DNS problems for a domain you are setting up. Nothing on the send path calls a model.