HashiCorp Boundary Enterprise
Commercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.
4 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 →
HashiCorp Boundary Vault credential-store SSRF
HCSEC-2026-54 covers CVE-2026-13303, a server-side request forgery issue in the Vault credential store.
Scope: Fixed in Boundary Enterprise 1.0.2 and 0.21.6.
Requires the affected Vault credential-store path and reachable network targets.
Action: Upgrade to the applicable fixed or later Enterprise build and restrict credential-store egress.
Primary source · Reviewed 2026-11-18
What lands where
Supplied by
Vendor or project
HashiCorp Validated Design Terraform architectures plus supported apt, yum or binary packages
Runs in
Documented customer environment
Customer-operated Boundary controllers and workers with external PostgreSQL, KMS or HSM integration and PKI.
- 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 controllers, workers, PostgreSQL, KMS, PKI, networking, identity integrations, backups, upgrades and availability.
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.
Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud ↗ · Source checked 2026-11-17
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud ↗ · Source checked 2026-11-17
- 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.
Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud ↗ · Source checked 2026-11-17
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 | HashiCorp Validated Design Terraform architectures plus supported apt, yum or binary packages |
|---|---|
| Infrastructure | Servers / containers Boundary Enterprise runs persistent controller and worker services on customer virtual machines and depends on external PostgreSQL, key management and TLS infrastructure. |
| Licensing model | Commercial Only Boundary Enterprise is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features. |
| License | Commercial Boundary Enterprise license required; HCP Boundary is a separate hosted service. |
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.
12 of 12 fields researched (100%) · 6 documented · 6 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery
Self-managed Enterprise deployment and pricing do not establish a current Marketplace offer matching this edition. HCP Boundary is a different operating model.
Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility
Boundary Enterprise pricing did not establish eligible software charges under the buyer’s cloud commitment agreement.
Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Boundary supports OIDC through external providers such as Okta and Entra ID, plus separate password/LDAP methods. A primary auth method can create users on first login; this is not evidence of SCIM lifecycle synchronization.
Self-managed Boundary identity methods · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning
Boundary documents OIDC/LDAP and first-login account creation, but a self-managed Enterprise SCIM endpoint and deprovisioning semantics were not established. HCP SCIM is separate.
Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
The reviewed HashiCorp Boundary Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.
Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
The deployment design separates controller and worker paths with database and key-management dependencies. Configure TLS, network access and recovery, and protect credentials used for provisioning. Current advisory review: HCSEC-2026-54 covers CVE-2026-13303, a server-side request forgery issue in the Vault credential store. Upgrade to the applicable fixed or later Enterprise build and restrict credential-store egress.
Boundary Enterprise deployment security Fixed in Boundary Enterprise 1.0.2 and 0.21.6. · Source ↗ · Prior security-controls source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation
The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation.
Self-managed Boundary Enterprise reporting; not blanket isolation of integrations · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The validated design provides Terraform deployment of Boundary controllers and workers in AWS, Azure or Google Cloud. PostgreSQL, key management and network configuration are required; this is not HCP Boundary.
Self-managed Boundary Enterprise validated design · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
Controllers, workers, PostgreSQL and KMS are separate components. Session concurrency and recording/egress requirements determine worker and storage capacity; 100 identities alone do not establish an HA sizing model.
Boundary Enterprise architecture; workload capacity requires session metrics · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Boundary Enterprise is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features.
HashiCorp Boundary Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate
Specify concurrent sessions, recording retention, controller/worker topology, HA PostgreSQL and KMS. Data transfer/session volume and commercial entitlements remain unpriced. A complete monthly operating estimate is not established.
Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The vendor release API identifies 1.1.1+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-11-05. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading.
Enterprise-filtered release API snapshot; community and HCP releases excluded · Source ↗ · Versioned Enterprise binaries and checksums ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
Scope & considerations
This entry covers self-managed Boundary Enterprise, not HCP Boundary. Production deployment requires multiple controllers and workers, an external PostgreSQL database, KMS or HSM-backed key management, TLS and a deliberate worker topology. Validate provider modules, identity integrations and recovery procedures before rollout. HCSEC-2026-54 covers CVE-2026-13303, a Vault credential-store SSRF issue. Fixed Enterprise builds are 1.0.2 and 0.21.6; upgrade the installed maintained branch and restrict credential-store network reachability.
Category fit
- Identity & access management
- Provides identity-aware, policy-controlled access to infrastructure targets without exposing long-lived network credentials.
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
- 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
- Teleport Enterprise Self-HostedCommercial access platform deployed as a high-availability Teleport cluster in the customer's cloud.
- 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
- Boundary self-managed deployment ↗developer.hashicorp.com
- Boundary Validated Design deployment ↗developer.hashicorp.com
- Boundary pricing and editions ↗www.hashicorp.com
- HCSEC-2026-54 ↗discuss.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.
- Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
HashiCorp documents self-managed Boundary Enterprise architectures and Terraform deployments in customer AWS, Azure and Google Cloud environments. Customers operate controllers, workers, PostgreSQL and key management.
- Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud ↗ · AWS, Azure, Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked