Resend on X

Praise takes a few forms. Builders show finished work: an email-digest agent built on the Resend connector for Sprites, a product's welcome email sent through broadcast, an open-source inbox package layered on Resend's receiving. One poster says a real-estate agent picked it because ChatGPT recommended it, and treats that as dev tools reaching non-developers. Others recommend it with a reason attached — preferring to pay than maintain email themselves, since "email is hard, spam, delivering."

Developer experience is where the words get specific: an integration inside Laravel Cloud that took "literally 60 seconds" while DNS propagated, setup that usually is "a pain for devs" going through on the first try, onboarding named alongside other companies' as great, React and TypeScript email as a stack teams standardize on. One reply argues the error path — a precise diagnosis and one actionable next step — is half the product.

A smaller group likes the company: a customer turned fan of "how they move" after its Forward event, someone who calls working with the team a joy.

The reservations are thin: a user of four years says it does the job while calling the API dated and support tired; another had a sending issue the team resolved.

The deliverability point is a warning, not a bug report: people say the tool sends, but monitoring, IP warming, list checking and cleanup, DNS and blacklist monitoring stay yours, and one argues that work is better outsourced to something like beehiiv. A support reply makes the same distinction from the other side — "delivered" means the recipient's server accepted it, so a missing email is usually the recipient's filtering — after a user reported mail that never arrived.

On cost, one person left for Cloudflare, whose five-dollar Workers paid plan they say comes with a thousand sends a day; another moved to an in-house replacement to cut the monthly software bill. A third asks the company to stop charging for domains and charge only for emails sent.

Support complaints are about speed: a reply telling Resend it is "missing out on business" because competitors answer faster, and a four-year user calling the API dated and customer service tired. Sign-up friction is two cases: a "Something went wrong" error for three days and a hunt for the log out button.

The calendar thread is one developer's: the API will not put an invite in the body, so the .ics goes as an attachment and iCloud users get no RSVP options.

The AWS thread is the live argument. One side asks the plain question — why not use SES directly, why pay anyone — and a reply says people do not want to work with AWS directly, listing what sits around the send: domain warmup, subscription management, analytics. Another says Resend runs on SES "behind the scenes anyway," and one praises Resend after having implemented SES. Someone leaving the other way says they stopped using AWS's sending service and are moving to Resend for reliability.

Cloudflare is a cost and vendor argument: a five-dollar Workers paid plan said to include a thousand sends a day, an already-present domain making its email service "one less vendor," and email handling now available there.

Mailtrap draws a pricing breakdown — free tiers of three thousand versus four thousand a month, pro at twenty dollars for fifty thousand emails against fifteen dollars for ten thousand — with a reply calling both free tiers generous and both pro tiers brutal. Loops appears as a place people left for Resend, "dodged a bullet," or as one Resend "completely smoked."

The tail: Postmark named as "the one," a four-hundred-dollar-a-month Mailchimp bill someone wants to escape, a free-limit comparison with Brevo, and a switch to an in-house build to shrink the software bill.

The Inboxes questions are practical, about running a mailbox an agent answers: can webhooks be set up per inbox or must routing live in your webhook code — the answer, from Resend's side, is that routing is in your code for now and is being looked at — plus how to stop an agent treating every inbound message as equally urgent, and what happens when a human starts replying while an agent is drafting: does ownership transfer and the agent's send get invalidated, so two sensible replies do not both reach the same customer?

On price, the questions read as expectations rather than negotiations: "Resend should become cheaper now?", whether it can "compete with AWS SES on price," and whether per-domain charging could give way to charging only for emails sent.

The compliance ask is direct: do they manage compliance, suppressions and deliverability in-house? The other wants to know whether an EU-hosted option exists where data stays in the EU.

The server-card question comes with its own answer from a user — not many clients read it yet (it is AMP), but support looks to be coming soon.

On Inboxes, the request starts from enthusiasm — one builder says they were waiting for exactly this — then asks about POP3/SMTP support, or at least aliases and redirection to a regular mailbox. A reply from Resend's side says SMTP connectivity and auto-forwarding to an external address are known gaps they will look at, and that the flow works the other way today: an existing mailbox can be forwarded into an inbox. The person then lists the limitations they still see.

The guardrail asks come from one developer and one team, both worried about collisions in a shared human-plus-agent inbox: an atomic claim or assignment state so a human and an agent don't both answer a customer from slightly stale views, and an answer to whether ownership moves when a person starts typing, invalidating the agent's draft. The other keeps one rule for outbound: the agent drafts and queues, a human approves before anything reaches a customer.

The rest are single asks: a way to block spam senders without those sends counting against the monthly quota, currently handled with a Cloudflare Worker; passing an OTP-Token header through without MIME-encoding it; and an email client app, which one user says would keep them "for life."