# Send With SES is now SENDUNE

<figure><img src="/files/rSqt2FjwrsitzMl4l3Tu" 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).**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://blog.sendune.com/send-with-ses-is-now-sendune.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.