Why it exists
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 project ends up sending these. Until now, each one meant another email vendor, with another signup, more keys and settings, and a free plan that could be cut at any time.
Depesha does that work once. It runs on a mail relay its author already operates, with Amazon SES as the fallback, and every project reaches it the same way.
Planned
What the first version is meant to do.
Planned Not available yet, no date promised.
-
One call to send
A project sends a templated email with one authenticated HTTP request and gets a message id back at once. Sending, retries and status happen in the background.
-
A new domain in one command
Signing keys, the SPF, DKIM and DMARC records, relay settings and a test send, done by one command instead of an afternoon in DNS dashboards.
-
Each project sends as itself
Mail goes out from the project's own domain, signed with its own key, in its own look, with its own list of addresses not to write to again.
-
Bounces and complaints stop further mail
When an address bounces or a recipient marks a message as spam, Depesha stops writing to it automatically, so problems don't pile up unnoticed.
Decided against
What Depesha won't do.
- No open or click tracking. No tracking pixels, and links in Depesha's emails go straight to where they say.
- No service for other people. There's no signup and no waitlist. If that ever changes, this page will say so first.