Customer Identity across clouds
Sign-in for your customers rather than your staff - Cognito, Azure AD B2C, Identity Platform - with the social providers, MFA, sign-up throttling and the redirect allow-list set before the first user arrives.
6 verified modules, 1 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| AWS | Cognito User Pool & App Client | ✓ live-tested |
| Azure | A B2C Tenant Where Its Customer Directory Should Live, on the Tier the Features Need | static-validated |
| Google Cloud | Customer Sign-In with Anonymous Accounts Off, MFA Offered and Sign-Ups Throttled | static-validated |
| IBM Cloud | Customer Sign-In Where the Bill and the Open Door Are Both Decisions | static-validated |
| Oracle Cloud | A Customer Directory Whose Licence Change Would Delete Every Account | static-validated |
| Tencent Cloud | A Customer User Store That Admits It Does Not Configure Sign-In | static-validated |
How to choose
Compare pricing per monthly active user and where the free tier ends, which federated providers and MFA methods are built in, whether the user store can live in a chosen region, whether one deployment can serve several customer bases (tenants), and how much of the sign-in UI is hosted for you.
When not to use
A customer directory is the most valuable table you have and the one exposed to the internet by design. Anonymous sign-in, unlimited sign-up and a redirect list with localhost in it are each on by default somewhere; the module turns them off, and the client code has to not turn them back on.