Britive Bridge
Britive Bridge
The Britive Bridge is a self-hosted proxy that sits between your users and the systems they need to reach - Linux and Windows servers, databases, Kubernetes clusters, network devices, and internal web applications. Every connection flows through the Bridge, which grants access just-in-time, records the full session, and hands the recording back to your security and audit teams.
New to the Bridge? Start with the Overview to learn how it works, then pick a deployment mode that matches where you run software.
What the Bridge Does
- Just-in-time access. Users connect through the Bridge instead of holding standing credentials on the target system. Access is granted for a checkout window and automatically revoked when it ends.
- Two ways to connect. Users can connect with the native client tools they
already know (the
sshcommand, a database CLI, Microsoft Remote Desktop), or do everything inside the web browser with nothing to install. - Full session recording. Terminal sessions, desktop sessions, database queries, and web traffic are recorded for playback and audit, with secrets automatically masked.
- Live oversight. Authorized reviewers can watch active sessions, and lock or disconnect them mid-stream.
Where to Start
How the Bridge works and the concepts you need to know.
Step-by-step setup for single-server, AWS, and Kubernetes.
The full configuration file, authentication, recording, and licensing.
Every supported protocol and all of its options.
The access-granting API, the user/auditor/admin roles, and examples.
Connect Bridge to Britive through the co-located broker.
The Admin console, upgrades, backups, and day-to-day running.
Watch live sessions and share view-only links.
Last updated on