Keep account routes separate
Choose an HTTP, SOCKS5 or existing VPN-gateway route for each account. Route credentials are encrypted; working sessions keep their applied route until you explicitly restart them. Requires a supported restricted workspace.
How it works
Account-specific network route
Inspect HTTP, SOCKS5 or an existing VPN gateway for this account. A changed route stays pending for the working process.
Choose a network adapter
Optional account route packages share one editor; credentials remain separate from project files.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Watch the workflow
Loading the recorded terminal…
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.