The Best: 100 emails a day free forever, three settings to configure
The Worst: Support 3.7, and seven reviews describe being cut off with no notice
SendGrid is the easiest relay in this category to start using and the hardest to feel safe on. Setup is three lines: point your client at smtp.sendgrid.net on port 587, set the username to the literal string apikey, and put your API key in the password field. A hundred emails a day are free forever. Nothing else here is that frictionless.
The risk is on the other side of the account. Across the 200 reviews we read, seven describe being cut off without warning, and they are not all angry newcomers. One is a seven-year customer, one had spent thousands of dollars a month for five years, and two of the seven rated SendGrid three or four stars anyway. The recurring detail is not the suspension itself but the silence around it: “When they ban your account, there is no notification”, “Compliance team does not speak with me, I could not determine what I had done wrong”, “account closed due to inactivity and without any email or notification”.
Twilio’s own terms promise otherwise. Section 2.3 says Twilio may suspend “upon written notice to you”. We are recording a gap between a published term and seven independent accounts, not resolving it.
The third thing to weigh is the neighbourhood. SendGrid’s shared sending infrastructure carries a documented abuse load. In 2020 Krebs on Security reported a wave of compromised SendGrid accounts pumping phishing and malware, with the head of a blocklist operator saying of SendGrid’s spam volume: “As far as the nasty criminal phishes and viruses, I think there’s not even a close second.” In 2024 Netcraft documented phishing campaigns run from compromised SendGrid accounts that impersonated SendGrid itself, using SendGrid’s own click-tracking links for cover. If you send on shared IPs, this is your street.
Perfect for a side project, a prototype, or anything where a sending outage is an inconvenience. For production email your business depends on, buy the dedicated IP, keep a second provider configured, and know that the compliance function is the part people cannot reach.
SendGrid is the first of nine dedicated sending providers on this site, and the six categories we score need a word of explanation before the numbers land.
Automation here scores what the product does with campaigns, journeys and behavioural triggers. A transactional relay is not trying to do those things, and SendGrid’s Marketing Campaigns is a separate product with its own listing. So a low automation score on this page is a description of what SendGrid is, not an accusation. Postmark carries the same shape and still ranks near the top of our scale, because the categories that matter for a relay, deliverability and API, are where it earns its points.
Deliverability is where the difficulty sits. The independent seedlist panel we quote elsewhere on this site tested marketing platforms and never included SendGrid, so there is no percentage to publish, and the panel has since stopped running the test at all. What exists instead is documented third-party reporting on the state of SendGrid’s shared infrastructure, and the corpus. We use both and we say which is which.
| Hostname | smtp.sendgrid.net |
|---|---|
| Ports, unencrypted or TLS | 25, 2525, 587 |
| Port, SSL | 465 |
| Recommended | 587. SendGrid: “If you are unsure which port to use, a TLS connection on port 587 is typically recommended.” |
| Username | The literal string apikey. Not your email address, not your account name. |
| Password | The API key you generated |
| Do not use IPs | SendGrid: “SendGrid recommends setting your server host to smtp.sendgrid.net, and not directly pointing to SendGrid IP addresses.” |
| API send endpoint | POST https://api.sendgrid.com/v3/mail/send |
| EU region | api.eu.sendgrid.com, described as “for EU regional subusers” |
| Max message size | 30 MB total, attachments included |
| Recipients per request | 1,000 |
We read SendGrid’s SMTP integration documentation, then read it a second time asking only for literal text, and published nothing that did not appear in both passes. We adopted this rule after catching an automated summariser inventing a plausible table of hostnames and ports for a different platform on this site. One term we will not use: SendGrid’s documentation never writes “STARTTLS”. It distinguishes a “TLS connection” on 25, 2525 and 587 from an “SSL connection” on 465, which describes STARTTLS behaviour without naming it.
| Founded | 2009, by Isaac Saldana, Jose Lopez and Tim Jenkins. A Techstars company, and the first IPO to come out of an accelerator. |
|---|---|
| Ownership | Twilio. IPO on the NYSE 16 November 2017; Twilio’s acquisition announced October 2018 at around $2 billion in stock and closed 1 February 2019. |
| Product lines | Two: Email API and Marketing Campaigns. This review covers the Email API. |
| Free tier | “Once you create a sender identity, you can send 100 emails per day on our free SMTP plan.” Separately, a 60-day trial covers 100 contacts and 100 emails a day. |
| Essentials | “starting at $19.95/mo”, tiers at 50,000 and 100,000 emails a month |
| Pro | “starting at $89.95/mo”, tiers at 100,000 through 2,500,000 emails a month |
| Premier | Custom pricing, 5,000,000 and above |
| Overage | Per-email, billed the following period: “If you send more emails than your email plan allows within a given billing period, you will be charged a small overage fee on a per-email basis.” |
| Dedicated IP | One included on Pro. “You can purchase additional IPs as an add-on”, but the price of an additional IP is not published anywhere on twilio.com. |
| API auth | Bearer token in the Authorization header |
| Published rate limits | None. SendGrid publishes response headers and a 429, not numbers: “Each Web API response includes rate-limit headers that indicate how many requests remain in the current refresh period.” |
| Official MCP | No. See the section below; what exists is a Twilio Labs alpha that indexes SendGrid documentation, not an execution server. |
| Independent inbox placement | No figure. SendGrid was never in the seedlist panel, which has since been discontinued. |
Three settings and you are sending. Host, port 587, username apikey, password is the key. There is no domain warm-up gate, no sales call, no sandbox to escape. Compare that with Amazon SES, where new accounts start in a sandbox that can only send to verified addresses until a support request is approved, and the difference on day one is enormous.
The corpus reflects it. The dominant positive across 200 rows is how quickly it worked: “Quite easy to setup, integration with firebase was easy enough”, “easy-to-integrate sdk for developers like me using several languages like nodeJS and python”, “the integration process with our product was fairly straight forward and on-going maintenance is low cost”.
A hundred emails a day, permanently, on the free SMTP plan. That is 3,000 a month at no cost with no expiry, which covers a genuine long tail of small applications: password resets for a side project, order confirmations for a shop doing a few sales a day, alerts from a home server. Several competitors in this family offer a larger monthly allowance but tie it to a trial window or a card.
SendGrid documents api.eu.sendgrid.com alongside the global endpoint, described as being for EU regional subusers. For teams with a data residency requirement, having this stated in the API documentation rather than negotiated in a contract is a real advantage, and several providers in this family do not offer it at all.
The limits that matter are written down plainly: 30 MB for the whole message including attachments, 1,000 recipients per request, 1,000 personalizations, a 10,000-byte ceiling on custom arguments. Gzip compression of the payload is available to high-volume accounts on request. This is more operational detail than most of this category publishes, and it is the reason SendGrid remains the default integration in so many frameworks.
This is the finding, and the reason to read the rest of this page carefully. Seven of the 200 rows we read describe an account cut off with no advance warning and no usable explanation. They span 2020 to 2025 and they are not concentrated among short-term users.
The most circumstantial is a seven-year customer relaying what support told him: “The platform, per the conversation with the customer support team, has seen a large rise in fraud and has begun banning clients regularly even when compliance hasn’t completed a diligence process. This has resulted in a large amount of ‘false positive’ cases. When they ban your account, there is no notification.”
A five-year customer: “After years of spending thousands of dollars a month we are suddenly and without warning, ‘temporarily’ blocked from sending emails while the routinely check for spam activity.”
A four-star reviewer, which is what makes this cluster hard to dismiss: “It was easy to set up, and worked perfectly until it didn’t; then, customer support was non-existent. Customer support does not answer emails. Compliance team does not speak with me, I could not determine what I had done wrong. They simply left me in the lurch, and held my email hostage.”
And the rejection language one reviewer received verbatim: “We have reviewed your account and have determined that Twilio’s services cannot support the content and/or nature of your business.”
SendGrid publishes four account states. Warned: “The account maintains full sending functionality during a warning period.” Suspended: “SendGrid accepts and queues mail while the account is under review. The account holds mail until issues are resolved or up to 72 hours from the time of send.” Deactivated: “A deactivated SendGrid account cannot accept mail. Upon deactivation, SendGrid deletes any undelivered mail queued on the system.” Banned: “Banned accounts cannot access our system either through SendGrid.com or the API.” Twilio’s terms, section 2.3, say Twilio may suspend “upon written notice to you”. Seven reviewers say the notice did not arrive. We publish both and draw no conclusion about which is typical.
This one surprised us and we checked it twice. Twilio’s Acceptable Use Policy governs SendGrid, and it contains no clause explicitly prohibiting unsolicited bulk email. Twilio does publish a Messaging Policy that prohibits “Sending any unsolicited or unwanted messages in bulk” and requires prior consent, but that policy covers SMS, MMS, RCS, Conversations and WhatsApp Business. It does not cover email.
So the rule you can be banned for breaking is not written down in a form specific to what you are doing. The AUP does say “The prohibited conduct in this AUP is not exhaustive”, which is the clause that makes the previous section possible. For a compliance-minded buyer this is the most important paragraph on the page: you cannot read the policy and know you are safe, because for email there is not one to read.
Two independent security organisations have published on SendGrid’s abuse problem, and both reports are specific.
Krebs on Security, August 2020, on a wave of compromised SendGrid accounts sending phishing and malware. The chief executive of the blocklist operator Invaluement, asked how SendGrid’s spam volume compared with competitors: “As far as the nasty criminal phishes and viruses, I think there’s not even a close second.” The same report describes a criminal vendor offering more than 400 compromised SendGrid accounts, priced from $15 to $400 according to the sending volume of the account. Twilio’s chief security officer responded that “Twilio believes that requiring 2FA for customer accounts is the right thing to do, and we’re working towards that end”, at a point when Twilio had owned the two-factor company Authy for five years. An anti-abuse advocate called single-factor authentication in 2020 “just ludicrous given the potential damage.”
Netcraft, February 2024, on a campaign observed the previous December: at least nine companies had their SendGrid accounts compromised and used to send phishing that impersonated SendGrid, with the malicious link hidden behind a tracking link hosted by SendGrid. The pretext the phishing emails used is the detail worth pausing on. They claimed the victim’s account had been “suspended while its sending practices are reviewed”. The suspension experience described in the section above is now familiar enough to work as bait.
Inside the corpus, 35 of 200 rows raise deliverability, spam placement or reputation. On a dedicated IP most of this is your problem to manage rather than your neighbours’. On the shared pool it is not.
Capterra puts SendGrid’s customer service at 3.7, level with GoHighLevel for the lowest on this site and well under the 4.2 to 4.8 band the rest of the category occupies. 42 of 200 rows raise support, and the complaint that recurs is not slowness but absence at the decisive moment. “SLOW support”, “Customer support didn’t even read what I wrote and just copy&pasted a response”, “customer support was non-existent”.
The structural version of the problem is that compliance and support are different functions, and the reviewers who most need to reach compliance report that they cannot.
SendGrid’s rate limit documentation gives you a mechanism instead of a number: “Each Web API response includes rate-limit headers that indicate how many requests remain in the current refresh period”, and a 429 when you exceed it. The example values on that page are illustrative rather than binding, which we mention because they are easy to mistake for limits.
Compare with what a competitor will tell you before you build. GoHighLevel publishes 100 requests per 10 seconds and 200,000 a day. Drip publishes 50 batch and 3,600 individual requests an hour. HubSpot publishes limits per tier. SendGrid asks you to discover yours at runtime.
There is no first-party SendGrid MCP server. What exists is easy to mistake for one. Twilio Labs publishes an alpha monorepo that generates MCP tools from Twilio’s OpenAPI specifications; it is branded Twilio Alpha, lives under a labs organisation, and does not mention SendGrid. A separate Twilio Alpha MCP server indexes documentation across Twilio products plus SendGrid documentation, which means it can answer questions about SendGrid but cannot send anything. Twilio’s blog carries a tutorial on building your own, filed under community.
Working community servers do exist. None of them is supported by Twilio. Against Drip, which ships a free official connector, or GoHighLevel, which publishes an Anthropic-specific endpoint, this is a real gap for a product this widely deployed.
Two figures are missing from a page that otherwise reads as transparent. The per-email overage rates are printed, but which rate attaches to which tier is not stated in a form we could confirm twice. And the price of an additional dedicated IP is not published at all, despite the pricing page inviting you to buy one. A figure of around $30 circulates widely; it is not on twilio.com, and the $30 that is on the pricing page buys email testing credits, not an IP.
We read 200 rendered review rows across eight pages of SendGrid’s Capterra listing (product ID 204113), out of 753 total, so roughly a 27 percent sample. Two of the eight pages returned condensed rather than full verbatim text; we used those for theme counting and quoted only from pages that returned complete text. Frequencies are stated as “named in at least N of the 200 rows”. Capterra identifier 126780, which appears in some sources, returns a 404; only 204113 is live.
A heavy tail for a product people mostly like. Of the 200 rows, 16 are one star and 7 are two star, so 23 rows, 11 percent, sit at the bottom. That is the second heaviest tail we have measured after GoHighLevel. At the same time 111 rows are five star. SendGrid does not produce mild dissatisfaction; it produces delight or exit.
Easy to start, hard to stay, said in one sentence. The most representative line in the whole corpus is a four-star review: “It was easy to set up, and worked perfectly until it didn’t.” That is the arc almost every negative review describes, and it is why the setup praise and the abandonment complaints are not contradictory.
The billing transition catches people. One row reports the free-to-paid change costing real work: “When they went from free to paid, didn’t tell me, and i lost multiple weeks worth of email / jobs.” Combined with per-email overages billed a period in arrears, the cost surface here is less predictable than the headline price suggests.
Six categories, each out of 10, judged against the same evidence rules on every platform we cover. The overall is the unweighted arithmetic mean, rounded to one decimal: 6.5 + 4.5 + 5.0 + 3.5 + 6.5 + 8.0 = 34.0, divided by 6, equals 5.7.
Ease of use, 6.5. The SMTP integration is the simplest in this category and the account surface is not. A Capterra ease score of 4.1, and 16 rows describing difficulty, almost all of it in subusers, authentication and compliance rather than in sending.
Automation, 4.5. Not a criticism so much as a definition. This is an email API; campaigns live in a separate product. Postmark scores 4.0 here for the same reason and still ranks near the top of our scale.
Deliverability, 5.0. Good tools, difficult neighbourhood. Dedicated IPs, authentication and validation are all available, and two independent security organisations have documented sustained abuse of the shared infrastructure. No seedlist figure exists. 35 rows raise placement.
Support, 3.5. The lowest score we have given on this site. A 3.7 customer service sub-score, 42 rows, and a documented pattern of the compliance function being unreachable at exactly the moment an account stops sending.
Pricing value, 6.5. A genuinely free permanent tier and a cheap entry plan, against 25 percent of the corpus complaining about cost, per-email overages billed in arrears, and two prices that are not published.
API and MCP, 8.0. An excellent, ubiquitous, well-documented API with a published EU region and clear operational limits. Held down by rate limits that are not published as numbers and the absence of any official MCP server.
| Source | Score | Volume | Notes |
|---|---|---|---|
| G2 | 4.0 / 5 | 368 reviews | Listing: Twilio SendGrid Email API. A separate listing exists for Marketing Campaigns; do not merge them. |
| Capterra | 4.2 / 5 | 753 reviews | Ease of use 4.1, customer service 3.7, features 4.1, value for money 4.0. Product ID 204113. |
| Trustpilot | N/A | – | No verified listing found. |
| Inbox placement | No figure | – | Never included in the seedlist panel, which has since been discontinued. |
The 3.7 customer service sub-score is the number to carry away from this table. Across the platforms we have measured, this figure clusters tightly between 4.2 and 4.8, and only three fall below 4.0: Mailjet at 3.9, GoHighLevel at 3.7, and SendGrid at 3.7. It is also the sub-score most likely to matter to you, because on a relay the day you need support is the day your application stopped working.
Note also that G2 and Capterra disagree by 0.2 points in the unusual direction, with the developer-heavy G2 audience rating it lower than the general Capterra population.
| Alternative | Our score | Take it instead if |
|---|---|---|
| Postmark | 7.1 | Transactional email your business depends on. It separates transactional and broadcast streams by design, and its deliverability and support are the reasons it scores where it does. It costs more and it is meant to. |
| Brevo | 7.7 | You want a relay and marketing email in one account. The only platform in our marketing set that publishes an SMTP relay on an entry plan, and it bills on sends rather than contacts. |
| Amazon SES | See our review | Cost at volume is the binding constraint and you already run on AWS. Cheaper per thousand than anything here, at the price of a sandbox to escape and no interface worth the name. |
Host smtp.sendgrid.net. Port 587 for a TLS connection, which SendGrid recommends, or 25 or 2525 as alternatives, or 465 for SSL. Set the username to the literal string apikey, not to your email address, and set the password to the API key you generated. SendGrid explicitly advises against pointing at its IP addresses directly rather than the hostname.
The free SMTP plan sends 100 emails a day permanently once you create a sender identity, and a separate 60-day trial covers 100 contacts and 100 emails a day. Essentials starts at $19.95 a month with tiers at 50,000 and 100,000 emails, Pro starts at $89.95 a month with tiers up to 2,500,000, and Premier is custom above 5,000,000. Overages are charged per email and appear on the following period’s invoice.
Yes, within limits, and permanently rather than for a trial period. The free SMTP plan allows 100 emails a day, which is 3,000 a month. That is enough for a small application’s password resets and order confirmations. Note that one reviewer reports being moved from free to paid without notification, so watch the account state if you are relying on the free tier.
Yes, and it is the reason most people choose it. Send with POST to https://api.sendgrid.com/v3/mail/send using a Bearer token, or use the EU regional host api.eu.sendgrid.com for EU subusers. Messages are capped at 30 MB including attachments and 1,000 recipients per request. SendGrid does not publish numeric rate limits: it returns rate-limit headers on every response and a 429 when you exceed the limit.
The same product under its current ownership. SendGrid was founded in 2009, went public on the NYSE in November 2017, and Twilio announced its acquisition in October 2018 for around $2 billion in stock, closing on 1 February 2019. It is now a Twilio product line with two halves, Email API and Marketing Campaigns, and its documentation and billing live on twilio.com.
They are close competitors with the same shape and the comparison usually comes down to two things: SendGrid has the wider integration footprint and the more generous permanent free tier, while Mailgun has historically been the more developer-focused of the two on routing and inbound. Both are reviewed on this site with the same six categories, so compare the ratings rather than the marketing.
Postmark at 7.1 if transactional email matters enough to pay more for support and deliverability, Brevo at 7.7 if you want a relay and marketing email in one account, and Amazon SES if cost at volume is the binding constraint and you can live with the sandbox and the missing interface. All are reviewed on this site.
SendGrid publishes four states, warned, suspended, deactivated and banned, and reviews accounts it describes as showing abnormal activity. What it does not publish is a policy specific to email: Twilio’s Acceptable Use Policy has no explicit unsolicited-bulk-email clause, and the Messaging Policy that does prohibit unsolicited bulk covers SMS and chat, not email. Seven of the 200 reviews we read describe suspension without advance notice, and Twilio’s terms say suspension follows written notice. Keep a second relay configured.
| Date | Change |
|---|---|
| 27 August 2026 | First publication. 200 Capterra rows read across 8 pages of a 753-review listing. Every SMTP hostname, port, username convention, size limit and price verified twice against SendGrid’s own documentation on this date, with unconfirmed values omitted rather than estimated. Suspension states quoted from SendGrid’s account review documentation and from Twilio’s terms. Abuse reporting sourced to Krebs on Security (August 2020) and Netcraft (February 2024). Search volumes measured for the United States. |
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.