> For the complete documentation index, see [llms.txt](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enclaive.cloud/enclaive-multi-cloud-platform/documentation/why-use-emcp.md). # Why use EMCP? At Enclaive, we hold a firm conviction that confidential cloud computing represents the future standard for cloud computing. EMCP stands as the platform designed to equip developers with the convenience, assurance, and security necessary to operate their workloads within confidential execution environments. Embracing EMCP offers numerous advantages in technical, economic, and usability realms. * **No Code Changes**: EMCP allows the execution of any application without requiring modifications to the existing codebase. * **Seamless Integration**: There is no need for DevOps adjustments or infrastructure changes, ensuring a smooth transition. * **Zero Performance Penalty**: With just a minimal increase of 2% in CPU cycles, EMCP guarantees top-notch security without compromising performance. * **Multi-Cloud Compatibility**: EMCP supports private, public, hybrid, and multi-cloud environments, providing unparalleled flexibility for users. * **Cost-Efficient**: Move your IT operations to the cloud and benefit from reduced internal IT workload, lowering both capital and operational expenses. * **Shield your workload vertically:** In the cloud environment, workloads are distributed among numerous customers, with isolation between them typically achieved through virtualization by the underlying hypervisor, which is susceptible to known attacks. Enclaving, however, introduces a crucial distinction: while isolation can still potentially be bypassed, in the event of a breach, your workload remains protected. This means that even if an attacker compromises your workload, they can only reconstruct encrypted versions of it, ensuring that no data or code is exposed in plaintext. * **Shield your workload horizontally:** Just as any software or hardware device, clouds are susceptible to hacking. Enclaving your workload within an enclave is akin to securing a private locker in a bank. Regardless of any compromise within the bank or among its employees, only you retain access to your locker. * **Protect Intellectual Property**: Shield your intellectual properties, such as code, data, and documents, even in environments managed by third parties. * **Simplify compliance:** There is a vast number of regulations, documentation and reporting, customers face in many industries. EMCP significantly increases the technical measures and eases the reporting, allowing to gather all relevant information that workload has been executed in the most confidential execution environment. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.enclaive.cloud/enclaive-multi-cloud-platform/documentation/why-use-emcp.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.