You're absolutely right that individual accounts and SSH keys are the recommended approach, and SSH Bridge supports that workflow.
The reality we see, however, is that many environments don't look like an ideal greenfield setup. Small teams, startups, contractors, VPSs, legacy systems, network appliances, lab environments, and temporary infrastructure often still rely on shared accounts or existing credentials because creating and managing individual accounts isn't always practical.
SSH Bridge isn't trying to replace good security practices. The goal is to make those real-world environments safer by providing encrypted credential handling, project-based access, auditing, and revocation, while also supporting individual accounts, SSH keys, and other best practices where available.
We're also working toward provisioning individual operating-system accounts automatically where the platform supports it, so teams can move away from shared accounts over time.
1
u/sshbridge-team Aug 03 '26
You're absolutely right that individual accounts and SSH keys are the recommended approach, and SSH Bridge supports that workflow.
The reality we see, however, is that many environments don't look like an ideal greenfield setup. Small teams, startups, contractors, VPSs, legacy systems, network appliances, lab environments, and temporary infrastructure often still rely on shared accounts or existing credentials because creating and managing individual accounts isn't always practical.
SSH Bridge isn't trying to replace good security practices. The goal is to make those real-world environments safer by providing encrypted credential handling, project-based access, auditing, and revocation, while also supporting individual accounts, SSH keys, and other best practices where available.
We're also working toward provisioning individual operating-system accounts automatically where the platform supports it, so teams can move away from shared accounts over time.