Earlier quoted context omitted.
Are there any unpublished limits for this? Asking for a friend :)
There are no unpublished limits. I'm the CEO. We don't specifically limit Cloudflare traffic.
How does this work if we don't need to validate domain?
Launch HN: Resend (YC W23) – Email API for developers using React
231–240 of 277 posts
Re: Launch HN: Resend (YC W23) – Email API for developers using React
#232Why limit it to 100 emails a day for the free plan? Makes the 3000 limit feel like a false advertisement unless you have 100 users signing up every day.
> false advertisement
No, very clear, quite literally right below
"
Up to 3,000 emails / mo
100 emails / day
"
Re: Launch HN: Resend (YC W23) – Email API for developers using React
#233Just use Mailgun.
Re: Launch HN: Resend (YC W23) – Email API for developers using React
#234Earlier quoted context omitted.
@ctas since you're running your own backend, how did you solve the reputation problem to ensure good deliverability? I would have thought that using a dedicated IP on an existing provider like Sendgrid would be the best solution for critical transactional email.
There's no one-size-fits-all-solution to ensuring good deliverability. Dedicated IPs are often (not always) a sign of weakness as they indicate that the shared IP pool lacks good reputation. We run an exclusive transactional email service, meaning customers go through an approval process before they can send live emails. Transactional emails by definition are sent as a reaction to a users' action and _should_ therefo…
> We run an exclusive transactional email service
What's this service called? A link also works. Imagine many people in this thread are looking for alternative transactional email services...
Re: Launch HN: Resend (YC W23) – Email API for developers using React
#235I have been looking for a basic Mailgun type transactional email service for my React based project, and I believe this is exactly what I need. I asked Adam to think about designing some reusable transactional email templates for Tailwind UI a few months ago. It looks like Resend would pair right up with Tailwind perfectly :) I added Resend to my R&D to do list, and I hope to partner up soon: https://github.com/elega…
That's pretty cool! You should definitely try Resend if you're already using Next.js, React, and Tailwind. This should be a good place to start: https://react.email/docs/components/tailwind
Hey Zeno, thanks for the resources! The Tailwind component looks perfect.
What's the best way to contact you and link up virtually?
I'd love to talk about Resend more, and show you what I'm cooking up. I really like what you are doing, and I think we share the same cohort of users :fistbump:
Re: Launch HN: Resend (YC W23) – Email API for developers using React
#236Earlier quoted context omitted.
There are no unpublished limits. I'm the CEO. We don't specifically limit Cloudflare traffic.
How does this work if we don't need to validate domain?
We have a lot of anti-spam capabilities in the platform and if you abuse the service to send actual spam, your account may be rate limited or blocked. But if what you are sending is good email and we don't see signals to indicate it is abusive, then there aren't any limits on how much you can send.
Re: Launch HN: Resend (YC W23) – Email API for developers using React
#237Help me understand the React selling point. Existing email sending software supports text and HTML because that's what email is . No email client out there supports JavaScript, virtual DOMs, event loops, SSR or any such fancy web technology. Instead of hand-crafting an HTML template with etc I'm supposed to use your custom React components ( ...) which you will promptly compile down to the tags I mentioned above. So.…
You get the comfort of using react components instead of fighting with HTML tables to make your emails look nice. I think it's awesome! It's analog to what ink[0] does with CLI outputs. Sure, you could write fancy CLI outputs in bash, but ink takes the pain out of it and makes it easy. [0] https://github.com/vadimdemedes/ink
It's also like react-pdf, where they give you react components to easily build out a PDF document without getting into the nitty gritty of the PDF spec. I'm a fan of this paradigm
Re: Launch HN: Resend (YC W23) – Email API for developers using React
#238Not for nothing... your site (resend.com) is a HUGE CPU hog. I didn't get a chance to view or read anything on the site because I quickly closed the tab after my CPU rocketed up.
Would you mind sharing what computer/OS/browser you're using so we can try to reproduce on our end?
I'm using Firefox on Android on an S21 FE 5G and having the page as the active tab without any interaction seems to cause 30% CPU usage in my about:processes listing.
Re: Launch HN: Resend (YC W23) – Email API for developers using React
#239Earlier quoted context omitted.
I think he may have wondered how would, say a Python backend using Resend Python SDK, render a React Email template and send it. Their API docs [1] for "Send Email" has an option for specifying a 'react' component to render the message but it's only available on the NodeJS SDK. Otherwise you pass HTML and/or Text. Personally, I was expecting the api to optionally accept a React Template, along with the Data, where up…
Exactly this. Said differently - how many devs out there are screaming "I really need to send transactional email via React", when most apps are sending it via Python, Ruby, PHP, Java, and (back-end) JS.
I think you’re conflating terms (or possibly concepts) here. This isn’t about sending emails via React; this is about sending HTML emails generated from React components via a backend. The examples shown on the landing page are of Node.js, Next.js route handlers and Remix loader functions, the latter two being fancy abstractions over Lambda functions (or isolates).
I agree that sending an email from React doesn’t make a lot of sense, but that’s not the target at which this is aiming.
Re: Launch HN: Resend (YC W23) – Email API for developers using React
#240Earlier quoted context omitted.
As long as you stick to only HTML that was available in the year 2000, and use zero CSS, your mails will come out the same in pretty much every client.
Absolutely, but show what this will look like to the marketing team and they will, probably rightly, tell you that times have changed. For a major brand, CSS and pretty design is a requirement for all branded emails.
You can do all of that without CSS though. It’s just harder.
For that having a React wrapper that makes the hard parts easy makes total sense.