---
title: "400,000 users and beyond"
slug: 400-000-users-and-beyond
description: "The path that brought us here and where we're headed next."
created_at: "2025-04-29"
updated_at: "2025-04-29"
image: https://cdn.resend.com/posts/400-000-users-and-beyond.jpg
humans: ["zeno-rocha"]
featured: true
category: "company"
---

Last April, we celebrated [going from 0 to 100,000 users](/blog/what-is-next-after-100-000-users).

A lot has changed since then.

Here's a quick look back at what we've done and what's coming up.

## TL;DR

In one year, we went from:

* **100k → 400k** users
* **6 → 21** team members
* **12k → 15k** stars on [GitHub](https://github.com/resend/react-email)
* **209k → 421k** weekly [downloads on npm](https://www.npmjs.com/package/react-email)

## What's next?

Resend is now powering **millions of emails sent every single day**, and we're only just getting started.

Our goal is for Resend to become the **default email platform** for developers.

To get there, we'll keep **talking to you**, our users, and listening to your feedback.

Here's how we're seeing the path to 1M users:

## 1. One-of-a-kind developer experience

The engineering team doubled in size, so we can keep improving the product and making the **developer experience even better**.

We improved the experience of [verifying domains](/changelog/new-domains-workflow), added support for [multiple teams](/blog/multiple-teams), built an integration with [Vercel](/blog/vercel-integration), shipped new SDKs for [Rust](/changelog/announcing-the-rust-sdk) and [.NET](/changelog/announcing-the-dotnet-sdk), and much more.

Over the next few months, you can expect to see:

* **Faster API** response times
* More features for you to **extend the product**
* **Broader tutorials**, documentation, and examples

As we enter a new era, where agents are taking more actions than humans, we'll make sure Resend is ready for it, too.

We're actively [exploring AI in many ways](/blog/agent-experience), including the development of an [MCP server](https://github.com/resend/mcp-send-email) and taking email templating to the next level with [new.email](https://new.email).

<LinkCard
  title="Introducing new.email"
  description="Why are we doing this? Why now?"
  url="/blog/introducing-new-email"
  image="https://cdn.resend.com/posts/introducing-new-email.jpg"
/>

## 2. World-class deliverability

Email is not a new thing, but it is a complex one.

We're leveraging our expertise to produce educational guides like the ["How to warm up a new domain"](/blog/how-to-warm-up-a-new-domain) so people can keep improving the quality of their emails.

Still, we believe **the best advice is contextual**, and that's why we're bringing all the email deliverability best practices into the product in two ways:

First, we're deeply committed to open source tools like [React Email 4.0](/blog/react-email-4), which comes with a built-in linter, compatibility checker, and spam score.

Second, we're bringing education directly into the product with [Deliverability Insights](/changelog/deliverability-insights-ga), which is now available for free for all users.

<LinkCard
  title="Deliverability Insights GA"
  description="Deliverability Insights is now generally available for free for all Resend users."
  url="/changelog/deliverability-insights-ga"
  image="https://cdn.resend.com/posts/deliverability-insights-ga.jpg"
/>

## 3. Great support by default

We believe great support is a core part of what makes Resend unique.

And when it comes to support, actions speak louder than words.

* **20,209 customers helped** all over the world
* **98.6% of tickets are solved** within the same business day
* **1h 29m is the median first response time** for urgent tickets

_Real data gathered via [Plain](https://plain.com) for the past 60 days._

We want to help people with their emails, regardless of how big or small their company is, or where they are located in the world.

That's why we recently expanded our support SLA to include **European timezones**.

Our goal is to build a product that reduces the need for support in the first place, so we'll continue to **invest time in docs and knowledge base** articles. Still, when you just need to talk to a human, we'll be there for you.

<LinkCard
  title="How Gumroad Migrated 100M Emails to Resend"
  description="Learn how dedicated IPs can improve your email deliverability and reduce the risk of your emails going to spam."
  url="/blog/how-gumroad-migrated-100m-emails-to-resend"
  image="https://cdn.resend.com/posts/how-gumroad-migrated-100m-emails-to-resend.jpg"
/>

## 4. Enterprise grade security

We are always looking for ways to improve our security measures.

In the past few months, we:

* Became [GDPR compliant](/blog/gdpr)
* Certified by the [Data Privacy Framework](/changelog/data-privacy-framework-certification)
* Renewed [SOC 2 report](https://x.com/resend/status/1914324536977461344) for the second year with zero findings

We'll continue to improve our security posture, including **running pen tests constantly**, reducing third-party dependencies, and moving more of our infrastructure in-house.

<LinkCard
  title="Resend's journey to GDPR compliance"
  description="Our path to complying with GDPR and continuing our commitment to protecting your data."
  url="/blog/gdpr"
  image="https://cdn.resend.com/posts/gdpr-compliance.jpg"
/>

## 5. Treat uptime like water

We can have the most beautiful product, the best support team, and the fastest API in the world, but if it's not online, then it's all for nothing.

Reliability is the **foundation of everything we do**, and every time there's downtime, we lose trust. That's why uptime is so important to us.

We shipped multiple improvements to our foundational services recently. These include migrating from two cloud providers, revamping the storage of millions of email events, and re-architecting our email sending workflow to make Resend more resilient.

At the end of the day, we're providing infrastructure, just like water, energy, banking, and transportation. So you can expect even more investments in reliability.

[Acquiring Mergent](/blog/resend-acquires-mergent), which has a stellar uptime and scalability track record, is just one of the steps we're taking to provide the most reliable service possible.

<LinkCard
  title="Resend acquires Mergent"
  description="A major step in becoming the best communication platform for developers."
  url="/blog/resend-acquires-mergent"
  image="https://cdn.resend.com/posts/resend-acquires-mergent.jpg"
/>

## Conclusion

If you had asked me a year ago if we would 4x our users in just 12 months, I wouldn't have believed you.

This is only possible because of you. Thank you for using the product, talking to your friends about it, and telling us what you like and what you don't.

We're just getting started.