Resend says Forge, its own sending infrastructure, is now available to every customer

Resend says Forge, the sending infrastructure it built and operates itself, is now available to every customer. In a post on Tuesday the company described “85% speed improvements,” a “99+% deliverability rate” and “2 minutes to activate,” and published a walkthrough of turning it on.

Resend Forge, our new sending infra, is available to everyone: 85% speed improvements, 99+% deliverability rate, 2 minutes to activate.

— Resend (@resend) November 10, 2026

Forge is not a brand-new announcement. Resend introduced it earlier as its own mail transfer agent, sending from IP blocks the company owns, so there is no third-party sender between the API call and the address a message leaves from. The October announcement said hundreds of customers had already sent more than 10 million emails through it, named Profound, Firecrawl, Clay and OTown among them, and said activation needed one CNAME record and no code changes.

What Resend’s own metrics show

The company’s Forge page publishes live measurements, which it says are updated from monitoring. “Delivered” means the receiving server accepted the message; “bounced” means it refused. Resend says it leaves out refusals no sending engine could have changed, such as a full mailbox, a message that is too large, a rejected attachment, or an address the receiver says does not exist, and that everything else stays in, so the figure is “still stricter than a pure reputation figure.”

A comparison on that page, covering the last seven days and split by engine, puts median time from the API call to the receiver accepting the message at 0.8 seconds on Forge and 1.5 seconds on the legacy engine, including its third-party provider, or 77% faster across all providers. Google is also shown as 77% faster (0.8 seconds versus 1.4). Yahoo and Outlook are slower improvements, at 36% and 32%. Apple is listed as on par, at 4.9 seconds on Forge and 4.8 seconds on the legacy path. Those medians are not the same as the “85% speed improvements” in the launch post, and they are Resend’s own figures.

Receiver	Legacy median	Forge median	Resend’s comparison
All providers	1.5s	0.8s	77% faster
Google	1.4s	0.8s	77% faster
Yahoo	1.9s	1.4s	36% faster
Outlook	3.0s	2.3s	32% faster
Apple	4.8s	4.9s	On par

The same page also reports how much mail is accepted within set windows: 94.13% of Forge messages within five seconds, against 91.98% on the legacy engine, and 99.98% within three minutes, against 98.74%. That is time-to-accept, not a separate inbox-placement rate, so it should not be read as a direct measurement of the “99+%” deliverability line in the post.

How activation actually works

According to Resend’s documentation, customers look for “Activate Resend Forge” on a domain’s configuration tab and add the DNS record shown there. Once that record is verified, the account becomes eligible, and Resend says it onboards the domain automatically after its systems have “established you as a good sender.” That reputation gate exists, the company says, to protect the shared IP pool. The “2 minutes to activate” claim in the post is not the same as this documented path, which still depends on DNS verification and those checks.

Code, SMTP credentials and webhooks stay the same. If a message cannot be completed on Forge, Resend says delivery can fall back to the engine it has used for years. Open and click tracking are not supported on Forge yet; mail for domains that have those features enabled is automatically sent on the legacy engine, while other mail can go through Forge.