SendGrid retired its permanent free plan on May 27, 2025 (Twilio changelog). On the Email API pricing page, checked Nov 2, 2026, there is a 60-day free trial with 100 emails per day, no card, and the first paid plan, Essentials, starts at $19.95/month. A project that fit the old free plan now goes from $0 to about $20 a month at least.
Free plans that do not expire (checked Nov 2, 2026, from each official pricing page)
| Pidgely Free | Resend Free | SendGrid | |
|---|---|---|---|
| Permanent free plan | Yes | Yes | No (60-day trial) |
| Free volume | 6,000 emails/month | 3,000 emails/month | 100 emails/day in the trial |
| Daily cap | 200/day | 100/day | 100/day |
| Domains | 3 | 3 | see their docs |
| Card at sign-up | No | No | No (trial) |
Disclosure: I work on Pidgely. Paid plans at the same volume are not exactly comparable, so check features and limits before you decide.
Does the daily cap get in the way?
200 a day adds up to 6,000 in 30 days, which is enough for transactional email that spreads over the month. A burst of 1,000 emails at once (a notice to your whole list) would take five days on the free plan. Before migrating, look at your busiest sending day in the last 30 days and compare it with the daily cap.
Migrating over SMTP
If your app uses SMTP, you change host, user and password and keep your sending code:
- Create the account and verify your sending domain (publish the SPF and DKIM records).
- Keep DMARC published and aligned.
- Change the SMTP credentials: host
smtp.pidgely.com, userpidgely, password = the API key. - Send a real test to your own mailbox and check "Show original" for SPF, DKIM and DMARC pass.
- Move traffic gradually if you had a lot of volume, and remove the old credentials only after delivery is confirmed.
When to stay on SendGrid
Very high volumes with a long track record, an existing Twilio contract for SMS or voice, or a Twilio-only feature you rely on.
Full version with the FAQ and sources: Left SendGrid's free plan? Free alternatives. Feature comparison: Pidgely vs SendGrid.
Top comments (1)
The advice to compare your busiest sending day against the 200 a day cap is the right test. One thing I would add is to check what happens to message 201. If the SMTP server rejects it with a temporary error, your app's retry logic decides whether a password reset arrives late or never, and many apps only log that failure.
On the Pidgely free plan, does a send over the cap get queued for the next day or rejected at SMTP time?