compare
Plunk vs useSend
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Plunk | useSend |
|---|---|---|
| Language | TypeScript | TypeScript |
| Licence | AGPL-3.0 | AGPL-3.0 |
| Stars | 5.5k | 4.7k |
| Latest | v0.15.0 | v1.9.8 |
| Last push | 2026-10-06 | 2026-09-08 |
| Release cadence | about 37 days between releases | about 21 days between releases |
| Active contributors | 12 commit authors on the default branch in the last 90 days | 5 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace SendGrid. Alternatives to SendGrid →
PartialPlunkTransactional email over an HTTP API next to campaigns and automations, sent through Amazon SES.
Full replacementuseSendTransactional and marketing email over a REST API and SMTP, with webhooks and delivery stats, sent through Amazon SES.
Plunk
- v0.15.02026-09-20Add ability to snooze contacts instead of unsubscribing (787d200)
- v0.14.02026-08-17Add additional card verification in worker (33cc815)
- v0.13.02026-08-09add email body cleanup job to remove old email content after 90 days (cef8ce0)
- v0.12.02026-06-22add composite index on campaignId and status for efficient campaign completion checks (4b752a5), closes #400
- v0.11.02026-05-13Ability to change subscription status in workflows (fadc19d)
useSend
- v1.9.82026-08-30fix: prevent variable popover from blocking text selection
- v1.9.72026-08-23fix: preserve safe headers through SMTP proxy
- v1.9.62026-07-23fix: reject invalid SES regions
- v1.9.52026-07-12Campaign previews are now isolated from the dashboard, so email styles can’t break or change the surrounding UI
- v1.9.42026-05-18chore: add Entire agent config
Plunk
✓ signed The latest release, v0.15.0, carries a signature GitHub verified.
Loading the security report
useSend
✓ signed The latest release, v1.9.8, carries a signature GitHub verified.
Loading the security report