# Overview Helios is built with an understanding that institutional adoption requires strict attention to compliance, regulatory alignment, and robust security/auditability. This section outlines how Helios addresses **KYC and permissioned access**, integrates **AML tooling**, provides **auditability and transparency**, and aligns with regulatory frameworks like **MiCA**. The goal is to show that Helios can meet the standards of institutional due diligence without sacrificing its decentralized nature. In summary, Helios’s institutional and compliance features show a mature approach: it’s not DeFi anarchy, but a thoughtful system that *bridges to TradFi requirements while staying decentralized*. Trust-minimized custody, adaptive risk controls, and full transparency are exactly what institutions like custodians, funds, and even banks will look for. With optional KYC and strong AML safeguards, Helios makes itself palatable to compliance teams. And by aligning with frameworks like MiCA from the start, it reduces regulatory uncertainty. All of this builds trust that Helios can handle large capital with integrity and oversight, which is crucial for onboarding institutional players. --- # 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://helios-finance.gitbook.io/helios-finance/institutional-compliance-and-security/overview.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.