Authing
Authing is a managed identity platform that can provide registration, login, account recovery, and token/session management out of the box.
When to choose Authing
- You want a managed solution with fast time-to-launch
- You want common auth features (password reset, OTP, MFA options) without building them yourself
- You want to reduce security maintenance burden for early-stage or lean teams
Pros
- Low implementation overhead compared to building auth yourself
- Common auth flows included (registration, login, recovery, sessions/tokens)
- Admin tooling typically available for user management and troubleshooting
Cons / gotchas
- Vendor dependency: your login UX and token model may be coupled to the platform
- Account linking: if you also support WeChat / Apple / Google login, you still need a clear linking strategy to avoid duplicate accounts
- Still requires your own stable user ID: do not use provider subject/email/phone as your primary key; map to your own internal
userId
Implementation notes
- Maintain a stable internal
userIdin your database. - After Authing authentication succeeds, map the Authing identity to your internal
userId. - Use the internal
userIdas the canonical identifier for account-bound data, entitlements, and cross-service integrations.
Official documentation
- Authing docs (English) (some pages may only be available in Chinese)
- If a page isn’t available in English, browser auto-translate (e.g., Chrome Translate) usually works well. If anything looks unclear after auto-translation, reach out to our team for help.
- Authing pricing
- Authing site