1. As opposed to the standard PKI where the system generates an X.509 certificate which is then trusted by your system by having the authority registered, our s

1. As opposed to the standard PKI where the system generates an X.509 certificate which is then trusted by your system by having the authority registered, our system relies more on live generation of Public + Private keys and securely sending the public bit to the Zalter servers during the authentication process. The service providers would then retrieve the public key as they're presented with signed requests, and verify the said signature to ensure the user is who they claim they are and the request is in fact coming from them. Meanwhile we do aim to have an X.509 solution as well, the current design is indeed allowing the app server to not have to rely on cookies / oauth and other similar things. 2. https://discord.gg/HFPnS3M7 https://discord.gg/HFPnS3M7 3. Thanks for pointing that out. The correct text should have been something along the lines of: We only hold the public keys and the identity ids in our own database. All the other associations are to be held on the service provider servers. Accessing the database of users can be made through your dashboard in your zalter user: https://dashboard.zalter.com/ https://dashboard.zalter.com/ 4. It is being actively developed although we haven't had a whole lot of time to write blog posts as we have focused our efforts into developing the product main feature. We're currently writing more blog posts and show more activity.