Email for developers. Both kinds.
SimpliDeliver Email is a REST API for the two streams of mail a product sends: the transactional message a person is waiting for, and the marketing message they signed up to receive. One API, one domain setup, one set of delivery events.
Status: private beta. The service is invite-only while we build it in the open. Sending is not yet available for public signup. If you want an invitation, write to support@simplideliver.com.
The two streams
Transactional
Mail sent to one person because of something they just did: password resets, email verification, one-time passcodes, receipts, order and delivery notifications, security alerts. It has to arrive in seconds and it has to arrive every time.
Marketing
Mail sent to people who asked to hear from you: product announcements, newsletters, campaigns, digests. Sent to a list of contacts you keep with us, to recipients who gave you explicit permission and can withdraw it in one click.
The word doing the work in that paragraph is asked. We are a marketing sender, not a cold-outreach tool. Purchased, rented, scraped and appended lists are prohibited and always will be — see the Acceptable Use Policy. That is not a formality: it is the single rule that decides whether shared sending infrastructure keeps working for everyone on it.
Sending limits
Limits are published rather than negotiated, and the two streams are metered differently: transactional by emails sent, marketing by contacts stored. Broadcasts to your contacts are unlimited and never count against your transactional quota — so a campaign to your whole list does not eat the quota your password resets depend on.
| Plan | Emails / month | Daily cap | Overage / 1,000 |
|---|---|---|---|
| Free | 3,000 | 100 | — |
| Pro | 50,000 | none | $0.90 |
| Pro | 100,000 | none | $0.90 |
| Scale | 200,000 | none | $0.80 |
| Scale | 500,000 | none | $0.70 |
| Scale | 1,000,000 | none | $0.65 |
| Scale | 2,500,000 | none | $0.46 |
| Enterprise | 3,000,000+ | none | custom |
| Plan | Contacts | Broadcast sending |
|---|---|---|
| Free | 1,000 | Unlimited |
| Pro Marketing | 5,000 — 150,000 | Unlimited |
| Enterprise | 200,000+ | Unlimited |
Transactional and marketing are independent subscriptions — you can sit on a
paid marketing plan and the free transactional plan, or the reverse. The API
rate limit is 10 requests per second per account across every
key on it, returning 429 with standard
ratelimit-* and retry-after headers so a client can
back off correctly instead of guessing.
Volume above the entry plans is reviewed rather than sold. We look at your sending record and at how your lists were built before raising a limit, and every account starts on a probation cap whatever it pays. The Acceptable Use Policy has the full ladder and the rules around it.
During private beta every account is on the free tier and nothing is charged. The tables above are the launch ladder, published so you can see the ceiling before building against it. Final pricing is confirmed before general availability.
Consent, and getting out
Every marketing recipient must have given you explicit permission, and you must be able to show when and how. Pre-ticked boxes, "we found your address", "you're a customer so you opted in", and lists from anyone but the recipient are not permission.
We add the unsubscribe mechanism ourselves. Every marketing message goes out
with a List-Unsubscribe header and one-click
List-Unsubscribe-Post per RFC 8058, pointing at an endpoint we
host. When someone uses it, the opt-out is written straight into your
account's suppression list and takes effect immediately — it does not depend
on your application receiving a webhook, or on you doing anything at all.
Gmail and Yahoo require this of bulk senders; more to the point, an opt-out
that can fail is not an opt-out.
How sending works
You prove you own the domain first
No account can send from a domain until ownership of it is proven. We generate DKIM records per domain, along with SPF and a custom MAIL FROM record, and sending from that domain stays disabled until we have checked the published records against public DNS. There is no way to skip this step and no way to send from a domain you have not verified.
Every message emits an event
Sends, deliveries, bounces, complaints, delays, rejections and rendering failures are all delivered as events, correlated to the individual message ID you got back from the API. That stream is the product as much as the send call is.
Bounces, complaints and opt-outs suppress the address
A permanent bounce, a spam complaint or an unsubscribe adds that recipient to your account's suppression list immediately, and later sends to the address are refused by us before they ever reach a mail server. Addresses are not removed from suppression automatically.
Reputation is measured per account, and enforced
Each account sends under its own identity so that delivery statistics are attributable to it and to nobody else. We track rolling bounce and complaint rates per account, and we suspend sending on an account whose rates cross the limits published in the Acceptable Use Policy. Shared infrastructure only works if a sender who abuses it is removed from it quickly.
Tracking is off until you turn it on
Open and click tracking is disabled by default on every domain. You enable it per domain, and only after you have set up a tracking subdomain on your own DNS — because opens are measured with a 1×1 pixel and clicks by rewriting every link in the message, and both of those should happen on your domain rather than ours. Shared tracking domains get flagged by spam filters and hurt the deliverability they are supposed to measure.
We suggest turning it on for marketing campaigns and leaving it off for transactional mail. Tracking pixels and rewritten links are a signal that mailbox providers use to classify a message as promotional, and you do not want your password reset classified that way. Leaving tracking off for transactional also means nobody, including us, holds a record of a person opening a security alert.
This website itself carries no analytics and no third-party scripts, fonts or trackers of any kind, and sets no cookies. See the Privacy Policy.
Where your mail is sent from
Outbound mail is sent through Amazon Simple Email Service in AWS region
ap-southeast-1 (Singapore), which is our only sub-processor for
message delivery. Message content is retained for 30 days and then purged.
The Privacy Policy sets out what we store, for how
long, and who else touches it — including your contact lists, which are the
one thing we hold on an ongoing basis rather than for 30 days.
Reporting abuse
If you received mail sent through SimpliDeliver Email that you did not ask for, tell us. Reports go to abuse@simplideliver.com, a monitored mailbox read by a person, and we aim to acknowledge within one business day. Please include the full message headers if you have them — they identify the sending account, which is what lets us act on the report. We can and do suspend accounts over abuse reports.
Contact
- General and support
- support@simplideliver.com
- Abuse reports
- abuse@simplideliver.com
- Operator
- Niyam Vora, sole proprietor, trading as SimpliDeliver. India.