Automated OAuth credential lifecycle manager for self-hosted WordPress plugins that silently re-authenticates before expiry without requiring user action
Every WP Mail SMTP user hits this cliff at 6 months and most lose email delivery silently, making this a near-universal churn and support cost problem with a clear mechanical fix
Built for WordPress admins using Gmail OAuth for mail.
WordPress site owners are non-technical and cannot navigate OAuth re-auth flows every 6 months, creating a recurring support nightmare that plugin makers ignore because it hits post-install
“Replies: 2 Received emails for all my wp mail smtp users – that they haven’t logged in and the data will be deleted. So what’s going on. Should we delete the ac…”
The receipts — real demand
“Replies: 2 Received emails for all my wp mail smtp users – that they haven’t logged in and the data will be deleted. So what’s going on. Should we delete the access and recreate it every 6 months – as currently the plugin does not seem to do any logins – but they are needed every 6 months at least. Email Text: Hello Google Developer, In accordance with OAuth 2.0 Policies, the following projects that you manage have O…”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
demand score 7.2 — the receipts are below
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
WordPress admins using Gmail OAuth for mail delivery (WP Mail SMTP, similar plugins). Demand appears niche and episodic—pain surfaces when Google enforces token expiry, not proactively. No search volume signal suggests low discoverability.
Competition & the opening
OAuth token refresh is already handled by Google OAuth 2.0 libraries, Auth0, Nylas Email API, and Zapier/Make. The gap: none of these are WordPress-specific or bundled into mail SMTP plugins themselves. Nylas and Zapier abstract it entirely, but cost and complexity lock out small admins. A crowded OAuth space (8/10) means incumbents own the standard.
What's hard to build
Integration with Google's OAuth 2.0 refresh flow is well-documented but requires server-side credential storage, secure token rotation, and handling of revoked/expired credentials per site. Plugin architecture must handle async refresh without blocking email delivery. Test coverage across Gmail API versions and WP Mail SMTP variants adds surface area.
Why now
Gmail OAuth token expiry forces manual re-auth every 6 months; incumbents (Auth0, Nylas) are enterprise-priced, leaving SMB WordPress users stranded.
How you'd monetize
freemium WordPress plugin ($0 base, $99/year for token auto-refresh + support)