Pantheon is a WebOps platform for WordPress and Drupal, backed by SoftBank (Series E, $100M in 2021). It has the most restrictive email posture of any major WordPress host: no email service, no reliable PHP mail(), SMTP ports discouraged due to dynamic outgoing IPs with no PTR records. Email on Pantheon requires a third-party provider configured via API (not SMTP).
Pantheon’s documentation explicitly states: outbound email from application containers uses dynamic IPs that change frequently and have no reverse DNS. Messages sent this way are routinely rejected or spam-filtered by receiving servers. The recommended integration is SendGrid’s REST API through an SMTP plugin.
Plans start at approximately $41/month (Basic). Traffic-based billing.
Email on Pantheon
The default: nothing works reliably
WordPress wp_mail() and PHP mail() will attempt to send through the container’s local MTA, but because the outgoing IP changes dynamically and has no PTR record, deliverability is near zero. Unlike Cloudways (where email also fails by default but the reason is port blocking), Pantheon’s issue is at the IP reputation level. Even with ports open, the dynamic IPs ensure that messages are rejected.
Required: API-based third-party integration
Pantheon recommends configuring an SMTP plugin with SendGrid’s REST API (they offer a partnership discount). The key point: use the API integration, not the SMTP integration. SMTP connections from Pantheon containers use the same dynamic IPs and have the same deliverability problems. API-based sending routes through the provider’s infrastructure, bypassing the container’s outgoing IP entirely.
Postmark, SMTP2GO, and Mailgun all support API-based WordPress integration.
What Pantheon does not provide
- Any email service. No relay, no mailboxes, no forwarding.
- Reliable SMTP port access. Ports 25, 465, 587 may be open but are unreliable due to dynamic IPs.
- Email hosting. Domain email requires a completely separate provider.