WordPress verdict · build Pain point

Self-hosted Gmail OAuth redirect handler plugin

Built for Security-conscious WordPress developers who want direct Gmail OAuth integration without third-party intermediaries..

“Replies: 0 please could you explain why the gmail oauth setup parameter: ‘smtp authorised redirect uri’ is set to https://connect.wpmailsmtp.com/google/ rather …”

The receipts — real demand

“Replies: 0 please could you explain why the gmail oauth setup parameter: ‘smtp authorised redirect uri’ is set to https://connect.wpmailsmtp.com/google/ rather than a local uri? (as per video & screen shots etc). i don’t see the need to have a 3rd party server between my site & gmail & i don’t like the security & performance ramifications either. just seems cynical. other similar plugins don’t do this. whats your exp…”
WordPress · view original →

Full dossier

Unlock the full dossier — free

Every corroborating quote, the source receipts, and the community echo. One email, no payment.

6.3 / 10 · demand score
Pain 7
Willingness to pay 5
Specificity 8
Audience 7
Competition 2

Why this is a gap

Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.

The market

Security-conscious WordPress developers want direct Gmail OAuth without third-party redirect handlers. The pain signal (a direct question about why OAuth redirects to a third-party) suggests a small but vocal segment of developers with strong privacy concerns, not a mass-market demand.

Competition & the opening

Open field · 2/10

WP Mail SMTP and similar plugins use third-party redirect handlers for simplicity. No direct competitors offer self-hosted OAuth handlers. The gap is technical and specific: local OAuth redirect handling without vendor intermediaries.

What's hard to build

Gmail's OAuth rules require HTTPS and registered redirect URIs, which means users need control over their domain's SSL and DNS. Supporting multiple WordPress installations, each with different domains, complicates architecture. Google's OAuth policies change frequently and can break self-hosted implementations without warning.

Why now

Self-hosted workflows increasingly common; OAuth redirect interception now feasible via local cert pinning.

How you'd monetize

$29-79/mo SaaS or one-time $199 self-hosted license