
Today marks the end of the first Resend Launch Week. In the last 7 days, we shipped 7 new features.

Here's a quick recap of what we launched:

* [Day 1: Faster Email Delivery with Multi-Region](#day-1)
* [Day 2: Introducing Managed Dedicated IPs](#day-2)
* [Day 3: Capture email events with Webhooks](#day-3)
* [Day 4: New Domain Verification Experience](#day-4)
* [Day 5: Supercharge Sending with Integrations](#day-5)
* [Day 6: Open and Click Tracking](#day-6)
* [Day 7: Send emails using React and Tailwind CSS](#day-7)

<h2 id="day-1">Day 1: Faster Email Delivery with Multi-Region</h2>

![Faster Email Delivery with Multi-Region](/blog/static/posts/multi-region.jpg)

On Monday, we added support for three new email sending regions, including Europe (Ireland), South America (Brazil), and East US (North Virginia).


This means that no matter where your users are, you can ensure that they receive your emails in a timely and efficient manner.

- **Read the [announcement](/blog/multi-region)**
- **Go to the [dashboard](https://resend.com/domains)**

<h2 id="day-2">Day 2: Introducing Managed Dedicated IPs</h2>

![Introducing Managed Dedicated IPs](/blog/static/posts/dedicated-ips.jpg)

On Tuesday, we announced the launch of managed Dedicated IPs.

With this, the sender has full control over their IP reputation, and their email sending is not impacted by other senders' activities.

Dedicated IP addresses are typically more expensive than shared IP addresses, but they offer more control and better deliverability rates for high-volume senders.

- **Read the [announcement](/blog/dedicated-ips)**
- **Go to the [dashboard](https://resend.com/settings)**

<h2 id="day-3">Day 3: Capture email events with Webhooks</h2>

![Capture email events with Webhooks](/blog/static/posts/webhooks.jpg)

On Wednesday, we launched one of our most requested features: Webhooks.

This enables you to receive real-time notifications about your email sending activities directly to your server.

- **Read the [announcement](/blog/webhooks)**
- **Go to the [dashboard](https://resend.com/webhooks)**
- **See a [code example](https://github.com/resendlabs/resend-examples/tree/main/with-webhooks)**
- **Browse the [docs](https://resend.com/docs/webhooks)**

<h2 id="day-4">Day 4: New Domain Verification Experience</h2>

![New Domain Verification Experience](/blog/static/posts/new-domain-verification-experience.jpg)

On Thursday, we released a redesigned domain verification experience.

The cool thing about this new interface is that it reduces friction and adapts based on your DNS provider.

- **Read the [announcement](/blog/new-domain-verification-experience)**
- **Go to the [dashboard](https://resend.com/domains)**

<h2 id="day-5">Day 5: Supercharge Sending with Integrations</h2>

![Supercharge Sending with Integrations](/blog/static/posts/new-integrations.jpg)

On Friday, we announced the first batch of Resend integrations, including Novu, Knock, Trigger.dev, and Pipedream.

- **Read the [announcement](/blog/new-integrations)**
- **Browse the [docs](https://resend.com/docs/integrations)**

<h2 id="day-6">Day 6: Open and Click Tracking</h2>

![Open and Click Tracking](/blog/static/posts/open-and-click-tracking.jpg)

On Saturday, we launched email open and click tracking.

This gives you to have actionable insights to better engage with your users.

- **Read the [announcement](/blog/open-and-click-tracking)**
- **Go to the [dashboard](https://resend.com/domains)**

<h2 id="day-7">Day 7: Send emails using React and Tailwind CSS</h2>

![Send emails using React and Tailwind CSS](/blog/static/posts/tailwind-with-react-email.jpg)

On Sunday, we announced support for Tailwind CSS in React Email.

Now you can build and send beautiful emails without having to write any CSS.

- **Read the [announcement](/blog/tailwind-with-react-email)**
- **Browse the [docs](https://react.email/docs/components/tailwind)**

## Looking forward

This launch week marked a significant milestone for the company. We're laying the foundation for years to come and we're excited to continue shipping stuff for you.

All about the seven new features we launched in the last seven days.

Launch Week 1: Wrap Up


Libraries like [React](https://reactjs.org) and [Tailwind CSS](https://tailwindcss.com) have made it easier to build modern websites. However, when it comes to emails, we were still stuck with old-school HTML and CSS.

Today we're excited to announce that you can now use [Tailwind CSS](https://tailwindcss.com) with [React Email](https://react.email) to build beautiful emails without having to write any CSS.

<blockquote>
  "Resend not only streamlines our emails to accommodate our expanding customer base, but their team also offered valuable hands-on support during the transition from our old API. Their product is visually stunning and seamlessly integrates with React Email."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Narative" src="/blog/static/posts/logo-narative.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Thiago Costa" src="/blog/static/posts/avatar-thiago-costa.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Thiago Costa</span>
      <span class="quote-author-job">Co-founder of Fey and Narative</span>
    </span>
  </div>
</blockquote>

## What is React Email again?

[React Email](https://react.email) is an open source set of unstyled components maintained by our team to help you build beautiful emails without having to deal with `<table>` layouts and maintaining archaic HTML code.

If you're new to React Email, I highly recommend checking out the [getting started guide](https://react.email/docs) or watching this amazing video from [Chris Pennington](https://twitter.com/cpenned):

<iframe width="672" height="378" src="https://www.youtube.com/embed/MdO1AKVTkLI" title="React Email First Look" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

## How to use Tailwind CSS with React Email

We recommend using [create-email](https://www.npmjs.com/package/create-email), which is the easiest way to get started:

```
npx create-email@latest
```

This will create a new folder called "react-email-starter" with a few email templates.

Now, import the component around your email body:

```jsx
import { Button, Tailwind } from '@react-email/components';

const Email = () => {
  return (
    <Tailwind>
      <Button
        className="bg-brand px-3 py-2 font-medium leading-4 text-white"
        href="https://example.com"
      >
        Click me
      </Button>
    </Tailwind>
  );
};
```

You can customize the default theme with the available properties in [Tailwind CSS docs](https://tailwindcss.com/docs/theme).

<blockquote>
  "As of our last deployment all of our emails are using Resend. We are loving the development experience of React Email - not having to leave my dev environment to develop new emails is a game-changer."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Warp" src="/blog/static/posts/logo-warp.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Adam Rankin" src="/blog/static/posts/avatar-adam-rankin.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Adam Rankin</span>
      <span class="quote-author-job">Founding Engineer at Warp</span>
    </span>
  </div>
</blockquote>

## Live example

If you want to see a live example, check out the [Vercel template using Tailwind](https://demo.react.email/preview/vercel-invite-user).

![Vercel template using Tailwind](/blog/static/posts/tailwind-with-react-email-1.jpg)

## Thanks

The [Tailwind CSS integration](https://react.email/docs/components/tailwind) wouldn't be possible without the help of our incredible open source community. A special thanks to [Vinicius de Moraes](https://github.com/vinicoder), who led the initial implementation and fixed several issues along the way.

Build beautiful emails with Tailwind CSS and React Email.

Send emails using React and Tailwind CSS


> "How are my emails doing?"
>
> "Is anyone engaging with my CTA?"
>
> "How many users saw my announcement?"

These are the questions that come when you start sending emails at scale.

Today, Resend helps you not just answer, but take action on those questions.

## More than curiosity

We believe open and click tracking offers practical and actionable insights to better engage with your users.

Ultimately, opens and clicks show you which customers are the most interested in receiving the messages you send.

By knowing this you can:

* Measure results of your emails
* Have a better understanding of your audience
* Transform these insights into action by refining your email templates

![Click and Opened Events in Resend Dashboard](/blog/static/posts/open-and-click-tracking-1.jpg)

## How open tracking works

When open tracking is enabled, we insert a 1 pixel by 1 pixel transparent GIF image at the bottom of each message.

Each email includes a unique link to this image file; when the image is opened, we can tell exactly which message was opened and by which user.

<blockquote>
  "If you're a developer or working on a startup, you're going to love Resend's approach to emailing."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="SpecCheck" src="/blog/static/posts/logo-speccheck.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Joe DeMaria" src="/blog/static/posts/avatar-joe-demaria.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Joe DeMaria</span>
      <span class="quote-author-job">Co-founder & CEO of SpecCheck</span>
    </span>
  </div>
</blockquote>

## How click tracking works

When click tracking is enabled, we set up a redirect for each link in the message. When your user clicks a link, they are routed to a Resend server and then immediately forwarded to the address you provided. This handoff is imperceivable to the recipient in normal circumstances.

As with open tracking, each of these redirect links is unique, allowing you to easily determine which person clicked which link at what time.

<blockquote>
  "We were up and running with Resend in no time. It was seamless to integrate into our existing workflow and gave us a tremendous amount of visibility into our email capabilities. Simple to say, it was a no-brainer."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="InBuild" src="/blog/static/posts/logo-inbuild.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Ty Sharp" src="/blog/static/posts/avatar-ty-sharp.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Ty Sharp</span>
      <span class="quote-author-job">Co-founder & CEO of InBuild</span>
    </span>
  </div>
</blockquote>

## Perfectly paired with Webhooks

[We announced Webhooks](https://resend.com/blog/webhooks) earlier this week, perfect timing for open and click tracking.

Creating a webhook stream of your tracking events gives you a live pulse of your contact list so you can take action immediately.

![Click and Opened Events in Resend Dashboard](/blog/static/posts/open-and-click-tracking-2.jpg)

You can also feed these data points into an external storage system to provide more context alongside your other user events.

![Click webhook event](/blog/static/posts/open-and-click-tracking-3.jpg)

## How to enable tracking

Tracking is configured on the domain level.

You can enable tracking today by navigating to Domains, selecting the domain you want to enable and looking for the "Configuration" section.

![Enable Open/Click tracking](/blog/static/posts/open-and-click-tracking-4.jpg)

Track engagement and tune your sending approach with Resend's open and click tracking.

Open and Click Tracking


With only a few lines of code, you can setup customized drip campaigns, automatically send outage alerts to your team, or notify your customers about in-app activities.

By using one of Resends Integration Partners, building battle-tested workflows is an end-to-end experience. No more reading between the documentation lines to guess how two systems can work with each other.

<blockquote>
  "The Resend team have built a great product in a space that hasn't seen 10x innovation for years. Engineering peers are raving about Resend - it's such a smoother dev experience."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Alliance" src="/blog/static/posts/logo-alliance.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Roberto Riccio" src="/blog/static/posts/avatar-roberto-riccio.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Roberto Riccio</span>
      <span class="quote-author-job">Head of Product at Alliance</span>
    </span>
  </div>
</blockquote>

Here are the new ways you can extend Resend:

## Novu

[Novu](https://novu.co) provides simple components and APIs for managing all communication channels in one place. You can easily create templates, styled components, and triggers that make sense to your application.

→ [Check the integration](https://docs.novu.co/channels/email/resend/)

## Knock

[Knock](https://knock.app) is a flexible, reliable notifications infrastructure that’s built to scale. It provides APIs to engage users, power cross-channel workflows, and manage notification preferences.

→ [Check the integration](https://docs.knock.app/integrations/email/resend)

## Trigger.dev

[Trigger.dev](https://trigger.dev) workflows from APIs, on a schedule, or on demand. API calls are easy with authentication handled for you. You can add durable delays that survive server restarts.

→ [Check the integration](https://docs.trigger.dev/examples/resend)

## Pipedream

[Pipedream](https://pipedream.com) helps you stop writing boilerplate code, struggling with authentication, and managing infrastructure. It gives you code-level control when you need it and no code when you don't.

→ [Check the integration](https://pipedream.com/apps/resend)

<blockquote>
  "As a developer I love the approach that the Resend team is taking. Its so refreshing. They are also extremely user-centric and helpful in terms of getting you up and running, sending beautiful emails that deliver."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Mintlify" src="/blog/static/posts/logo-mintlify.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Hahnbee Lee" src="/blog/static/posts/avatar-hahnbee-lee.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Hahnbee Lee</span>
      <span class="quote-author-job">Co-Founder at Mintlify</span>
    </span>
  </div>
</blockquote>

## Roadmap

There are many more integrations that we would like to explore in the future.

Here are a few that we are excited about:

![List of integrations coming soon](/blog/static/posts/new-integrations-1.jpg)

Wanna build an integration with Resend? [Send us a message](mailto:support@resend.com)!

Announcing the first batch of Resend Integrations, including Novu, Knock, Trigger.dev, and Pipedream.

Supercharge Sending with Integrations


With everything we build, we ask the same question: *“How can we reduce friction?”*

This internal interrogation pushes us to sift out everything unpleasant and only leave what is **necessary**, **helpful**, and **delightful**.

<blockquote>
  "I started using Resend right before we launched Anyone on Product Hunt, to start delivering emails to all of our users and patrons. The speed and ease of integrating with the product was incredible, but what really stood out was their intricate knowledge of email and relentless support day or night. Oh and we also ended up winning Product of the week."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Anyone" src="/blog/static/posts/logo-anyone.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Sam Ducker" src="/blog/static/posts/avatar-sam-ducker.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Sam Ducker</span>
      <span class="quote-author-job">Co-founder of Anyone</span>
    </span>
  </div>
</blockquote>

## Why Domains Matter

Domains (sometimes referred to as Identities) are a cornerstone of sending email.

In the past, a sender’s IP address carried most of the reputation weight. Nowadays, more emphasis is put on domain to answer that question of “who is this sender?”.

Not only must you setup your domain to start sending emails, the way you verify your domain will communicate your legitimacy to inbox providers, impacting deliverability.

This is why we chose our [Domains page](https://resend.com/domains) as our first UI redesign.

<blockquote>
  "Don’t snooze on Resend if you’re looking for a transactional email service. Tried it out today and sent my first production email within minutes after a smooth onboarding. This is what DX is supposed to look like."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar quote-avatar-author">
        <img alt="Joshua Jansen" src="/blog/static/posts/avatar-joshua-jansen.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Joshua Jansen</span>
      <span class="quote-author-job">Lead Ruby on Rails Developer at Firmhouse</span>
    </span>
  </div>
</blockquote>

## The New Experience

Here is a sneak peak at what’s new:

![Domain Experience with Google Domains](/blog/static/posts/new-domain-verification-experience-1.jpg)

The cool thing about this new interface is that it changes based on your DNS provider.

If you're using Google Domains, we adapt the UI to match the Google Domains settings. If you're using Cloudflare, we adapt the UI to match the Cloudflare's UI settings.

![Domain Experience with Cloudflare](/blog/static/posts/new-domain-verification-experience-2.jpg)

On top of that, we also made the following improvements:

* **Multi-Region Support**: We announced support for two new sending regions. You can now clearly see region when creating or managing your domains.
* **Per-Record Status**: Sometimes a specific record is having issues. You can now see the verification status of each record so you know where to focus your troubleshooting.
* **Clear Feedback**: We've added helpful tooltips and documentation links across the various interaction points to give help and clarity as you are verifying your domain.

See the [new domains page](https://resend.com/domains) for yourself or [request access](https://resend.com) today.

Behind the scenes of our redesigned domains experience with provider-specific instructions.

New Domain Verification Experience


We’re excited to announce one of our most requested features: Webhooks.

## What is a Webhook?

A webhook is a way for one application to provide other applications with real-time information. In our case, we send a notification to your application every time an email event occurs. This allows you to receive real-time and actionable updates on the delivery, open, bounce, and click events of your emails.

<blockquote>
  "Working with Resend has been amazing. By using Webhooks, I'm able to track email opened/clicked events via Segment and log those events in LogSnag for visibility. I highly believe in the people behind Resend."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Finta" src="/blog/static/posts/logo-finta.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Taylor Facen" src="/blog/static/posts/avatar-taylor-facen.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Taylor Facen</span>
      <span class="quote-author-job">Founder of Finta</span>
    </span>
  </div>
</blockquote>

## What can you build with Webhooks?

Webhooks use HTTPS and deliver a JSON payload which includes metadata like the from, to, and status of your email event. You can use email webhooks to automate your workflows, like:

- Automatically remove bounced email addresses from mailing lists
- Create alerts in your messaging or incident tools based on event types
- Store all send events in your own database for custom reporting/retention
- Expose email events in your app

## Setting up

For how powerful webhooks are, they could not be more straightforward to get started.

<blockquote>
  "Resend is super easy to set up. Loving the modern approach the team is taking with supercharging email. Never been a fan of other clunky tools."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Hammr" src="/blog/static/posts/logo-hammr.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Brek Goin" src="/blog/static/posts/avatar-brek-goin.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Brek Goin</span>
      <span class="quote-author-job">Founder of Hammr</span>
    </span>
  </div>
</blockquote>

First, create an endpoint to receive `POST` requests (or use a tool like [Zapier](https://zapier.com/features/webhooks)).

For example, you can add an API route on Next.js:

```jsx
import type { NextApiRequest, NextApiResponse } from 'next';

export default (req: NextApiRequest, res: NextApiResponse) => {
  if (req.method === 'POST') {
    const payload = req.body;
    console.log(payload);
    res.status(200);
  }
};
```

Then [register your webhook](https://resend.com/webhooks) endpoint on Resend.

![Resend Webhooks](/blog/static/posts/webhooks-1.jpg)

Now every time an email event occurs, Resend will send a `POST` request to your endpoint with the event payload.

## Check the full example

We built a [GitHub repository](https://github.com/resendlabs/resend-examples/tree/main/with-webhooks) that shows a Slack notification being triggered from Resend webhooks using Next.js and TypeScript.

![Slack Webhook Example](/blog/static/posts/webhooks-2.jpg)

## What’s next?

We’re excited to see what you build with webhooks. For more information on each event types, retry schedule, and delivery attempts, check the [Webhooks docs](https://resend.com/docs/webhooks).


Learn how to receive real-time notifications about your email sending activities directly to your server.

Capture email events with Webhooks


We are thrilled to announce the launch of our Managed Dedicated IPs.

So, what are dedicated IPs, when should you use them, and why are we so pumped up about them?

## Understanding IP's and Email Sending

When it comes to email sending, an IP address is used to identify the server that is responsible for sending emails from a specific domain. There are two types: shared and dedicated.

**Shared IP addresses** are used by multiple domains to send emails and their reputations are shared. If one sender on the shared IP address sends spam, it can negatively affect the reputation of all the other senders on that IP address. However, shared IP addresses are typically more affordable and already “warmed up” by the other domains already sending emails on it.

**Dedicated IP addresses**, on the other hand, are used exclusively by one domain to send emails. This means that the sender has full control over their IP reputation, and their email sending is not impacted by other senders' activities. Dedicated IP addresses are typically more expensive than shared IP addresses, but they offer more control and better deliverability rates for high-volume senders.

For those that are sending a high-volume and need the reputation control, Resend now offers a Dedicated IP add-on.

<blockquote>
  "Our team loves Resend. It makes email sending so easy and reliable. After we switched to Dedicated IPs, our deliverability improved tremendously and we don't hear complaints about emails landing on spam anymore."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Infisical" src="/blog/static/posts/logo-infisical.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Vlad Matsiiako" src="/blog/static/posts/avatar-vlad-matsiiako.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Vlad Matsiiako</span>
      <span class="quote-author-job">Co-founder of Infisical</span>
    </span>
  </div>
</blockquote>

## The Benefits of Dedicated IPs

Now, let's dive into the benefits of dedicated IPs.

**1. Increased Deliverability**

With dedicated IPs, you have more control over your sender reputation. When you share an IP with other companies, their actions can negatively impact your deliverability. By using a dedicated IP, you reduce the risk of your emails going to spam due to someone else's actions.

**2. Improved Sender Reputation**

As mentioned earlier, dedicated IPs give you complete control over your sender reputation. You can send emails at your own pace, control all inputs into your sender reputation, and ensure that all emails coming from your IP complies with industry standards. All of these factors contribute to building a strong sender reputation, which is critical for email deliverability.

**3. Increased Security**

With a dedicated IP address, you have full control over your email sending activities and can ensure that your emails are not being mixed with other senders' emails. This provides full isolation down to the server level.

## The Big Drawback (IP Warming)

Usually when you purchase a dedicated IP you are required to follow a process called “IP warming” which is a multi-week process of incrementally sending more emails each day until the new IP address is warmed up, which can take weeks to months. This is because your new IP address has no reputation and if you start sending thousands are millions of emails, many inbox providers may flag your IP as concerning because its unknown.

We don’t think this experience is very pleasant, so we provide **Managed Dedicated IP** pools. We handle all the IP warming in the background so when you receive your dedicated IP from Resend, you can immediately start sending at scale.

<blockquote>
  "I've used Mailgun, Sendgrid, and Mandrill and they don't come close to providing the quality of developer experience you get with Resend."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Outerbase" src="/blog/static/posts/logo-outerbase.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Brandon Strittmatter" src="/blog/static/posts/avatar-brandon-strittmatter.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Brandon Strittmatter</span>
      <span class="quote-author-job">Co-founder of Outerbase</span>
    </span>
  </div>
</blockquote>

## Deliverability for All

You may be thinking: *“I’m not a high-volume sender but I still want incredible deliverability”*.

The good news is that though dedicated IP’s are a powerful piece of the deliverability puzzle for high-volume cases, any user can achieve the legendary deliverability on our shared IP’s.

Many senders find their deliverability improves more from Resend’s high-quality shared traffic than from the isolating of a dedicated IP.

Both shared and dedicated IPs get our full deliverability attention. This means aggressive measures to protect from spamming, bouncing, and malicious actors, but also white-glove support from our team to enable you towards best practices.

## Get Your Own IP

Want to get started with a dedicated IP for your domain?

You can [request it as an add-on on your account](https://resend.com/settings) today.

Understand the benefits between dedicated IPs and shared IPs for email deliverability.

Introducing Managed Dedicated IPs


Now, users have the option to send transactional emails from three different regions:
* **Europe (Ireland)**
* **South America (Brazil)**
* **East US (North Virginia)**

This means that no matter where your users are, you can ensure that they receive your emails in a timely and efficient manner.

<blockquote>
  "All of our customers are located in South America, so having a solution that could send emails from the region closest to our users is very important. Resend's multi-region feature is a game-changer for us."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="VOA Hoteis" src="/blog/static/posts/logo-voa-hoteis.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Giovanni Keppelen" src="/blog/static/posts/avatar-giovanni-keppelen.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Giovanni Keppelen</span>
      <span class="quote-author-job">CTO &amp; Partner at VOA Hoteis</span>
    </span>
  </div>
</blockquote>

Here's how you can visualize the different regions in the Resend dashboard:

![List of domains on each region](/blog/static/posts/multi-region-1.png)

## Why is this important?

Think of magic link emails, password reset emails, and welcome emails - users expect to receive them right away. If they don't, they might not be able to access your service, which can be a missed opportunity.

Here are some of the other benefits of using our multi-region email sending feature:

1. **Faster delivery:** By sending emails from the region closest to your user, you can reduce latency and ensure a faster time-to-inbox. This can be the difference between people using/buying your product or not.
2. **Easier account management:** Instead of having to maintain two separate accounts with two separate billings, we're providing multi-region within the same account. That way, you're not juggling different login credentials.
3. **Increased resilience:** In case of any disruption in one region, our multi-region feature ensures that your emails can be sent from a backup domain in a separate region, guaranteeing maximum uptime.

## How to use it

To start using our multi-region email sending feature, go to Domains and choose the option to add a new domain. Select the region you want to send your emails and that's it.

![Select a region when adding a domain](/blog/static/posts/multi-region-2.png)

## How to migrate to another region

Existing customers will notice that all of their domains are set to the East US (North Virginia) region by default.

![See current region](/blog/static/posts/multi-region-3.png)

If you would like to migrate your domains to another region, please [contact support](mailto:support@resend.com) and we will assist you with the migration.

<blockquote>
  "Resend is an amazing product. It was so easy to switch over. I feel confident knowing that our important emails are in good hands with Resend. Everyone should be using this."
  <div class="quote-metadata">
    <div class="quote-avatars">
      <div class="quote-avatar">
        <img alt="Ruby Card" src="/blog/static/posts/logo-ruby-card.jpg" width="40" height="40" />
      </div>
      <div class="quote-avatar quote-avatar-author">
        <img alt="Shariar Kabir" src="/blog/static/posts/avatar-shariar-kabir.jpg" width="40" height="40" />
      </div>
    </div>
    <span class="quote-author">
      <span class="quote-author-name">Shariar Kabir</span>
      <span class="quote-author-job">Founder at Ruby Card</span>
    </span>
  </div>
</blockquote>

## What does that mean in terms of data residency?

We understand that there's an increasing complexity around data processing because of different privacy laws. Although, we're enabling our customers to send emails from different regions, we're not changing our data residency policy. All of our customers' data is still stored in the United States.

## Need a specific region to start using?

If you need a specific region that we don't currently support, just shoot me an email at [zeno@resend.com](mailto:zeno@resend.com) and we can chat more about your specific needs.


We're excited to announce support for multi-region email sending.

Faster Email Delivery with Multi-Region


The first question I get from YC batch mates is: _["How did you get your domain?"](/blog/how-to-pick-a-startup-name)_.

The second question is: _"How did you grow your waitlist?"_.

I'm writing this post to document what went well and what went wrong. Hopefully, this will help other founders who are launching their own waitlists or looking to find potential users.

![Waitlist growth](/blog/static/posts/lessons-learned-from-growing-a-waitlist-1.jpg)

## What went well

**1. Landing page**

We knew that we were entering a space with many consolidated competitors, so it was crucial to show people that we were different. We did that by creating a landing page that was extremely simple but also had unique branding and smooth interactions.

![Resend.com](/blog/static/posts/lessons-learned-from-growing-a-waitlist-2.jpg)

Here's what worked for us:

- **Tip #1 - Show personality** - Adding an animated WebGL object was super important for me. Some people might say it's a distraction, but without saying a word, it communicates that we care about the technical details. Also, the Rubik's cube is the perfect analogy to what we were doing. It's an old thing that people are familiar with, but it's displayed in a new way. The same goes for Resend. We're doing something that people are familiar with (sending emails), but we're doing it in a modern way (using React).
- **Tip #2 - Know your audience** - As a developer, I absolutely love keyboard shortcuts. I couldn't live without them, and I'm sure many other developers feel the same way. Even though a landing page is not a place to add keyboard shortcuts, it was a great way to show that we care about the same things our audience cares about.
- **Tip #3 - Focus on the details** - Most landing pages we visit nowadays follow the same pattern. They use a predefined template that looks like every other landing page. As you start navigating, you might find typos or broken links. I truly believe that the small details make a big difference. If you don't communicate that you care about your own website, then why should someone else care?

**2. Social media posts**

Back in 2009, I created an account on this new social media website called Twitter. There were a few months when I was posting every day, and there were a few months when I wasn't posting at all. I didn't have a strategy, I was just sharing whatever I was working on. After years of doing that, I built a following of 39.4k people. This came in handy when we were launching Resend.

On January 4th, 2023 at 7:11 am PT, I published the [first tweet about Resend](https://twitter.com/zenorocha/status/1610655123063336961). This tweet had 999.3k views, 4,634 likes, 352 retweets, and 282 replies. I'm not a big LinkedIn user, but I did [post the same content there](https://www.linkedin.com/posts/zenorocha_personal-update-im-leaving-my-job-to-start-activity-7016420524977209344-qrUI), and it got 107,411 views, 1,378 likes, and 156 comments.

![Tweet about Resend](/blog/static/posts/lessons-learned-from-growing-a-waitlist-3.jpg)

Here's some tactical advice I learned from this experience:

- **Tip #4 - Post a video** - from all the possible content formats, video is the one that performs best nowadays. If you can't do video, then use an image. Plain text and links perform worst in my experience.
- **Tip #5 - Post early in the day** - when doing a big launch, be aware of the best time to post. I chose 7 am PT because that's when people from California wake up and check their phones, it's still early on the East Coast, and people from Europe have not ended their work day yet.
- **Tip #6 - Post during the week** - I also chose a weekday because people are more likely to be at work and have time to check their social media. In my opinion, Monday isn't a good day to launch because people are getting ready for the week. Friday is also not a good day because people are already thinking about the weekend. That's why we posted on Wednesday.

If you're not into social media, that's totally fine. There are many founders who don't engage on social platforms and still build incredible companies. However, if you're thinking about starting a profile, keep this in mind - the best time to start posting was yesterday, the second best time is today.

**3. Build in public**

After the initial launch, it's important that you keep bringing new people to the waitlist. We did that by sharing our progress publicly.

- **Tip #7 - Keep the momentum** - in order to keep people from the waitlist engaged, we started sending them emails about [company news](https://twitter.com/zenorocha/status/1620809395310583808) and [product updates](https://twitter.com/zenorocha/status/1618633776212631554). This was a great way to keep people interested in what we were doing.
- **Tip #8 - Be personal** - one of the things that I learned with YC is that being vulnerable is not a demonstration of weakness. Being vulnerable shows that you're a human being too. People act like they know everything. In reality, we're all just trying to figure it out. So don't be afraid of [showing the behind-the-scenes](https://twitter.com/zenorocha/status/1612263110370549760).
- **Tip #9 - Build with others** - as you start to share your journey, you'll start to get more people interested in what you're doing. Some of them might want to help you. In our case, that meant other companies building [integrations with our product](https://twitter.com/zenorocha/status/1621204586500591619). We also tried to respond to every single person who engaged with our content.

![Email about Resend](/blog/static/posts/lessons-learned-from-growing-a-waitlist-4.jpg)

## What went wrong

**1. Performance testing**

On the day we launched, we got several complaints about performance issues ([1](https://twitter.com/matloyed/status/1610715639576170496), [2](https://twitter.com/BarzolaGabriel/status/1610677004231131141), [3](https://twitter.com/steren/status/1610757385429319680), [4](https://twitter.com/bernatfortet/status/1611030644301365250), [5](https://twitter.com/jonatasvsalles/status/1610664703516090371)). We knew that people were going to sign up on mobile, but we didn't spend too much time testing the performance on real phones.

!["Slowest landing page I have seen in 2023" Tweet](/blog/static/posts/lessons-learned-from-growing-a-waitlist-5.jpg)

Dealing with performance issues in the middle of a launch is not fun. Small bugs can be dealt right away, but performance improvements typically require deep thinking and a lot of debugging. We ended up fixing all of them, but I wished we had done that before the launch.

**2. Email address validation**

When setting up the waitlist form, we wanted to have something that was easy to use and low friction. There was only a simple input field, and we didn't want to ask people to confirm their email address. Even though we had some back-end validation, people could still add fake email addresses.

![Resend Request Access screen](/blog/static/posts/lessons-learned-from-growing-a-waitlist-6.jpg)

In order to address this, we integrated an email validation service called [Emailable](https://emailable.com) to guarantee that the email addresses were real. If we had better validation from day one, we would have saved a lot of time.

**3. Processing the waitlist**

In the beginning, we didn't have a proper plan to process the waitlist. We found ourselves with a big list of email address and no idea how to prioritize them. What worked for us was building a quick Typeform to understand who were the best people to onboard first.

We initially required every prospect to go through a mandatory onboarding call first (Superhuman style), but we quickly realized that wouldn't scale with our current team size, so we changed it to automatically onboard certain user segments.

![Resend Typeform](/blog/static/posts/lessons-learned-from-growing-a-waitlist-7.jpg)

It's important that you qualify your leads before reaching out to them. If you don't, you'll end up wasting a lot of time with the wrong customer profile.

## Conclusion

A waitlist is a great way to build a community around your product. It's also a great way to get feedback from people who are interested in what you're building.

You will never be 100% ready to launch, and that's okay. There will always be something that you can improve or fix. The best thing you can do is to launch and iterate.

If you're not launching, you're not learning.


The challenges we faced and actionable tips for founders looking to build their own waitlist.

Lessons learned from growing a 6,338 people waitlist in 7 weeks


Whenever I talk to other YC founders in my batch, the number one question I get is:

> "How did you get the [resend.com](https://resend.com) domain?"

Instead of repeating myself, I decided to write this post with two goals in mind:

1. Answer this question in a written format so that I can send a link to whoever asks me that again;
2. Help other founders struggling to find a good name for their startup.

## Picking any name to start

When we began discussing the idea of starting this, we decided we wouldn't spend even 1 minute thinking about naming in the beginning.

We wanted to focus on building the product and nothing else, so we got a domain that combined our first names. My name is Zeno, and my co-founder's name is Bu, so we bought [zeebbu.com](https://zeebbu.com).

I know, I know, terrible name! But it didn't matter. At that point, we were building a prototype and just needed a URL to deploy and test.

## Validating the idea

As the MVP evolved, we realized we needed a better name before sending the link to people.

We were looking for a domain that was free and a little bit easier to type, so we bought [klotty.com](https://klotty.com). We knew that was still a very bad name and definitely not the final one, but it was good enough to start putting it in the hands of early adopters.

One day we applied to [Y Combinator](https://www.ycombinator.com/companies/resend) and got accepted (a crazy story for another day).

So now it was time to go all in. We wanted a strong name, a name that would send a message, a name that could communicate that we were serious about this company idea.

## Having an idea generation framework

We started by brainstorming a list of words that we thought were cool, and then we combined them in different ways. Here are some of the methods we used:

1. Put two random words together:

```
tail-wind, planet-scale, up-stash, super-human
```

2. Combine niche-specific words:

```
git-hub, drop-box, fire-base, mail-gun
```

3. Drop the last vowel:

```
flickr, tumblr, grindr, scribd, checkr
```

4. Pick dictionary word:

```
linear, stripe, convoy, notion
```

5. Invent a word:

```
brex, google, kodak, sony
```

6. Add another letter:

```
dribbble, fiverr, groww
```

At this point, we had a list of dozens of names, but how do you know which one is the best?

<figure>
  <img src="/blog/static/posts/how-to-pick-a-startup-name-1.jpg" alt="Notion page with some initial name ideas">
  <figcaption>Notion page with some initial name ideas</figcaption>
</figure>

## Establishing some guidelines for yourself

We had to narrow down the options somehow, that's why we came up with a system to filter the name ideas and make the decision easier. This was our list of must-haves:

1. **Global** - it needs to be a .com TLD, no exceptions;
2. **Short** - it has to be less than 10 characters, no more than that;
3. **Memorable** - it needs to be connected to the product in some way;
4. **Easy to type** - you can type it on your phone without asking others to spell the name;
5. **Easy to pronounce** - you can tell someone in a bar with loud music in the background, and people can still understand it;

Another good idea is to set a timebox for making this decision. It's easy to go down the rabbit hole and spend months thinking about the perfect name. You need to set a deadline and stick to it.

## Checking what's available

Once you have a list of names, you need to check if they are available. We did this manually by checking the [whois](https://whois.com) records and trying to find the owner. Nowadays, with all the privacy laws, it's much harder to find contact information online, so you need to get creative and look for clues.

One thing I like to do is check the source code of the website or look for [web.archive.org](https://web.archive.org) snapshots to see if there's anything that could help track the owner.

For this part, you have to be prepared to be disappointed. Many people won't return your emails, and you'll have to move on to the next name.

<figure>
  <img src="/blog/static/posts/how-to-pick-a-startup-name-2.jpg" alt="Outreach database to keep track of who responded or not">
  <figcaption>Outreach database to keep track of who responded or not</figcaption>
</figure>

## Understanding the prices

Once you finally get a reply from the domain owner, it's time to start cataloging the initial prices.

It's important that you open multiple negotiations at the same time, so you can compare prices and better understand the market.

Some numbers are just too high, and there's nothing you can do about it. However, you can get a good deal if you play your cards right.

<figure>
  <img src="/blog/static/posts/how-to-pick-a-startup-name-3.jpg" alt="List of available domains and their prices">
  <figcaption>List of available domains and their prices</figcaption>
</figure>

## Negotiating and closing the deal

I'm not going to lie, this is the hardest part. You need to be persistent, and you need to be prepared to walk away at any moment.

When I first saw the asking price for [resend.com](https://resend.com) I was in shock. No way I'd pay $39,999 for a domain.

Still, this was a 6-letter dictionary word domain, so it was worth digging deeper.

<figure>
  <img src="/blog/static/posts/how-to-pick-a-startup-name-4.jpg" alt="Asking price: $39,999">
  <figcaption>Asking price: $39,999</figcaption>
</figure>

I replied to the email with a lowball offer of $7,999 and waited for a response.

For sure I was going to get a rejection, but this was a test to see if they were willing to negotiate or not.

<figure>
  <img src="/blog/static/posts/how-to-pick-a-startup-name-5.jpg" alt="Initial counteroffer: $7,999">
  <figcaption>Initial counteroffer: $7,999</figcaption>
</figure>

They sent a counteroffer of $35,000, and we started negotiating.

After a few of days of back and forth, we settled on $25,000.

<figure>
  <img src="/blog/static/posts/how-to-pick-a-startup-name-6.jpg" alt="Deal closed for $25,000">
  <figcaption>Deal closed for $25,000</figcaption>
</figure>

I can't tell you how happy I was when they finally transferred the domain.

It was a long and painful process, but it was worth it.

## Conclusion

It's easy to think that a good name is the key to success, but that's not true. You can have the best name in the world, but if you don't have a good product, you won't get anywhere.

Paul Graham once wrote an essay called [Change Your Name](http://www.paulgraham.com/name.html), and he said:

> If you have a US startup called X and you don't have x.com, you should probably change your name.

Of course, every rule has exceptions. Just look at [notion.so](https://notion.so) and [linear.app](https://linear.app). These companies are winning not because of their domains but because of their amazing products.

The ultimate value of a domain name depends on how well it is utilized.


Thoughts on the importance of choosing a strong brand name, challenges of finding an available domain, and tips on how to better negotiate and acquire a domain.

Why I spent $25,000 on a domain (or how to pick a startup name)


Our goal is to reimagine how email can be done in 2023 and beyond. With YC, we have the right partners to make this a reality.

## What is Resend again?

Resend is an email API for developers. You can think of it as a next-generation Sendgrid.

Since launching 4 weeks ago, we got 4,949 people on the waitlist, and our open source project ([react.email](https://react.email)) is already at 4,168 stars on GitHub.

## Why YC?

I've always seen YC as the best startup accelerator out there. Companies like Airbnb, Stripe, Dropbox, Gitlab, Zapier, and Supabase all came out of it.

Being a part of this program with such a fantastic group of founders and partners is really special.

Together with [Bu Kinoshita](https://twitter.com/bukinoshita) and [Jonni Lundy](https://twitter.com/jonnilundy), we’re participating in the Winter ‘23 batch.

This is just the beginning of a new journey and I'm looking forward to sharing every step of the way with you all!


We're excited to announce that Resend is now backed by Y Combinator.

Resend + Y Combinator


## Why are we doing this?

When I was a CPO at [Liferay Cloud](https://liferay.com), I faced the problem of sending emails at scale.

We had high-profile customers complaining about deliverability, and I've been frustrated with existing services ever since.

More recently, as a VP of Developer Experience at [WorkOS](https://workos.com), I once again had to deal with emails landing in the spam folder.

After looking at all the different solutions out there, I've been obsessed with the idea of solving this problem once and for all.

We first launched [react.email](https://react.email) to help developers write modern email templates.

As I started to dig deeper, it became clear that this was just the tip of the iceberg.

Sending emails is the biggest pain point, so we started to explore something new.

## What problem are we solving?

We're building a communications platform, and we're starting with email.

The idea is for you to send messages with easy-to-use APIs/SDKs without having to worry about emails going to the spam folder.

Think of it as a next-generation Sendgrid.

## Why now?

When you look at all the biggest competitors, you'll notice that they were all founded around 2009/2010, and they all have been acquired by now.

Because of that, it's common to see them only prioritizing enterprise requirements and optimizing for sales-led growth.

Nobody is building an exceptional developer experience. Nobody is trying to innovate.

There isn’t a single developer-first email platform in the market today. We want to change that.

We need to stop developing emails like 2010 and rethink how email can be done in 2023 and beyond.

Email development needs a revamp. A renovation. Modernized for the way we build apps today.

## Join us

I'm really excited to take on the role of founder & CEO and to create an elite team of builders.

We're creating something special here, and I can't wait to share it with you.

Join the waitlist and you'll be the first to try it out: [resend.com](https://resend.com).


Why are we doing this? What problem are we solving? Why now?