Track the accounts outside your identity provider, the authenticators on each one, and the recovery codes that get you back in before a lost device becomes a lockout.
I built RecoveryCodes because MFA dependencies should not live in people’s heads.
Before building RecoveryCodes, I kept seeing the same gap. MFA information was scattered, and nobody could confidently say which device or person an important account depended on.
That becomes a serious problem when someone leaves the company or a security key is lost. The accounts most likely to cause an outage often sit outside SSO and standard identity reports.
I built RecoveryCodes to make those dependencies visible before they become a lockout. It is a continuity inventory that helps teams transfer MFA safely and document what happened.
My goal is simple: help teams fix access risks before access is gone.
It is a map. Every account linked to the device / place where the mfa is stored. Never again searching for the mfa device. No guessing anymore on offboarding.
What needs improvement
api integration (1)
I would love an open API to connect the tool to other software.
vs Alternatives
It sits somewhere specific in the stack: the vault holds the secret, the IdP holds the login, this holds the relationships and the proof.