The request landed quietly in the changelog: opt-out support for Hashicorp Boundary. No marketing blasts. No press release. But for teams running Boundary in production, this change matters. It gives control back to operators.
Hashicorp Boundary is built to manage secure access across dynamic infrastructure. It enforces identity-based access and session recording by design. For most users, this is non-negotiable: every connection runs through Boundary's broker, every session is logged. But there are cases — regulatory exceptions, internal tooling, performance testing — where bypassing or disabling certain features becomes necessary. That’s where Boundary opt-out mechanisms enter.
Opt-out in Boundary doesn’t mean abandoning security. It means selectively disabling parts of the system you don’t need for a specific workflow. Common opt-out paths include:
- Disabling session recording for privacy compliance.
- Turning off credential brokering for internal trusted networks.
- Skipping certain authorization checks in non-production environments.
These mechanisms live in configuration and policy definitions. For example, you can set recording_enabled = false at the scope level. You can adjust the broker_mode to simplify credential flow. Opt-out can also happen at the worker level, where you control which features each Boundary worker enforces.