The way I read it... it's a password manager that doesn't store passwords (centrally or locally).
Instead it regenerates the password each time.
i.e. password for HN may be: some trait of HN (domain?) + some salt + your identity (cert?) to always produce the same password.
I didn't understand it all from the site, the explanations and broken English didn't really elucidate. But... if my understanding was right, I wondered about how to handle cert changes or key rolling, etc. There seemed to be a mentioned mechanism for this, but again I didn't really understand that from the description.
Gist though: No generated and stored passwords, but a pattern to always generate the same password for a given site.
Instead it regenerates the password each time.
i.e. password for HN may be: some trait of HN (domain?) + some salt + your identity (cert?) to always produce the same password.
I didn't understand it all from the site, the explanations and broken English didn't really elucidate. But... if my understanding was right, I wondered about how to handle cert changes or key rolling, etc. There seemed to be a mentioned mechanism for this, but again I didn't really understand that from the description.
Gist though: No generated and stored passwords, but a pattern to always generate the same password for a given site.