GoSend keeps the pricing tied to what developers care about: plan-based sending volume, sending domains, delivery visibility, sender routing, and webhooks.
For trying GoSend or shipping a small side project.
For production SaaS apps that need reliable transactional email.
For growing products with multiple domains and higher sending volume.
| Feature | Free | Pro | Business |
|---|---|---|---|
| Email quota | 100 / day | 10,000 / month | 100,000 / month |
| Sending domains | 1 | 20 | Unlimited |
| API access | Included | Included | Included |
| Email logs | Included | Included | Included |
| Webhooks | - | Included | Included |
| Priority support | - | - | Included |
V1 focuses on transactional email only: verification codes, password resets, support notifications, audit alerts, and system messages. Marketing campaigns and newsletters are intentionally outside the plan.
Each recipient in a send request counts as one email. Delivery, bounce, and complaint events do not count as additional emails.
Yes. You can use GoSend-managed DNS verification, or bind a domain to your own sender account and let that provider decide whether the sender is allowed.
No. GoSend exposes a JSON API for transactional email, so your backend can send mail without SMTP credentials or mail server setup.
The API rejects new send requests once quota is exhausted. You can upgrade plans from billing when your product grows.