hashicorp/boundary

Boundary enables identity-based access management for dynamic infrastructure.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on April 8th, 2021
Created on January 8th, 2020
Open Issues & Pull Requests: 162 (+0)
Number of forks: 316
Total Stargazers: 4,055 (+0)
Total Subscribers: 185 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.1 days
Mean response time: 118.0 days
90th percentile: 449.9 days
Tracked items: 77

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 51
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 653 days
Stale 30+ days: 48
Stale 90+ days: 43

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • bug (38)
  • enhancement (37)
  • triage (8)
  • needs-response (2)
  • duplicate (1)

Most active issues this week

Detailed Description

Boundary is HashiCorp's identity-aware proxy designed to provide secure, identity-based access management for dynamic infrastructure environments. Written in Go, the project enables organizations to implement zero-trust security principles by controlling access to hosts and critical systems across networks without requiring agents on individual endpoints. The platform integrates with identity providers through OpenID Connect, allowing users to authenticate securely while receiving just-in-time network access to resources wherever they reside.

The architecture consists of two primary server components: Controllers that serve the API and coordinate session requests, and Workers that handle actual session management. This separation allows for scalable deployments where multiple controllers and workers can be paired together. A single Boundary binary can operate in either or both modes, providing flexibility for different deployment scenarios. The system supports both cloud and on-premises installations, secure enclaves, and container-based workflows without requiring host-level software installation, making it suitable for managed services and modern infrastructure patterns.

Boundary's credential management capabilities distinguish it from simpler access solutions. Organizations can manage session credentials through a native static credential store or dynamically generate unique per-session credentials by integrating with HashiCorp Vault. The platform includes automated discovery of new endpoints and provides session controls for managing privileged access. These features enable teams to standardize access workflows across heterogeneous infrastructure spanning multiple cloud providers and on-premises systems.

The system has two external dependencies: a SQL database for storing configuration and session information with encryption of sensitive values, and a Key Management System for protecting secrets and authenticating workers. PostgreSQL is currently supported as the database backend, with both hosted and self-managed instances compatible. Boundary uses key derivation extensively to minimize key sprawl when managing high-value cryptographic keys, supporting any cloud KMS or HashiCorp Vault's Transit Secrets Engine.

The project maintains connections with other infrastructure and security-focused repositories including Angular, Argo CD, and Envoy through overlapping contributor networks.

Boundary provides multiple client interfaces including a Desktop client and command-line interface for end-users to request and establish authorized sessions. The project includes a development mode for testing that automatically provisions PostgreSQL and ephemeral KMS keys, allowing rapid experimentation. Production deployments require configuration files specifying database and KMS endpoints. The repository explicitly warns against using the main branch for long-term deployments due to potential migration renumbering, recommending release branches instead. Documentation, tutorials, and community forums are available through HashiCorp's developer platform and Discuss community.