
# HashiCorp Boundary Enterprise

Commercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.

Canonical page: https://launchinyourcloud.com/directory/hashicorp-boundary-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.


## HashiCorp Boundary Enterprise

Commercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.

- Listing: https://launchinyourcloud.com/directory/hashicorp-boundary-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Boundary Enterprise license required; HCP Boundary is a separate hosted service.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform architectures plus supported apt, yum or binary packages
- Architecture: Customer-operated Boundary controllers and workers with external PostgreSQL, KMS or HSM integration and PKI.
- Operations: Customer manages controllers, workers, PostgreSQL, KMS, PKI, networking, identity integrations, backups, upgrades and availability.
- Product website: https://www.hashicorp.com/en/products/boundary
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

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.

Boundary Enterprise is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features.

Boundary Enterprise runs persistent controller and worker services on customer virtual machines and depends on external PostgreSQL, key management and TLS infrastructure.


### Category fit

- identity-access-management: Provides identity-aware, policy-controlled access to infrastructure targets without exposing long-lived network credentials.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (checked 2026-11-17). 


### Cloud deployment evidence

- Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Boundary self-managed deployment: https://developer.hashicorp.com/boundary/docs/deploy/self-managed

- Boundary Validated Design deployment: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment

- Boundary pricing and editions: https://www.hashicorp.com/en/products/boundary/pricing

- HCSEC-2026-54: https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932

### Licensing sources

- https://www.hashicorp.com/en/products/boundary/pricing

### Infrastructure sources

- https://developer.hashicorp.com/boundary/docs/deploy/self-managed

- https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 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: Sources checked — unresolved. Self-managed Enterprise deployment and pricing do not establish a current Marketplace offer matching this edition. HCP Boundary is a different operating model. Scope: Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/boundary/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Boundary Enterprise pricing did not establish eligible software charges under the buyer’s cloud commitment agreement. Scope: Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/boundary/pricing (reviewed 2026-11-17).

- Single sign-on: Documented. 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. Scope: Self-managed Boundary identity methods. Source: https://developer.hashicorp.com/boundary/docs/authentication (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. 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. Scope: Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/boundary/docs/authentication (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. 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. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- Security controls: Documented. 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. Scope: Boundary Enterprise deployment security Fixed in Boundary Enterprise 1.0.2 and 0.21.6.. Source: https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment.

- Air-gapped operation: Sources checked — unresolved. 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. Scope: Self-managed Boundary Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/boundary/docs/enterprise/automated-license-reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. 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. Scope: Self-managed Boundary Enterprise validated design. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. 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. Scope: Boundary Enterprise architecture; workload capacity requires session metrics. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- License pricing: Documented. Boundary Enterprise is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features. Scope: HashiCorp Boundary Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/boundary/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. 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. Scope: 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: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. 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. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/boundary/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/boundary/1.1.1+ent/.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- HashiCorp Boundary Vault credential-store SSRF (security-advisory): 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. Conditions: 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. Source: https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932; reviewed 2026-11-18.



