# Send With SES is now SENDUNE

<figure><img src="https://799490287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrBivE1FyCVwIqE5rQR3A%2Fuploads%2FFYfY6NUpv7kPxffeAeS0%2Fswses%20to%20sendune%20transparent.png?alt=media&#x26;token=e368bf57-3699-48c2-b7d0-17546c3da859" alt=""><figcaption></figcaption></figure>

Hi.

Send With SES is now SENDUNE. The new website is [<mark style="color:red;">https://sendune.com</mark>](https://sendune.com/).

When Send With SES launched in 2018, its main function was to abstract away all the complexity of using AWS SES. A lot has changed since then. Send With SES is now capable of doing [<mark style="color:red;">many more things</mark>](https://sendune.com/pages/features). We want the new name to reflect these new powers and we think SENDUNE is apt.

* You might still see some references to Send With SES in the documentation pages. You can safely follow any instructions that mention Send With SES.
* This migration is fully backward compatible. All erstwhile API endpoints (api.sendwithses.com) will continue to work normally and no changes are required from you.
* There are no pricing changes.&#x20;
* We continue to adhere to our [<mark style="color:red;">minimalist agenda</mark>](https://sendune.com/pages/minimalism).

You can write to <hello@sendune.com> in case you have any questions or face any issues.

**Cheers.**\
**SENDUNE Team.**\
\&#xNAN;**(formerly Send With SES).**