IdeaSift

Self-hosters struggle to centralize login across apps

People running self-hosted services want to use a central identity provider instead of managing separate logins, but some apps lack OIDC, LDAP, or a trusted identity-header option. A gateway can protect an app from outside, but it may not provide the per-user identity or granular controls an app needs internally. The requests span media and other self-hosted services, suggesting a recurring integration gap rather than one app-specific issue.

For self-hosters running multiple services. Mentioned from Sep 2021 to Jun 2026 on GitHub.

4 different people described this problem in 3 separate discussions.

Week of 2026-07-13: 0Week of 2026-07-20: 0Week of 2026-07-27: 0Week of 2026-08-03: 0Week of 2026-08-10: 0Week of 2026-08-17: 0Week of 2026-08-24: 0Week of 2026-08-31: 0Week of 2026-09-07: 0Week of 2026-09-14: 0Week of 2026-09-21: 0Week of 2026-09-28: 0
0 mentions in the last 12 weeks
Indie fit
4.0/10
Pain
5.5/10
Frequency
5.8/10
Willingness to pay
0.0/10
Momentum
5.0/10
Who pays
Consumers
Competition
High
Build difficulty
High

What people said

Quoted word for word. Follow a link to read the whole discussion.

  1. I use Authentik and would love to more easily and granularly secure my *rr stack
  2. Add LDAP Support > +1 for LDAP support as well, but if SSO solutions like Keycloak (which can sync with ldap) are supported, those are preferable to plain LDAP for me. I second this. LDAP and/or SSO support will be great. Don't hesitate to reach out if any beta testing is needed !
Build brief

See what to build and who will buy it

  • 1 product idea with the smallest useful version and pricing
  • 3 places to find your first customers
  • 2 more quotes from people who have this problem
  • Current workarounds, existing solutions and risks