SendGrid Pricing 2026: Infrastructure Pricing, Two Products
Twilio SendGrid is deliverability infrastructure, not a lifecycle platform — and its pricing reads that way: an Email API product metered by send volume plus a separate Marketing Campaigns product metered by contacts. Verified September 2026: Email API trial covers 100 emails/day for 60 days (no longer a permanent free tier), Essentials starts at $19.95/month (50,000–100,000 emails), Pro starts at $89.95/month (100,000–2.5M emails, dedicated IP), and Premier is custom. Marketing Campaigns separately offers a free tier (2,000 contacts / 6,000 emails), Basic from $15, and Advanced from $60. Sources: sendgrid.com/pricing and Twilio's SendGrid pricing.
The short version
- Email API trial: 100 emails/day for 60 days — enough to integrate and load-test, not to operate.
- Essentials ($19.95/month): API + SMTP, analytics, template editor; overages from $0.0009–$0.0013 per extra email by band.
- Pro ($89.95+): dedicated IP included, subuser management, 5,000 validations, SSO options, phone support — the serious-sender tier.
- Premier (custom): 5M+ volumes with SLAs and dedicated support for enterprise infrastructure.
- Marketing Campaigns is a second bill (contacts + sends); most teams pair SendGrid API with a separate lifecycle tool instead.
How the billing model works
Two details dominate planning. First, the trial expires — teams that built on the old permanent free tier must now budget Essentials from month three. Second, volume bands price non-linearly: 100k emails cost $34.95 on Essentials but $89.95 buys Pro with a dedicated IP, so the IP upgrade decision and the volume decision collide at the same threshold.
Plan-tier ladder
- Trial100/day for 60 days. Integrate the API, validate event webhooks, prove inboxing. Calendar the trial end — sends stop, not degrade.
- Essentials $19.95Up to 50k–100k emails/month on shared IPs. Right for transactional and notification volume with basic analytics.
- Pro $89.95From 100k emails with dedicated IP, subusers, validations, and deliverability controls. Buy here when reputation isolation or team permissions matter.
- PremierMulti-million volumes, custom IPs and pools, SLA-backed support. Negotiate commits, overage rates, and incident response in the contract.
API vs Marketing Campaigns
| Dimension | Email API | Marketing Campaigns |
|---|---|---|
| Meter | Emails sent per month | Contacts stored + emails sent |
| Entry | Trial 100/day; paid $19.95+ | Free 2k contacts/6k emails; Basic $15+ |
| Strength | Deliverability infra, webhooks, scale | Editors, segmentation, automation basics |
| Gap | No journeys, billing triggers, attribution | Shallow lifecycle vs specialists |
Running both products means two meters, two consoles, and split reputation management. Most mature teams instead keep SendGrid (or a rival) purely as API infrastructure and run lifecycle elsewhere — or consolidate both onto one lifecycle platform.
Enterprise fit
SendGrid fits engineering-led transactional scale: password resets, receipts, notifications, and alerts at millions of sends with dedicated IPs, subuser governance, SSO, event webhooks, and Twilio-account consolidation. Deliverability tooling (validation API, reputation visibility, suppression management) is genuinely infrastructural.
It does not fit lifecycle marketing. There are no billing-event triggers, no dunning, no trial nurture playbooks, no upgrade attribution — Marketing Campaigns covers only basic automation. SaaS teams that adopted SendGrid for receipts and then bolted campaigns alongside it end up with the classic split-brain problem: two reputations, two analytics views, and no answer to which email drove the upgrade.
Migration checklist (consolidate or complement)
- Decide the architecture first: keep SendGrid as pure API infra with a lifecycle tool on top, or consolidate transactional plus marketing onto one platform.
- Inventory every sending identity: API keys, SMTP credentials, webhook consumers, suppression lists, and template versions across subusers.
- If consolidating, warm the new platform's IPs/domains with transactional traffic first — it is the most engaged mail you own.
- Rebuild event-webhook consumers (bounces, complaints, opens) against the new platform before cutover; dunning depends on failure signals.
- Retire subusers and keys in dependency order; keep SendGrid in paid standby for one billing cycle as rollback insurance.
API delivery or a broader lifecycle stack?
SendGrid is infrastructure pricing: volume bands, dedicated IPs and separate campaign products. Keep it when an engineering team owns delivery and event webhooks. If marketing needs billing triggers, dunning or upgrade attribution, compare a lifecycle platform separately rather than assuming the API plan includes it.
Fit check · before you model the bill
Who this guide is for
SendGrid is infrastructure pricing: volume bands, dedicated IPs, and a product split that assumes an engineering owner. Buying it well means knowing which of these three situations you are in before you read the ladder.
Engineering-led transactional senders
Product teams delivering password resets, receipts, and notifications at scale, with event webhooks, subuser governance, and dedicated IP reputation to manage.
Teams consolidating onto one Twilio account
Organizations standardizing voice, SMS, and email billing under one provider, where procurement simplicity matters as much as unit price.
SaaS teams auditing a split stack
Businesses running receipts in SendGrid and campaigns somewhere else — two bills, two reputations, and no answer to which email drove the upgrade.
If you are a marketer without an engineering owner, this is the wrong category: buy lifecycle tooling and treat delivery as somebody's infrastructure. The comparison section below prices the consolidation case.
Pricing geometry explained
The Email API product meters emails sent per month in volume bands; Marketing Campaigns meters contacts held plus emails sent as a separate product. Two meters, two consoles, two reputations — that split is the single most expensive thing about the platform, because it forces every team to decide where lifecycle ends and delivery begins.
Bands price non-linearly. Essentials covers 50,000–100,000 emails at $19.95; Pro starts at $89.95 for 100,000 up to 2.5 million and includes a dedicated IP. So at roughly the same threshold where volume justifies the Pro price, the dedicated-IP decision lands too — the two decisions collide and are usually budgeted separately, badly.
The trial compresses the timeline: 100 emails a day for 60 days is about 3,000 sends a month, enough to integrate and load-test and nowhere near enough to operate. Calendar the expiry, because sends stop rather than degrade, and month three needs a paid plan already approved.
| Meter | What triggers cost | Control lever |
|---|---|---|
| API send volume | Crossing a monthly volume band | Forecast twelve months; check overage rates |
| Overage | Sends past the band, roughly $0.0009–$0.0013 each | Right-size the band instead of riding overages |
| Marketing Campaigns contacts | Contacts stored plus emails sent | Keep campaigns out of the API bill entirely |
| Tier features | Dedicated IP, subusers, validations, SSO, phone support | Buy Pro only when the control is required |
Model both products separately and then together: many teams price the API well and discover the campaigns bill arriving through a different purchase order six months later.
What each tier actually includes
- Trial — 100 emails/day for 60 days: integrate the API, validate webhooks, prove inboxing. It expires; it does not degrade.
- Essentials — from $19.95/month: 50,000–100,000 emails on shared IPs, API and SMTP, analytics, and the template editor.
- Pro — from $89.95/month: 100,000–2.5 million emails, dedicated IP included, subuser management, 5,000 validations, SSO options, and phone support.
- Premier — custom: 5M+ volumes, custom IPs and pools, SLA-backed support. Negotiate commits, overage rates, and incident response in writing.
- Marketing Campaigns — separate: free at 2,000 contacts / 6,000 emails, Basic from $15, Advanced from $60 — a second meter, not an inclusion.
Read before you sign
Hidden fees & fine print
- The trial expires. 100 emails a day for 60 days, then sends stop — not a permanent free tier. Budget Essentials from month three with approval already in hand.
- Bands are non-linear cliffs. $19.95 covers 50k–100k emails while $89.95 covers 100k–2.5M; the jump is five times the price for up to twenty-five times the volume, which is favorable — but landing just over a boundary is where teams overpay.
- Overages run roughly $0.0009–$0.0013 per email by band. They are convenient for spikes and expensive as a habit; right-size the band after two months of riding over.
- The dedicated IP decision rides on Pro. Reputation isolation, warm-up discipline, and the subuser and SSO controls all arrive at $89.95 — confirm your team can operate a dedicated IP before paying for one.
- Marketing Campaigns is a second bill. Contacts and sends meter separately from the API, so running both means two budgets and split reputation management.
- Premier terms are negotiable. Commits, overage rates, support SLAs, and incident response belong in the contract, not in a sales call summary.
- Validation and support caps sit on tiers. The 5,000 validations and phone support are Pro features — check your cleanup tooling against them.
Cost scenarios
Verified figures only: trial 100/day for 60 days, Essentials $19.95 (50k–100k), Pro $89.95 (100k–2.5M), Premier custom, overages about $0.0009–$0.0013 per email, Marketing Campaigns free at 2,000 contacts / 6,000 emails with Basic from $15 and Advanced from $60.
| Scenario | API emails/month | Campaigns | Expected shape |
|---|---|---|---|
| Pre-launch integration | ≤3,000 (trial cap) | Not started | Free for 60 days, then budget Essentials |
| Early product, transactional only | 70,000 | None | Essentials at $19.95 |
| Growing product with reputation needs | 150,000 | None | Pro at $89.95, dedicated IP included |
| Transactional plus basic campaigns | 70,000 | 4,000 contacts | Essentials $19.95 + a second campaigns bill |
| Notification-scale platform | 5,000,000+ | None | Premier — negotiate commit and SLA |
Row four is the architecture question in one line: two products, two meters, one reputation split down the middle. Price the pair, not the API alone, before you sign anything.
Consolidate or complement: a decision frame
| Team shape | Recommended architecture | Watch |
|---|---|---|
| Engineering owns email; millions of API notifications | Keep SendGrid as pure infrastructure | Run lifecycle elsewhere; don't force it |
| Small SaaS, one product, marketers own lifecycle | Consolidate onto one lifecycle platform | Shared meter; budget transactional volume |
| Both, mid-transition | Complement short-term, plan the merge | Two reputations are a temporary state |
| Procurement wants one Twilio relationship | Stay on SendGrid for delivery | Still need lifecycle tooling with it |
Whatever you choose, decide the architecture before the migration checklist — every item later in this guide presumes you know whether you are keeping, complementing, or replacing the pipe.
Model your own bill before you commit
- Forecast twelve months of API volume with 20% headroom and check which band it lands in, including the boundary between Essentials and Pro.
- Price the dedicated-IP decision separately from volume: warm-up time and reputation ownership are operational costs, not line items.
- Add Marketing Campaigns as its own budget line if campaigns will run — contacts plus sends, not sends alone.
- Confirm trial expiry dates and who approves the month-three spend before the first send.
- Check validation caps, subuser needs, and support channel against your tier before signing.
- Compare the combined stack against consolidation on one platform, then decide on cost per outcome rather than cost per email.
Calendar the trial expiry now
100 emails a day for 60 days, then sends stop. Finish integration in week one, prove inboxing in week two, and have the paid decision made before week eight.
FAQs
Is SendGrid still free?
Only as a 60-day trial at 100 emails/day. The old permanent free tier is gone — budget Essentials ($19.95+) from month three. Marketing Campaigns retains a small free tier (2,000 contacts / 6,000 emails).
Essentials or Pro?
Buy Pro when you need a dedicated IP, subuser management, or deliverability controls — typically at or above ~100k emails/month. Below that, Essentials on shared IPs is the economical choice.
Should SaaS run lifecycle on SendGrid?
No. Use it as delivery infrastructure if you must, and run lifecycle — billing triggers, dunning, attribution — on a platform built for it.
What happens if I exceed my volume band?
Extra emails bill at roughly $0.0009–$0.0013 each depending on band. Fine for a one-off spike, expensive as a standing habit: after two months of riding overages, the next band up is usually cheaper — check the boundary math rather than absorbing the overage indefinitely.
Do we need a dedicated IP?
Only if you send enough volume to justify owning your reputation and can staff the warm-up. Dedicated IP arrives with Pro at $89.95, and it is a responsibility before it is a benefit: cold IPs warmed with low volume perform worse than a well-managed shared pool. Buy the tier for subuser and deliverability controls first, the IP second.
Are marketing campaigns included with the API plans?
No — Marketing Campaigns is a separate product with its own meters: free at 2,000 contacts and 6,000 emails, Basic from $15, Advanced from $60. Running both means two budgets, two consoles, and split reputation management, which is exactly why most mature teams keep SendGrid for delivery and run campaigns elsewhere.
SendGrid or Mailgun for API volume?
Both are developer-first volume ladders: Mailgun runs free 100 emails/day with Basic $15 (10k), Foundation $35 (50k), and Scale $90 (100k), while SendGrid's Essentials starts at $19.95 with Pro at $89.95. Compare at your projected volume — our Mailgun pricing guide lays out that ladder in full.