RDP and VNC together
Keep Windows Remote Desktop and VNC connections beside SSH hosts, databases, and project resources.
- Protocol-specific profiles
- Custom ports and security modes
- One remote desktop view
SSH Bridge Remote Desktop
RDP and VNC access your whole project can use
Save and test remote desktops, organize them around real environments, and grant project members encrypted access without exposing credentials. Desktop app required for connections.
RDP and VNC Encrypted access Project-scoped access
Remote Desktop
3 shared connections
Infrastructure project
Shared with 4 members
RDP
Production Windows
10.24.8.12:3389
InfrastructureConnect →
VNC
Design workstation
10.24.8.31:5900
InfrastructureConnect →
RDP
QA Windows
10.24.8.44:3389
InfrastructureConnect →
Remote access with context
More than another saved connection list
Remote desktops live beside the projects, members, SSH hosts, files, databases, and collaboration tools involved in the same work.
Test before you save
Validate the host, protocol service, and required SSH provisioning path before a profile enters your workspace.
- Reachability checks
- RDP or VNC service validation
- Clear pass and failure results
Share by project
Grant an active project member access without copying the owner credential into chat, email, or a spreadsheet.
- Owner and admin controls
- Project member assignment
- Project badges for recipients
Encrypt for each member
Shared access uses a member-specific encrypted credential envelope instead of exposing the owner's stored secret.
- Vault-aware encryption
- Recipient-specific access data
- Credentials stay out of messages
Manage the access lifecycle
Track managed access, verify the result, and enable, disable, or revoke an assignment as project needs change.
- Permission policies
- Verification status
- Access and runtime audit events
Launch a supported client
SSH Bridge Desktop checks the local remote desktop client, explains what is missing, and launches the saved connection.
- Desktop app required for connections
- Installation guidance
- Connection handoff
Share access, not credentials
Encrypt access for the person who needs it
When an owner or admin shares access to a remote desktop, SSH Bridge stores a member-specific encrypted credential envelope on the access record. The recipient sees the shared host and opens it through the Desktop app; the owner's saved secret is not returned as ordinary project data.
- Active project membership is required
- Shared desktops are grouped and labeled by project
- Access can be verified, disabled, enabled, or revoked
OW
Project owner
Owns the RDP host
MB
Project member
Receives encrypted access
Member access record
Status
Active
Role
Standard
Verified
Just now
How it works
From private desktop to project access in three steps
Add and validate the desktop
Choose RDP or VNC, enter the host and approved authentication details, select the security options, and complete the required connection test in the Desktop app.
Choose a project member
From the project, select an active member, the remote desktop host, the managed role, and the permissions appropriate for the work.
Connect with project context
The member receives encrypted access and sees the desktop grouped under the project in their Remote Desktop workspace.
Windows remote access
Save Windows Remote Desktop profiles with an individual or domain account, certificate handling, and negotiate, TLS, NLA, or RDP security options.
- Default port 3389
- Domain-aware accounts
- Windows account provisioning support
Cross-platform screen control
Save VNC profiles for desktops and lab machines with protocol authentication options and the same project-sharing workflow.
- Default port 5900
- Auto, none, or VNC authentication
- Linux and macOS provisioning paths
Give the right member the right remote desktop
Bring RDP and VNC access into the secure project workspace your technical team already shares.