27 lines
1.2 KiB
Plaintext
27 lines
1.2 KiB
Plaintext
       
|
---
|
||
|
|
layout: docs
|
||
|
|
page_title: OSS Boundary
|
||
|
|
description: An introduction to OSS Boundary
|
||
|
|
---
|
||
|
|
|
||
|
|
# Boundary OSS
|
||
|
|
|
||
|
|
Boundary provides secure remote access to critical systems with fine-grained
|
||
|
|
authorizations based on trusted identities. While HCP Boundary provides a
|
||
|
|
managed solution, Boundary OSS is a self-managed distribution that organizations
|
||
|
|
can deploy on-premise to manage access to infrastructure endpoints. The source
|
||
|
|
code for Boundary OSS is freely available on GitHub. The following sections
|
||
|
|
contain information on the use case for Boundary and how to install and
|
||
|
|
configure self-managed Boundary environments.
|
||
|
|
|
||
|
|
Traditional approaches like SSH bastion hosts or VPNs require distributing and
|
||
|
|
managing credentials, configuring network controls like firewalls, and exposing
|
||
|
|
the private network. Boundary OSS provides secure access to hosts and critical
|
||
|
|
systems without having to manage credentials or expose your network, and is
|
||
|
|
entirely open source.
|
||
|
|
|
||
|
|
Boundary OSS is designed to be straightforward to understand, highly scalable,
|
||
|
|
and resilient. It can run in clouds, on-premise, or within secure enclaves.
|
||
|
|
Boundary does not require an agent to be installed on the end host.
|
||
|
|
|
||
|
|
|