## Institutional Vault Install Environments

Institutional Vault offers three different environments that can be used to demonstrate the experience to prospective customers or users.

### Demo Hosted Sandbox

We recommend starting with a **Hosted Sandbox** for quick, low-effort evaluation. The sandbox is **preconfigured with testnet chains** so you can test transaction and approval flows end-to-end before committing to deployment work. Sandbox access is typically available within **~1 business day**—reach out at **[support@blockdaemon.com](mailto:support@blockdaemon.com)**.

**Docs**: [Demo Hosted Sandbox enrollment](https://vault.docs.blockdaemon.com/docs/blockdaemon-wallet-sandbox-enrollment-process)

### Self-installed environments

After validating your workflows in the hosted sandbox, you can move forward with a **self-installed** deployment in your own infrastructure.

We recommend a phased approach:

- **Self-installed (testnet)**: Deploy Institutional Vault in your environment while connecting to **testnet chains**. This lets you validate networking, IAM/KMS, observability, approvals, and operational procedures in an environment you control—before taking on mainnet risk.
- **Self-installed (mainnet)**: After testnet validation, deploy/upgrade to a **mainnet** configuration for production usage.

**Docs**: [AWS ECS deployment process](https://vault.docs.blockdaemon.com/docs/aws-ecs-deployment-process)

# 🗣️We Are Here to Help!

Please contact us via [email](mailto:support@blockdaemon.com) or support chat if you encounter an issue, bug, or need assistance. Don't forget to include any relevant details about the problem. To request a wallet form and Institutional Vault Approver form, please click [here](/content/support/index.html) or contact [our sales team](/content/get-in-touch/?contact-sales/index.html).

Updated about 2 months ago