reddit · SaaS · 10-17 19:50 40 分 ← 返回列表

How much would you pay for an IdP that doesn't suck?

Ok - so "doesn't suck" is a bit of a loaded phrase. Apologies. But what I mean by that is: Doesn't gate developing support for security features (MFA, Passkeys, etc) behind paid plans. I don't mind them being on paid plans in prod. My complaint here is when you can't even build support for them before paying. Has standards-compliant OIDC support Has standards-compliant JWT / JWK support Has API support for everything Preferably a single unified API instead of multiple dif

五维评分

付费意愿

需求真实度

个人可落地

竞争空间

新鲜度

AI 分析

痛点：现有托管 IdP 将 MFA/Passkeys 等安全能力的开发支持锁在付费计划后，且 OIDC/JWT/JWK 不规范、API 不统一、配置复杂。

目标用户：需要给 SaaS 快速接入登录/认证的独立开发者和小型工程团队

证据："How much would you pay for an IdP that doesn't suck?" ... "none of them meet all of these" ... "Requires a non-standard parameter on all OIDC calls"

变现：按项目/MAU 订阅，开发环境免费开放 MFA/Passkeys 和标准 OIDC/JWT/JWK；生产环境按用量收费，提供统一 API 和托管部署。

MVP：两周内做一个基于 Ory/Keycloak 或开源库封装的托管 OIDC 服务：免费开发租户、标准发现文档、JWKS、MFA/Passkey 可开发测试、统一 REST API 和 3 个框架快速接入示例。

竞品：Auth0、Clerk、WorkOS、Supabase Auth、Firebase Auth、Keycloak、Ory、Stytch、Descope

摘要：发帖人详细列出托管 IdP 的不满：MFA/Passkeys 开发支持被付费墙挡住、OIDC/JWT/JWK 不合规、API 不统一、配置复杂，并询问愿意付多少钱。没有其他用户附和或真实付费数据，且认证基础设施竞争激烈、信任和安全门槛高，适合作为需求线索但验证不足。