> ## Documentation Index
> Fetch the complete documentation index at: https://docs.turnkey.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Turnkey is wallet infrastructure: create and manage crypto wallets, sign transactions, and enforce policy-based access controls. Best-fit uses: embedded consumer wallets (email/passkey/social auth, no seed phrases), automated onchain operations with server-side wallets, AI agent wallets with policy-scoped signing, enterprise key management, and verifiable off-chain workloads on Turnkey Verifiable Cloud (TVC).
> Every API call is a JSON POST to https://api.turnkey.com signed with a P-256 API key; create an organization and key self-serve at https://app.turnkey.com.
> Key Turnkey developer resources: API reference (https://docs.turnkey.com/api-reference/overview/intro.md), OpenAPI spec (https://docs.turnkey.com/public_api.swagger.json), authentication (https://docs.turnkey.com/features/authentication/overview.md), webhooks (https://docs.turnkey.com/features/webhooks/overview.md), MCP server for docs search (https://docs.turnkey.com/mcp), skill for building with Turnkey (https://docs.turnkey.com/skill.md), agent skills for operating an organization (https://docs.turnkey.com/get-started/ai-skills.md), CLI (https://docs.turnkey.com/sdks/cli.md), SDK reference (https://docs.turnkey.com/sdks/introduction.md), full docs content (https://docs.turnkey.com/llms-full.txt).

# Enterprise Disaster Recovery

> Import and recover wallets with end-to-end encryption, quorum-controlled access, and a cryptographic audit trail.

Back up wallets on Turnkey and recover them when you need to for incident response, provider migration, and redundancy. All key material is encrypted directly to Turnkey's secure enclave using [HPKE](https://docs.turnkey.com/security/enclave-secure-channels.md), and every recovery operation is cryptographically stamped. For an overview of Turnkey's key management capabilities, see the [Key Management Overview](https://docs.turnkey.com/solutions/key-management/overview.md).

## Key implementation decisions

| Decision | What to consider | Learn more |
| :- | :- | :- |
| **Organization setup** | Create dedicated recovery users with limited permissions. Distribute authenticators (passkeys, YubiKeys) across geographic locations where possible. | [Organizations](https://docs.turnkey.com/features/organizations.md) |
| **Root quorum** | Require multiple approvers for sensitive operations to prevent any single credential compromise from triggering unauthorized recovery. | [Root Quorum](https://docs.turnkey.com/features/users/root-quorum.md) |
| **Recovery policies** | Restrict what can be done with recovered wallets: limit fund movement to allowed addresses, require multi-party approval, scope signing by chain or value. | [Policy Engine](https://docs.turnkey.com/features/policies/overview.md), [Signing Control](https://docs.turnkey.com/features/policies/examples/signing-control.md) |
| **Import method** | Use the NodeJS server SDK for the full import flow including encryption and secure transport, or the React Wallet Kit for client-side import. | [Import Wallets](https://docs.turnkey.com/features/wallets/import-wallets.md), [SDK Server](https://github.com/tkhq/sdk/tree/main/examples/key-management/import-in-node) |

## Example: treasury recovery

Import wallet keys into Turnkey's secure enclave ahead of time. If a key holder becomes unavailable or a hardware wallet fails, recover treasury assets with quorum-controlled access and policy-restricted fund movement.

![turnkey enclave secure wallet import ceremony](https://mintcdn.com/turnkey-0e7c1f5b/O0eHJyArty3qEnge/images/key-management/enterprise-disaster-recovery.png?fit=max\&auto=format\&n=O0eHJyArty3qEnge\&q=85\&s=a592325675e76a521a72eba2ed9ee2e8)

| Need | How Turnkey solves it |
| :- | :- |
| Import keys with no plaintext exposure in transit | All key material is encrypted directly to the enclave using [HPKE](https://docs.turnkey.com/security/enclave-secure-channels.md). Plaintext never exists outside the enclave boundary. |
| No single person can unilaterally move recovered funds | [Quorum approval](https://docs.turnkey.com/features/users/root-quorum.md) requires multiple approvers for sensitive operations |
| Restrict what can be done with recovered wallets | [Policies](https://docs.turnkey.com/features/policies/overview.md) scope fund movement to allowed addresses, chains, and value thresholds |
| Cryptographic audit trail | Every recovery operation is cryptographically stamped, ensuring recoveries cannot be tampered with |
| Secondary signing path must always be available | Import backup copies of critical wallet keys so operations continue if a primary signer goes down |

### Implementation steps

> [!NOTE]
>
> Explore the complete implementation in the [GitHub disaster-recovery example](https://github.com/tkhq/sdk/tree/main/examples/key-management/disaster-recovery).

**1. Set up organization and recovery policies**

Create a [Turnkey organization](https://app.turnkey.com/dashboard/auth/initial) and establish the security foundation for recovery operations:

* Create dedicated recovery users with specific, limited permissions
* Configure the [Root Quorum](https://docs.turnkey.com/features/users/root-quorum.md) to require multiple approvers for sensitive operations
* Distribute authenticators ([passkeys](https://docs.turnkey.com/features/authentication/passkeys/introduction.md), YubiKeys) across geographic locations
* Define [policies](https://docs.turnkey.com/features/policies/examples/signing-control.md) that restrict what can be done with recovered wallets

**2. Initialize and encrypt the wallet bundle**

Use the [NodeJS server SDK](https://github.com/tkhq/sdk/tree/main/examples/key-management/import-in-node) to initialize the import and encrypt the wallet material to Turnkey's enclave:

```ts theme={"system"}
import { Turnkey } from "@turnkey/sdk-server";
import { encryptPrivateKeyToBundle, encryptWalletToBundle } from "@turnkey/crypto";

const initResult = await turnkeyClient.apiClient().initImportWallet({
  userId,
});

const walletBundle = await encryptWalletToBundle({
  mnemonic,
  importBundle: initResult.importBundle,
  userId,
  organizationId,
});
```

**3. Import the wallet**

Use [importWallet()](https://docs.turnkey.com/generated-docs/core/turnkey-client-import-wallet.md) to transmit the encrypted bundle. The enclave decrypts and stores the key material. All fund movements are logged with cryptographic signatures.

```ts theme={"system"}
const walletImportResult = await turnkeyClient.apiClient().importWallet({
  userId: userId,
  walletName: "Your imported wallet!",
  encryptedBundle: walletBundle,
  accounts: [],
});
```

## Next steps

Import Wallets

Full guide for importing wallets and private keys into Turnkey.

[Open](https://docs.turnkey.com/features/wallets/import-wallets.md)

Export Wallets

Export wallets and keys when needed for migration or backup.

[Open](https://docs.turnkey.com/features/wallets/export-wallets.md)

Policy Engine

Define granular access controls and approval requirements.

[Open](https://docs.turnkey.com/features/policies/quickstart.md)

![](https://docs.turnkey.com/images/solutions/light/encryption-key-storage.svg)

Encryption Key Storage

Store encryption keys with risk separation between your infrastructure and Turnkey.

[Open](https://docs.turnkey.com/solutions/key-management/encryption-key-storage.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.