Vault Enterprise Self-Managed
Commercial self-managed secrets and identity security platform deployed as a customer-operated high-availability cluster.
3 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Official HashiCorp Validated Design Terraform modules for AWS EC2, Azure VMs or Google GCE
Runs in
Documented customer environment
High-availability Vault Enterprise VM cluster with integrated storage, load balancing, TLS and cloud key-management dependencies
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
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.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Vault Enterprise inside a customer cloud account ↗ · Source checked 2026-11-15
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Vault Enterprise inside a customer cloud account ↗ · Source checked 2026-11-15
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Vault Enterprise inside a customer cloud account ↗ · Source checked 2026-11-15
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official HashiCorp Validated Design Terraform modules for AWS EC2, Azure VMs or Google GCE |
|---|---|
| Infrastructure | Servers / containers The validated design deploys a persistent high-availability Vault Enterprise VM cluster with integrated storage and provider key-management services. |
| Licensing model | Commercial Only The selected Vault Enterprise edition requires a commercial license and supports license autoloading or explicit license configuration. |
| License | Commercial Vault Enterprise license required. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
Self-managed Vault user authentication via the JWT/OIDC auth method · Source ↗ · Identity-provider configuration examples ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Vault Enterprise VM installation, HashiCorp Validated Designs · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Official Vault integrated-storage per-server and cluster reference; not an application-data storage estimate · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
Current Vault Enterprise self-managed licence-key policy; no public numeric quote established · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
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.
Category fit
- Identity & access management
- Provides centrally governed secrets, encryption, authentication methods, dynamic credentials and identity-based access policies.
Compare within Identity & access management
- authentikIdentity provider for centralized authentication and access policies across connected applications.
- AWS
- FusionAuth Self-HostedProprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Render
- HashiCorp Boundary EnterpriseCommercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.
- AWS
- Azure
- Google Cloud
- Infisical Self-HostedSelf-hosted secrets-management platform with application and machine-identity access workflows.
- AWS
- Google Cloud
- Vultr
- Keycloak Self-HostedIdentity and access management for application sign-on, federation and authorization.
- AWS
- Azure
- NetBird Self-Hosted Community EditionOpen-source zero-trust networking control plane self-hosted on a customer cloud VM.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- DigitalOcean
- Hetzner
- OpenBaoFoundation-governed secrets, key and certificate management with a customer-operated server.
- Linode
- OpenVPN Access ServerSelf-hosted business VPN and network-access server deployed in the customer's cloud account.
- AWS
- Azure
- Google Cloud
Showing 8 of 10 other listings in Identity & access management. These products address related workflows; read their category-fit notes before comparing scope. See all of Identity & access management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Deploy Vault Enterprise with official Terraform modules ↗developer.hashicorp.com
- Vault Enterprise license keys ↗developer.hashicorp.com
- Vault editions ↗developer.hashicorp.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Vault Enterprise inside a customer cloud account ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Vault Enterprise inside a customer cloud account ↗ · AWS, Azure, Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked