Early Access — Open for developer integration testing

Account security

MFA authenticator and account security

Manage TOTP authenticator entries, passkeys, and CAIRL account-security methods from a single control surface.

What it does

CAIRL provides a person-facing surface for supported MFA and account-security methods. Instead of treating second factors as disposable setup steps, the surface keeps supported authenticator entries and security methods connected to the person's CAIRL account.

That includes TOTP authenticator entries, one-time code generation, and supported passkey and account-security operations. It is not a generic password, note, or connection-credential vault.

Account-security methods reinforce the broader architecture: the person controls their identity while authorized interactions receive the assurance relevant to their purpose.

Key capabilities

TOTP storage

Keep authenticator secrets in the identity context instead of scattering them across devices and ad hoc tools.

Code generation

Generate one-time passwords from the same interface used to manage the account inventory.

MFA method management

Organize supported MFA methods and update them as account-security needs change.

Identity-context control

Treat MFA as part of the user's controlled identity layer rather than a disconnected utility.

Ready when you are

Move from explanation to implementation.

CAIRL is built to let users control identity and let platforms trust the result. Choose the next step that matches the surface you are building.