Tiled sessions
Up to 10 terminals visible in one desktop window. Resize your desktop to view sessions side by side.
PrototypeProduct overview
One workspace. More control.
A desktop-first tool for day-to-day network engineering. Features shown are part of the prototype or explicitly identified as planned.
Host library
Save up to 500 device profiles with nicknames, host addresses and protocol settings.
PrototypeSSH console
Designed for remote CLI sessions over encrypted SSH using the Windows platform capabilities.
Device dependentSerial console
Use COM ports for direct console access when provisioning or recovering local hardware.
Requires compatible driversLegacy access
Telnet and FTP for explicitly authorized and isolated legacy device management.
Unencrypted protocolsIdentity and vault
Stronger identity-provider sign-in and protected credentials are planned before general release.
Not yet in v1.3Public readiness: The current v1.3 prototype has not completed a third-party security audit, vendor compatibility certification or signed distribution. This site intentionally does not provide an unrestricted executable download.
Protocols
The right tool for each device
Secure remote command-line access should normally use SSH. For transferring configurations, SFTP/SCP are the recommended direction for later versions. Telnet and plain FTP should only be used on trusted isolated networks where unavoidable.
Security principles →| Protocol | Transport | Recommended use |
|---|---|---|
| SSH | Encrypted | Routine CLI administration |
| Serial | Local physical link | Initial setup and recovery |
| Telnet | Plaintext | Isolated legacy equipment |
| FTP | Plaintext | Isolated legacy transfers |
Want a step-by-step example? Read the Windows SSH client setup guide to learn device access prerequisites, host-key checks and troubleshooting.