# Our Solution We offer a full suite of permissioning solutions, from one-stop-shop compliance for regulated entities (**Keyring Pro**) to fully automated verification (**Keyring Connect**). The core infrastructure to translate and share data is the same, only the way we gather user information differs. The value of our data layer lies in: 1. **Translating compliance requirements into a custom standard language** so that compliance rules can be mapped to data points and compared across policies. 2. **Sharing data in a secure way**, to unlock reusability across platforms (PII flows) and leverage proof of compliance on-chain (zk privacy). * **Keyring Connect**: customers are not heavily regulated and can rely on proof of verification from other platforms. We let users share information from any https-enabled website with a cryptographic proof of authenticity. Think of it as a screenshot of a browser tab with cryptography to prevent fakes and preserve privacy. Read more [here](https://www.keyring.network/blog-posts/from-login-with-to-verify-with-the-future-of-identity). * **Keyring Pro**: customers typically require users' underlying data to verify and hold. We collect user information and route it via API for verification. Verification can be done by our customer's internal compliance desk or a third-party vendor. Once onboarded, users can reuse previously shared information to generate new Credentials[^1] and prove compliance across various use cases (or Policies). Since these Credentials are readable on-chain, the Credentials mapping serves as a dynamic whitelist. ## Why did we choose this framework? Our system facilitates the programmable creation of reusable onboarding flows. Once a user is onboarded for a Policy, we can instantly match the datapoints collected against other Policies to allow 1-click onboarding to allowed partners. * [x] Adaptable: To use cases, transaction parameters and legal environments. * [x] Future-proof: Upgradable, accommodating evolving rules and types of credentials. * [x] Dynamic: Compliance is not immutable, refresh rates enforce monitoring. We believe this fosters a flexible and interconnected environment where different compliance policies don't have to generate massive extra friction for users. [^1]: On-chain representation of a Wallet meeting PolicyID requirements, at a given time. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.keyring.network/docs/introduction/our-solution.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.