Boundary
7.3#4 in ssh server softwareFree planFree planWebAPILinuxmacOS
Visit
| Fact | Boundary | CoreSSH Server |
|---|---|---|
| API | Boundary exposes a REST API with correlation IDs, rate limiting, filtering, pagination, and standard resource methods. | The documentation describes a REST API for session management and server administration. |
| Authentication | Supported authentication methods are password, OpenID Connect, and LDAP, with OIDC examples including Okta, Auth0, and Microsoft Entra ID. | Listed authentication methods include passwords, public keys, multifactor authentication, 2FA, and Active Directory. |
| Headquarters | San Francisco, California, United States | Chapel Hill, North Carolina, USA |
| Purpose | Boundary provides identity-based, authenticated access to infrastructure without requiring users to access the underlying network directly. | CoreSSH Server is a cross-platform SSH/SFTP server for secure file sharing and shell access. |
| Security | Boundary uses TLS or mutual TLS for communications and supports role-based access control, granular scopes, and envelope encryption for sensitive stored data. | The product offers configurable IP allowlists and denylists, optional encryption at rest, and a FIPS-enabled version by request. |
Boundary suits organizations that need controlled access to infrastructure across a hybrid deployment. It is also relevant to teams using Vault, Terraform, or identity providers such as Okta, Microsoft Entra ID, Auth0, and LDAP.
You want what its maker publishes above — check its page for the details.