HashiCorp Boundary
8.3/10Save $45,000/yrBest open-source PAM with MPL-2.0 OSS and HCP managed cloud
Open-source modern PAM with MPL-2.0 OSS, identity-based access, and HCP managed cloud.
| Plan | Monthly | Annual | What you get |
|---|---|---|---|
| OSS Community | Free | — | Free open-source self-hosted Boundary with identity-based access and RBAC on self-managed clusters. |
| HCP Boundary Standard | $1,250.00/mo | $15,000.00/yr | Managed Boundary on HashiCorp Cloud with Vault integration, audit logs, and worker-pool support. |
| Enterprise | $5,000.00/mo | $60,000.00/yr | Self-managed enterprise Boundary with governance, SSO, dedicated CSM, and Vault bundle. |
HashiCorp Boundary is the open-source modern PAM for HashiCorp-ecosystem teams who already run Vault, Terraform, and Consul. Released in 2020 and now part of IBM after the Feb 2025 acquisition, Boundary built around the thesis that PAM should be identity-based rather than network-based, with no agents on target hosts and no static credentials handed out to operators.
Three tiers cover the lifecycle. OSS Community ships free open source self-hosted with identity-based access and RBAC on self-managed clusters. HCP Boundary Standard adds managed Boundary on HashiCorp Cloud with Vault integration, audit logs, and worker-pool support at usage-based pricing. Enterprise opens self-managed enterprise Boundary with governance and dedicated CSM.
The load-bearing wedge is HashiCorp-ecosystem integration plus identity-based access. Where Teleport ships its own audit-and-recording stack, Boundary brokers connections through identity-aware workers with no agents on hosts and tight Vault integration for credential brokering. The catch is the smaller standalone feature set; Boundary is strongest paired with Vault. For HashiCorp-ecosystem PAM, Boundary is the proven path; for non-HashiCorp shops, Teleport covers more out of the box.
Pros
- MPL-2.0 OSS with no MAU cap or licensing fee on OSS Community
- Identity-based access without agents on target hosts
- Tight Vault integration for credential brokering
- Composite leader at neutral fit on free-OSS plus low managed-cloud entry
- HashiCorp ecosystem fit for teams already running Vault and Terraform
Cons
- Smaller standalone feature set than Teleport without Vault pairing
- HCP Standard usage-based pricing harder to forecast than per-user lists
Best for: HashiCorp-ecosystem teams running Vault and Terraform who want identity-based PAM in the same stack.
- Audit posture
- 8
- Deployment speed
- 8
- Admin overhead
- 7
- Value
- 9
- Support
- 7