# Competitive Differences We aim for secure and trustless environments, and reliable coverage is critical to that end. At the core of asset coverage is having the confidence that it's secured by a known community who is there when you need it. Instead of reinventing the wheel, and in line with DeFi philosophy of collaborative growth, we have chosen to use Nexus Mutual as the underwriter for our insurance. Some of the reasons for this are: * Nexus Mutual is trustworthy and has a good track record * It is sufficiently decentralized at this stage considering its maturity. In fact, it is more decentralized than certain competitors who claim decentralization yet depend on central councils or dramatically inefficient governance * It has a large capital pool availability, which directly translates to low cost of insurance Armor will broker both the supply and demand sides of insurance. This gives us the ability of being able to bootstrap supply (by staking NXM through the arNXM yield vault) to reduce insurance costs, and to sell more insurance by capturing a huge untapped market using arCore and arShields. In addition, we already have many more products in various stages of development which will be releasing shortly, and will vastly increase the features and market reach of Armor. We are confident our approach will win a significant portion of the market due to ease of use, costs comparison, and a few other factors as yet unrevealed. --- # 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://armorfi.gitbook.io/armor/faq-1/competitive-differences.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.