
# Vault Enterprise Self-Managed

Commercial self-managed secrets and identity security platform deployed as a customer-operated high-availability cluster.

Canonical page: https://launchinyourcloud.com/directory/vault-enterprise/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Vault Enterprise Self-Managed

Commercial self-managed secrets and identity security platform deployed as a customer-operated high-availability cluster.

- Listing: https://launchinyourcloud.com/directory/vault-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Vault Enterprise license required.
- Licensing model: commercial-only
- Installation: Official HashiCorp Validated Design Terraform modules for AWS EC2, Azure VMs or Google GCE
- Architecture: High-availability Vault Enterprise VM cluster with integrated storage, load balancing, TLS and cloud key-management dependencies
- Operations: Customer manages VPC or VNet infrastructure, VMs, load balancers, storage, cloud KMS or Key Vault, TLS, initialization and unseal controls, audit logs, backups, replication, upgrades and licensing.
- Product website: https://developer.hashicorp.com/vault
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

This entry covers Vault Enterprise self-managed, not HCP Vault Dedicated or the separately licensed Community edition. Protect recovery and root credentials, design unseal and disaster-recovery procedures, and review the Terraform modules' requested permissions before deployment.

The selected Vault Enterprise edition requires a commercial license and supports license autoloading or explicit license configuration.

The validated design deploys a persistent high-availability Vault Enterprise VM cluster with integrated storage and provider key-management services.


### Category fit

- identity-access-management: Provides centrally governed secrets, encryption, authentication methods, dynamic credentials and identity-based access policies.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (checked 2026-11-15). 


### Cloud deployment evidence

- Vault Enterprise inside a customer cloud account (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform
  HashiCorp provides official validated-design modules for AWS EC2, Azure VMs and Google GCE and states that the modules deploy a complete Vault Enterprise environment inside the customer's own cloud account.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Deploy Vault Enterprise with official Terraform modules: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform

- Vault Enterprise license keys: https://developer.hashicorp.com/vault/docs/license

- Vault editions: https://developer.hashicorp.com/vault/tutorials/get-started/available-editions

### Licensing sources

- https://developer.hashicorp.com/vault/docs/license

- https://developer.hashicorp.com/vault/tutorials/get-started/available-editions

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Vault documents OIDC browser login from the UI and CLI, using configured identity providers, callback URLs, roles and claim-bound policies. OIDC authentication is distinct from Kubernetes/JWT machine login and from downstream applications consuming secrets. Configure authorization and the selected Enterprise feature entitlements separately. Scope: Self-managed Vault user authentication via the JWT/OIDC auth method. Source: https://developer.hashicorp.com/vault/docs/auth/jwt (reviewed 2026-11-20). Supporting source: Identity-provider configuration examples — https://developer.hashicorp.com/vault/docs/auth/jwt/oidc-providers.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. HashiCorp publishes validated Terraform modules for Vault Enterprise on AWS EC2, Azure VMs and Google Cloud. Provider-specific networking, encryption keys, TLS material and a valid Enterprise license are prerequisites. These modules do not include an Enterprise entitlement. Scope: Vault Enterprise VM installation, HashiCorp Validated Designs. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The integrated-storage reference recommends 2–4 cores, 8–16 GB RAM and 100+ GB SSD at 3,000+ IOPS per small-cluster server; larger workloads have higher tiers. Its resilient topology uses five nodes across three zones. Audit-log I/O, replication and secret/request rates need separate sizing; these figures are not a complete 1 TB HA design. Scope: Official Vault integrated-storage per-server and cluster reference; not an application-data storage estimate. Source: https://developer.hashicorp.com/vault/tutorials/day-one-raft/raft-reference-architecture (reviewed 2026-11-20).

- License pricing: Documented. Vault Enterprise requires a commercial licence key governing feature access and use dates. The current policy distinguishes expiration from termination: release date and termination conditions affect restart, unseal and security-upgrade eligibility. Obtain the applicable self-managed quote, feature/replication entitlements and term; HCP Vault Dedicated uses a separate commercial model. Scope: Current Vault Enterprise self-managed licence-key policy; no public numeric quote established. Source: https://developer.hashicorp.com/vault/docs/license (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






