Why Depesha
Every project needs email. None of them should need a new vendor.
A code to sign in, a link to reset a password, a note that a long job has finished: every product sends these. Usually each one means another email vendor, another signup, more keys and settings, and a free plan that can be cut at any time.
With Depesha you set up email once. Every project you add reaches it the same way and sends from its own domain.
How it works
Built for the emails people are waiting for.
-
One call to send
Send a templated email with one authenticated HTTP request and get a message id back at once. Delivery, retries and status tracking run in the background.
-
A new domain in a few CNAMEs
Add the records Depesha shows you once. It checks them, signs your mail and rotates keys from then on, without you touching DNS again.
-
Each project sends as itself
Its own domain, its own signing key, its own branded layout and its own list of addresses not to write to again. One project's trouble doesn't hold up another's sign-in codes.
-
On time, or not at all
Give a message a deadline, like a code's expiry. If it can't go out in time, it's marked expired instead of arriving late and confusing someone.
-
Bounces and complaints handled
When an address bounces or a recipient marks a message as spam, Depesha stops writing to it automatically, so your sending reputation stays clean.
-
A fallback built in
Mail goes out through Depesha's own relay. If the relay has trouble, Amazon SES takes over automatically, behind the same API.
-
Looks right in every inbox
Each project gets a branded base layout that holds up in Gmail, Outlook and Apple Mail, light and dark, with a plain-text version in every message.
-
Made for coding agents
A CLI, a Claude skill and an MCP server let your agent add Depesha to a project, set up the domain and send you a test email.
The API
One request per email.
Templates live in your project's repository and are pushed with one command. Sending is a single HTTP request with an idempotency key, so a retry never sends twice.
curl https://api.depesha.com/v1/messages \
-H "Authorization: Bearer dp_live_…" \
-H "Idempotency-Key: sign-in-7f3a9c" \
-H "Content-Type: application/json" \
-d '{"to": "you@example.com",
"template": "sign-in-code",
"variables": {"code": "482 913"},
"deliverBy": "2026-11-02T10:15:00Z"}'Returns 202 with the message id. Projects, domains, keys and templates are managed through GraphQL, the CLI or the MCP server.
Questions
Short answers.
- What is Depesha?
- Depesha is transactional email for every project you run: sign-in codes, password resets and "your result is ready" messages, each sent from the project's own domain through one small API. It is in private beta.
- How do I add a domain?
- You add the few CNAME records Depesha shows you, once. Depesha checks them, signs your mail and rotates its keys from then on. Your domain's own MX and SPF records stay as they are.
- Is Depesha free?
- Yes, during the private beta: invited projects send for free. Pricing is set before Depesha opens to everyone.
- Who can join the beta?
- Builders with a real project and a domain to send from. Join the waitlist with both and confirm your address; we invite projects one at a time, so every sender on Depesha keeps a clean reputation.
- How is it different from using Amazon SES directly?
- Depesha is the layer you would otherwise build around SES, set up once for all your projects: domains in a few CNAMEs with signing and key rotation handled, templates kept in your repository, deadlines, a suppression list per project and a fallback. You don't need an AWS account of your own.
Join the private beta.
Tell us about your project and the domain you'd send from. We invite projects one at a time, so every sender on Depesha keeps a clean reputation.
We use these details only to review your project and invite you to Depesha. See the waitlist privacy notice.