> ## Documentation Index > Fetch the complete documentation index at: https://docs.mpcvault.com/llms.txt > Use this file to discover all available pages before exploring further. # Architecture > How MPCVault distributes key shares across multiple cloud environments. ## Key Share Distribution MPCVault uses a 3-of-3 multi-party computation (MPC) setup: | Share | Holder | Location | TEE | | ------- | -------- | --------------- | --------- | | Share 1 | You | Your device | - | | Share 2 | MPCVault | Google Cloud | AMD SEV | | Share 3 | MPCVault | Microsoft Azure | Intel SGX | All three shares are required for signing. No single party ever has access to the complete private key. Key Shares ## Multi-Cloud Infrastructure MPCVault operates across multiple cloud providers, each using a different Trusted Execution Environment (TEE): | Cloud | TEE Technology | Description | | --------------- | -------------- | ------------------------------- | | Google Cloud | AMD SEV | Secure Encrypted Virtualization | | Microsoft Azure | Intel SGX | Software Guard Extensions | This orthogonal platform design reduces the risk of compromise - a vulnerability in one TEE technology doesn't affect the other. Architecture ## No Counterparty Risk Unlike centralized custody providers, MPCVault never holds all your key shares. This eliminates counterparty risk - you always know where your assets are and maintain control over them. You can: * Request your key shares from MPCVault at any time * Designate a Trust to hold encrypted backups for recovery independent of MPCVault ## Recovery Options | Option | Description | | ----------------- | ------------------------------------------------- | | Key Share Export | Request all three shares for full wallet recovery | | Trust Backup | Store encrypted backup with a third-party trust | | Standard Recovery | Use your device and MPCVault's shares together |