Amazon Web Services quietly rewrote the economics of transactional email on July 21, 2026, when it retired the flat $0.10-per-1,000 Simple Email Service rate for new accounts and replaced it with tiered Essentials, Pro, and Enterprise plans. That single pricing change forced a fresh round of comparisons between the three services developers actually reach for when an app needs to send a password reset, an invoice, or a marketing digest: Resend, Twilio SendGrid, and Amazon SES. Each one now sits at a different point on the cost, control, and developer-experience spectrum, and picking wrong can mean paying nine times more per email than necessary or losing days to a clunky integration.
This comparison breaks down real September 2026 pricing, API design, deliverability data, and rate limits for all three, then walks through migration steps and use-case recommendations so you can match the platform to your actual sending volume instead of guessing.
The three services rarely get compared fairly because they were built for different jobs. Resend launched as a Y Combinator startup aimed squarely at developers who wanted email to feel like any other npm package. SendGrid grew up as an independent email service provider before Twilio acquired it, and its feature set still reflects a decade of enterprise procurement cycles and marketing-team requirements. Amazon SES was never a standalone product at all. It is a primitive inside AWS, priced and operated the same way S3 or DynamoDB is, which explains both its rock-bottom cost and its lack of any consumer-friendly dashboard. Understanding that history helps explain why a direct price-per-email comparison, while useful, only tells part of the story.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Resend vs SendGrid vs Amazon SES at a Glance
Before digging into pricing tiers and deliverability numbers, here is how the three platforms stack up on the specs that matter most for a typical engineering team choosing an email API in 2026.
| Spec | Resend | SendGrid (Twilio) | Amazon SES |
|---|---|---|---|
| Free tier | 3,000 emails/mo, 100/day cap | 100 emails/day for a 60-day trial | No dedicated free tier for new accounts since July 2026 |
| Cheapest paid entry | $20/mo (Pro, 50,000 emails) | $19.95/mo (Essentials, 50,000 emails) | $0.10/1,000 emails, a la carte, no minimum |
| Cost per 1,000 at 100K/mo | $0.35 (Pro $35 tier) | $0.3495 (Essentials 100K) | $0.16 (Essentials plan) or $0.10 (a la carte) |
| Overage rate | $0.90 per 1,000 | About $1.10 per 1,000 (Pro tier) | Flat rate per plan tier, no separate overage |
| Dedicated IP | $30/mo add-on | Bundled at Pro ($89.95/mo) or $30/mo extra | $24.95/mo standard, or $15/mo plus $0.08/1,000 managed |
| SSO | $150/mo add-on | Included on Pro and Premier | Handled through AWS IAM, no separate charge |
| React Email support | Native, first-class SDK | Not supported natively | Not supported natively |
| Primary integration path | HTTPS API, Vercel/Next.js marketplace app | REST API and SMTP relay | API, SMTP, deep AWS service integration (Lambda, SNS, CloudWatch) |
| Attachment cost | Included in plan | Included in plan | $0.12 per GB |
| Rate limit note | No daily cap above the free tier | Email Activity API capped at 6 requests/minute since Dec 9, 2025 | Sending rate tied to account reputation and region quota |
| Recorded major incidents | No widely reported outage in 2026 | 32 major/critical incidents since 2015 (status page history) | Standard AWS regional SLA, tracked via AWS Health Dashboard |
| Best fit | Startups, Next.js/Vercel apps, small teams | Enterprise SaaS mixing marketing and transactional | AWS-native backends, cost-sensitive high volume |
Three things jump out immediately. Amazon SES is still the cheapest raw sending option if you stay on the legacy a la carte rate. Resend is the only one of the three built specifically around modern frontend frameworks. And SendGrid is priced like an enterprise tool because it is one, complete with subuser management, dedicated account teams at the Premier tier, and a feature set built up over more than a decade as a Twilio product.
What Is Resend?
Resend is a Y Combinator-backed email API built for developers who write React and TypeScript, not marketers who click through drag-and-drop template builders. Its entire pitch rests on one idea: emails are just React components, and the Resend SDK ships them through a plain HTTPS call instead of forcing teams to manage SMTP connections or wrestle with a legacy templating language.
The integration that put Resend on the map for most developers is its official Vercel Marketplace listing, which lets a team generate an API key and start sending from a serverless or edge function within minutes. Resend also ships a dedicated Vercel template pairing Next.js, React Email, and its own SDK, and the company confirmed in September 2026 that this template is now the recommended starting point for new projects on the platform. That tight loop between framework, template library, and API is the biggest reason teams pick Resend over incumbents that predate the React ecosystem entirely.
On the business side, Resend keeps pricing simple by design: a free tier, a Pro tier at $20 a month, and a Scale tier that climbs from $90 a month for 100,000 emails up toward roughly $1,150 a month at 2.5 million emails, according to pricing breakdowns published by FlexPrice’s 2026 Resend cost guide. There is no quote-only enterprise tier hiding behind a sales call for teams under a few million emails a month, a sharp contrast to how SendGrid and SES structure their top plans.
What Is SendGrid?
Twilio SendGrid has been the default choice for transactional and marketing email at mid-size and enterprise companies for more than a decade, and its 2026 pricing structure reflects that maturity. The platform runs on four tiers: a 60-day free trial capped at 100 emails a day, an Essentials plan starting at $19.95 a month for 50,000 emails, a Pro plan at $89.95 a month for 100,000 emails that scales to 2.5 million, and a custom-quoted Premier plan for senders above roughly 5 million emails a month.
What separates SendGrid from the other two is depth of feature set rather than raw price. Every paid tier includes REST and SMTP relay support, event webhooks, and a dynamic template editor, while the Pro tier adds a bundled dedicated IP, subuser accounts for managing multiple sending identities under one roof, and deliverability insight tooling that smaller teams rarely need. That subuser system is why large SaaS platforms running white-label or reseller programs still default to SendGrid. One account can host dozens of isolated sending identities with separate reputation tracking, something neither Resend nor a raw SES setup handles out of the box.
SendGrid’s maturity carries a maintenance cost, too. Twilio changed the rate limit on the Email Activity API on December 9, 2025, dropping it from 30 requests per five-minute window down to 6 requests per minute, a change that broke dashboard integrations for teams polling the API aggressively. Twilio’s own status page shows a steady cadence of maintenance windows through 2026, alongside a historical record of 32 major or critical incidents since 2015 tracked by third-party uptime monitors. None of that makes SendGrid unreliable by industry standards, but a platform this old carries more operational scar tissue than a five-year-old challenger.
SendGrid also remains the only one of the three built around a genuine marketing-and-transactional hybrid model. Its dynamic template editor supports drag-and-drop design for non-engineers, contact list segmentation, and A/B testing tools that neither Resend nor raw SES attempt to replicate. That breadth is why marketing teams at mid-size companies frequently push engineering toward SendGrid even when a leaner transactional API would technically suffice for password resets and receipts. The tradeoff is that a platform built to serve both audiences at once inevitably carries more surface area, more settings screens, and a steeper onboarding curve for a developer who just wants to send one templated email from a webhook handler.
What Is Amazon SES?
Amazon Simple Email Service has spent over a decade as the default answer for any team already running infrastructure on AWS. Its pitch is not developer experience or feature richness. It is price, control, and native integration with Lambda, EventBridge, SNS, IAM, and every other AWS service that already sits in a typical backend stack.
On July 21, 2026, AWS restructured SES pricing in a way that changes the math for new accounts. According to the official AWS announcement, every new SES account created after that date starts on the Essentials plan rather than the old free tier, and the historical allowance of 62,000 free emails a month for EC2-hosted senders is closed to new customers entirely. The legacy a la carte rate of $0.10 per 1,000 outbound emails still exists and remains technically the cheapest option on this list, but Essentials now charges $0.16 per 1,000 for the first 10 million emails a month, $0.14 per 1,000 from 10 to 100 million, and $0.11 per 1,000 above that. Pro and Enterprise plans add fixed monthly fees of $105 and $500 respectively on top of slightly higher per-email rates, in exchange for bundled dedicated IPs and Virtual Deliverability Manager access.
The official SES pricing page confirms the tiered rate bands and makes clear that engineering teams provisioning new accounts today need to model both the a la carte and Essentials paths before committing, since the two can produce very different bills at the same volume. A workload sending 100,000 emails a month costs $10 flat on the legacy rate but $16 on Essentials, a 60% jump for functionally the same service.
SES also differs from Resend and SendGrid in how it treats new customers before they can send at all. Every new account lands in the SES sandbox by default, which restricts outbound mail to a small set of verified test addresses until AWS reviews and approves a production access request. That review typically clears within a few hours to two business days, but it means SES is the only one of the three platforms where a team cannot simply generate an API key and start sending to real customers the same afternoon. Teams that plan a product launch around SES need to file that request well ahead of any hard deadline.
SDKs, Frameworks, and Ecosystem Fit
The gap between these three platforms shows up most clearly in how they fit around the rest of a team’s stack. Resend leans entirely into the JavaScript and TypeScript ecosystem. Its Vercel integration announcement describes a setup flow where a project owner links a Vercel project, generates a scoped API key, and stores it as an environment variable without ever leaving the Vercel dashboard. That same pattern extends to Resend’s official SDKs for Node, Python, Ruby, PHP, Go, and Rust, though the React Email integration remains the feature that draws most new signups, since it lets a team version-control email templates the same way it version-controls UI components.
SendGrid’s SDK coverage is broader in raw language count, reflecting its longer history, with official libraries for C#, Go, Java, Node.js, PHP, Python, and Ruby, plus a mature set of community-maintained integrations for frameworks like Laravel and Django. Amazon SES, by contrast, does not ship a dedicated SDK at all. It rides on the general-purpose AWS SDK, meaning a Node.js team calls SES through the same @aws-sdk/client-sesv2 package it would use for S3 or DynamoDB, which keeps credential and IAM handling consistent across an entire AWS-based backend but adds a layer of AWS-specific boilerplate that Resend and SendGrid avoid by design.
Pricing Breakdown: What You Actually Pay at Scale
Sticker prices rarely tell the full story once volume climbs. The table below models effective cost per 1,000 emails at four common sending volumes, using each provider’s standard published plan (Resend Pro/Scale, SendGrid Essentials/Pro, and SES Essentials, with the SES a la carte rate noted separately since it requires manual account configuration rather than a default plan).
| Monthly volume | Resend | SendGrid | Amazon SES (Essentials) | Amazon SES (a la carte) |
|---|---|---|---|---|
| 10,000 emails | Free ($0) | Free trial only (60 days) | $1.60 | $1.00 |
| 50,000 emails | $20.00 | $19.95 | $8.00 | $5.00 |
| 100,000 emails | $35.00 | $34.95 (Essentials) or $89.95 (Pro, with dedicated IP) | $16.00 | $10.00 |
| 500,000 emails | $350.00 | Roughly $220-260 on Pro tiering | $80.00 | $50.00 |
The pattern holds across every volume tested: Amazon SES’s a la carte rate is the cheapest raw sending cost by a wide margin, roughly a third of what Resend or SendGrid charge at 100,000 emails a month. But that price comparison ignores everything SES does not include out of the box. There is no template editor, no built-in analytics dashboard, and no managed deliverability tooling unless a team pays extra for the Virtual Deliverability Manager or builds its own reporting layer on top of CloudWatch and SNS. Resend and SendGrid both fold dashboard, template, and webhook tooling into the base price, which is part of why they cost more per email.
SendGrid’s Pro tier is worth flagging separately because its sticker price of $89.95 for 100,000 emails looks worse than Essentials at $34.95 for the same volume, until you account for the bundled dedicated IP, which would otherwise cost $30-plus a month on Resend or $24.95 on SES. Teams evaluating SendGrid Pro against a competitor’s base plus add-ons should always compare the fully loaded price, not the headline number.
Add-on costs compound faster than most teams expect once a product scales past its initial launch. A startup that begins on Resend Pro at $20 a month, adds a dedicated IP at $30, and later adds SSO for a security-conscious enterprise customer at $150 a month is suddenly paying $200 a month before counting a single email beyond the base 50,000 allowance. Run the same math on SendGrid Pro, where the dedicated IP is already bundled but SSO and subuser tiers push the effective price toward $150-250 a month depending on configuration, and the two platforms land closer together than their headline prices suggest. SES avoids most of these line items entirely since dedicated IPs are billed a la carte and SSO rides on existing AWS IAM at no extra charge, which is part of why cost-sensitive teams gravitate toward it once volume and add-on requirements both climb.
Deliverability and Inbox Placement
Pricing only matters if the email actually lands in the inbox. All three providers support the same core authentication stack, SPF, DKIM, and DMARC, and all three let a sender configure custom domain authentication rather than relying on a shared subdomain. Where they diverge is in the tooling built around that foundation.
SendGrid ships deliverability insights and subuser-level reputation tracking as part of its Pro tier, aimed at teams that need to isolate a bad sender from a good one inside the same account. Amazon SES offers the Virtual Deliverability Manager, a bolt-on analytics layer that surfaces bounce, complaint, and reputation data across sending identities, billed separately from base sending costs on some plan tiers. Resend keeps its deliverability tooling simpler, leaning on domain-level dashboards and recommending dedicated IPs once a sender crosses roughly 3,000 emails a day, the same threshold where its free tier’s daily cap becomes a practical ceiling anyway.
None of the three publish a head-to-head inbox placement study against each other, which is common in this market since deliverability depends heavily on sender reputation, list hygiene, and content, not just the platform. The practical takeaway for engineering teams is that authentication setup and warm-up discipline matter more than the provider chosen, though dedicated IPs on any of the three meaningfully reduce the risk of shared-IP reputation problems once volume grows past a few hundred thousand emails a month.
Developer Experience and API Design
This is where the three platforms feel most different in daily use. Resend’s SDK is built around a single HTTPS call, no SMTP connection pooling, no queue management on the client side, and first-class TypeScript types. A minimal send from a Node or edge function looks like this:
import { Resend } from 'resend';
const resend = new Resend(process.env.RESEND_API_KEY);
await resend.emails.send({
from: '[email protected]',
to: '[email protected]',
subject: 'Welcome aboard',
react: WelcomeEmail({ name: 'Alex' }),
});That single call replaces what would otherwise be a React Email render step, an SMTP transport configuration, and a manual HTML string assembly on SendGrid or raw SES. SendGrid’s REST API and SMTP relay both work well and are documented thoroughly after more than a decade in production, but the platform was not designed around component-based templating, so teams that want React Email support on SendGrid have to build their own render-and-send wrapper.
Amazon SES sits at the opposite end of the developer experience spectrum from Resend. It is a low-level primitive, not a polished product. Sending an email means either calling the SES API directly, routing through the SMTP interface, or wiring up Lambda functions triggered by EventBridge or SNS. That flexibility is exactly why AWS-native teams like it: SES becomes just another IAM-scoped resource inside an existing Terraform or CloudFormation stack, with the same access control and observability patterns the rest of the infrastructure already uses. Teams already comfortable with managing AWS Secrets Manager or configuring Cognito user pools tend to find SES a natural extension of the same toolkit, while teams without that AWS context often find the setup slower than either Resend or SendGrid.
Rate Limits, Sending Caps, and Scaling
Resend’s free tier enforces a hard 100 emails a day cap alongside the 3,000 emails a month allowance, which pushes any real production workload onto the Pro tier almost immediately. Once on a paid plan, there is no daily send limit beyond the monthly quota, and Resend recommends a dedicated IP, available from $30 a month, once daily volume crosses roughly 3,000 emails to protect deliverability.
SendGrid’s sending limits scale with plan tier and account reputation, but the more immediately relevant limit for engineering teams in 2026 is the Email Activity API change that took effect December 9, 2025. Any dashboard or monitoring tool that polls SendGrid’s activity data now has to work within 6 requests per minute, down from the previous 30 requests per five minutes, a change that broke some existing observability integrations and forced teams to batch their polling logic.
Amazon SES ties sending rate directly to account reputation and region-specific quotas rather than a flat plan limit. New accounts start in the SES sandbox, which restricts sending to verified addresses only until AWS approves a production access request, a step that has no equivalent friction on Resend or SendGrid. Once approved, sending rate and daily quota scale automatically based on sending history, which rewards consistent, low-complaint senders but adds an unpredictable ramp period that teams need to plan around before a launch date.
Real-World Use Cases
The theoretical comparison only goes so far. Here is how the pricing and API differences actually play out across five common scenarios engineering teams face in 2026.
- Next.js SaaS startup sending onboarding and password-reset emails. A two-person team building on Vercel with a Supabase backend typically wires Resend directly into a serverless function, using React Email components for every template. At under 10,000 emails a month, this costs nothing and takes under an hour to wire up end to end.
- Enterprise SaaS running both marketing campaigns and transactional receipts. A company sending 500,000-plus emails a month across newsletters, receipts, and lifecycle campaigns typically lands on SendGrid Pro or Premier, using subuser accounts to separate marketing sends from transactional traffic so a marketing complaint spike never threatens password-reset deliverability.
- AWS-native backend triggering invoices from Step Functions. A billing microservice already running on AWS Lambda that fires invoice emails from an EventBridge-triggered workflow almost always defaults to SES on the a la carte rate, since it is already inside the same IAM boundary and VPC as the rest of the billing stack.
- Reseller or white-label platform managing dozens of client sending identities. A platform offering white-label email on behalf of its own customers needs isolated reputation tracking per client, which is exactly what SendGrid’s subuser system was built for, making it a near-default choice regardless of raw cost per email.
- Cost-sensitive high-volume batch sender. A company sending several million transactional emails a month with tight margins, such as a logistics or fintech platform, often runs the numbers and lands on SES’s a la carte rate specifically because the 60% premium of the Essentials plan, or the multiples-higher cost of Resend or SendGrid at that scale, meaningfully affects the bottom line.
- Solo developer or indie hacker shipping a side project fast. A single founder wiring up a waitlist or launch email typically reaches for Resend first, since the free tier covers early traffic and the SDK integrates with a serverless deploy on Render, Railway, or Fly.io without any SMTP configuration at all.
Reliability and Uptime History
Uptime rarely makes headlines until it fails at the wrong moment. SendGrid’s status page history shows 32 major or critical incidents recorded since 2015, a number that reflects both the platform’s age and its scale rather than a specific reliability problem. Twilio’s status page through August and September 2026 mostly logs routine maintenance, including a planned deprecation of legacy IP ranges previously used to reach the SendGrid API and SMTP endpoints, with no widely reported catastrophic outage in that window.
Amazon SES inherits the reliability profile of the broader AWS region it runs in, tracked through the standard AWS Health Dashboard rather than a dedicated SES status page. Teams already monitoring AWS service health for other workloads get SES visibility for free as part of that existing process. Resend, as the youngest of the three platforms, has no widely reported major outage on record through September 2026, though it also has the shortest operating history and the smallest published incident data set of the three, so that track record carries less statistical weight than SendGrid’s decade-plus history.
Migration Guide: Moving Between Providers
Switching email providers is lower risk than most infrastructure migrations since email sending is usually isolated behind a single service or utility function, but domain reputation and DNS records need careful handling. Here is a practical path for moving from SendGrid or SES to Resend, which is the most common direction teams move in 2026 as they consolidate onto simpler tooling.
- Create a Resend account and add your sending domain before touching any DNS records tied to your current provider.
- Add the Resend-provided SPF and DKIM records to your DNS zone alongside your existing provider’s records. Both can coexist during the transition window.
- Wait for domain verification to complete in the Resend dashboard, typically within minutes but occasionally up to an hour depending on DNS propagation.
- Convert your highest-volume email templates to React Email components first, since these deliver the biggest maintenance win once migrated.
- Replace your SMTP or REST API calls with the Resend SDK in a single service or utility module, not scattered across the codebase, to keep the rollback path simple.
- Route a small percentage of production traffic, such as password resets for internal test accounts, through Resend first and monitor bounce and complaint rates for 48 to 72 hours.
- Migrate webhook handlers for delivery, bounce, and complaint events to Resend’s webhook format, checking that any downstream analytics or suppression-list logic still fires correctly.
- Gradually shift the remaining email categories over 1-2 weeks, watching deliverability metrics at each step rather than cutting over all traffic at once.
- Once fully migrated, remove the old provider’s DNS records and cancel the subscription only after confirming at least one full billing cycle of stable sending on the new platform.
The same sequence works in reverse for teams moving from Resend to SendGrid or SES, though moving toward SES adds an extra step: requesting production access to exit the SES sandbox, which should be submitted as early as possible in the migration timeline since AWS approval can take anywhere from a few hours to a couple of business days.
Pros and Cons of Each Platform
Weighing tradeoffs side by side makes the right choice clearer for most teams than pricing tables alone.
- Resend pros: Native React Email support, simple flat pricing, fast Vercel/Next.js integration, generous free tier for early-stage products.
- Resend cons: Smallest feature set of the three, no subuser system for multi-tenant sending, shortest operating track record, overage pricing gets expensive fast at high volume.
- SendGrid pros: Deepest feature set, subuser accounts for multi-tenant or white-label sending, over a decade of production hardening, strong marketing-plus-transactional combo tooling.
- SendGrid cons: Highest cost per email among the three at comparable feature levels, recent API rate-limit cuts hit some integrations, dated template authoring compared to component-based tools.
- Amazon SES pros: Cheapest raw sending cost by a wide margin on the a la carte rate, deep native AWS integration, scales to any volume without a sales call.
- Amazon SES cons: No built-in template editor or polished dashboard, sandbox approval friction for new accounts, July 2026 pricing changes closed the old free tier for new customers, steepest learning curve for teams outside the AWS ecosystem.
Which Email API Should You Choose?
The right answer depends almost entirely on team size, existing infrastructure, and sending volume rather than any single platform being universally better.
Choose Resend if you are building on Next.js or Vercel, want to write emails as React components, and are sending under 500,000 emails a month. The developer experience advantage outweighs the higher per-email cost at that scale, and the free tier removes any barrier to getting started.
Choose SendGrid if you need to manage multiple sending identities under one account, run both marketing and transactional email through the same platform, or need enterprise support and SLAs that come with the Premier tier. The cost premium buys operational maturity that smaller platforms have not built yet.
Choose Amazon SES if your backend already lives on AWS, you are comfortable configuring IAM policies and DNS records by hand, and you are sending high enough volume that the price gap between $0.10 and $0.35-plus per 1,000 emails actually shows up on a monthly invoice. Budget extra setup time for sandbox approval and expect to build your own dashboard and template tooling on top of the raw API.
The Verdict
None of the three platforms wins outright, and the data backs that up. At 100,000 emails a month, Amazon SES’s a la carte rate of $10 beats Resend’s $35 and SendGrid’s $34.95 by more than 3x, but that number ignores the engineering time SES requires to build the template, dashboard, and sandbox-approval tooling the other two ship out of the box. Resend wins on integration speed for anything built on React or Next.js, cutting a send-email workflow down to a single SDK call with no SMTP configuration. SendGrid wins on feature depth for any team managing multiple sending identities or blending marketing and transactional email in one platform.
For most new projects starting in late 2026, the practical default is to start on Resend’s free tier for speed, move to Amazon SES once volume and AWS infrastructure maturity justify the setup cost, and reach for SendGrid specifically when subuser management or enterprise support becomes a hard requirement rather than a nice-to-have.
Run the numbers on a mid-size SaaS product sending 200,000 emails a month, a common threshold where teams start reevaluating their original choice. On Resend Scale, that volume lands around $160 a month at the $0.80-per-1,000 overage band. On SendGrid, it falls between the Essentials and Pro tiers, likely pushing a team onto Pro at roughly $90-130 a month once the dedicated IP is factored in. On Amazon SES Essentials, the same 200,000 emails cost $32, and on the legacy a la carte rate, just $20. That gap, $140 a month between Resend and SES a la carte at identical volume, is exactly the threshold where engineering time spent building SES’s missing dashboard and template layer starts to pay for itself, particularly for a team that already has AWS expertise in house and does not need to hire for it.
Frequently Asked Questions
Which is cheaper, Resend or Amazon SES?
Amazon SES is cheaper on raw per-email cost, charging $0.10 per 1,000 emails on the legacy a la carte rate compared to Resend’s effective $0.35-0.40 per 1,000 on the Pro tier. SES requires more setup work and does not include a template editor or dashboard, which Resend bundles into its price.
Does Amazon SES still have a free tier in 2026?
Not for new accounts. As of July 21, 2026, AWS closed the historical 62,000 free emails a month allowance to new customers, and all new SES accounts start on the paid Essentials plan. Existing accounts that were active before that date may retain legacy access depending on their account history.
Can I use React Email templates with SendGrid or Amazon SES?
Not natively. Neither SendGrid nor SES ships built-in support for React Email the way Resend does. Teams can still render React Email components to HTML manually and pass the output through SendGrid’s or SES’s send API, but that requires building a custom render step that Resend provides out of the box.
What is the SendGrid Email Activity API rate limit in 2026?
Since December 9, 2025, the Email Activity API is limited to 6 requests per minute, down from the previous limit of 30 requests per five-minute window. This applies to querying activity and analytics data, not to sending emails, but it affects any dashboard or monitoring tool that polls SendGrid frequently.
Is Resend suitable for high-volume marketing email?
Resend can handle marketing sends and offers plans up to roughly 2.5 million emails a month, but it was designed primarily as a transactional and developer-focused email API. Teams running large marketing campaigns alongside transactional traffic often find SendGrid’s subuser system and dedicated marketing tooling a better fit at scale.
How do I migrate from SendGrid to Resend without breaking deliverability?
Add Resend’s SPF and DKIM records alongside your existing SendGrid records, verify the domain, then shift a small percentage of low-risk traffic first while monitoring bounce and complaint rates for 48 to 72 hours before migrating remaining email categories over one to two weeks.
Does Amazon SES support dedicated IPs?
Yes. SES offers standard dedicated IPs at $24.95 a month each, or a managed dedicated IP option at $15 a month plus $0.08 per 1,000 emails sent, which includes automated IP warm-up handled by AWS.
What happens if I exceed Resend’s free-tier limits?
Resend’s free tier caps out at 3,000 emails a month with a 100-emails-per-day limit. Sends beyond that cap fail until you upgrade to the Pro plan at $20 a month, which raises the allowance to 50,000 emails and removes the daily cap entirely.
