Boundary vs JumpServer

Boundary provides authenticated, identity-based access to infrastructure without requiring users to connect directly to its underlying network. It supports just-in-time and least-privilege access, role-based authorization, and single sign-on through OIDC or LDAP. Users can reach TCP, SSH, RDP, HTTPS, RDS, Kubernetes, and database targets through familiar clients such as SSH tools, PuTTY, Remote Desktop, database clients, and web browsers. Boundary can broker credentials and integrate with HashiCorp Vault for short-lived dynamic credentials and credential injection. Target discovery can be automated, with dynamic host catalogs for AWS, Azure, and GCP available in HCP Boundary. Deployment options include managed HCP Boundary, optionally with customer-run workers, and self-managed Boundary Enterprise. The Community Edition is listed at free. HCP Boundary Standard and Plus have usage-based billing, with monthly rates per user depending on edition; Standard includes Vault credential injection and audit-log streaming, while Plus adds session recording. Enterprise is self-managed and has full feature parity with HCP Boundary. Boundary supports Terraform, a REST API, CLI, and SDK.

JumpServer has no write-up on Specifiction yet; its figures are above.