When comparing Shellngn - Cloud Based SSH Client vs mRemoteNG, the Slant community recommends Shellngn - Cloud Based SSH Client for most people. In the question“What are the best SSH clients for Windows?” Shellngn - Cloud Based SSH Client is ranked 14th while mRemoteNG is ranked 19th. The most important reason people chose Shellngn - Cloud Based SSH Client is:
Since this tool is cloud-based, there's no need to download and install anything. You can simpy run it from the browser.
Ranked in these QuestionsQuestion Ranking
Pros
Pro SSH & SFTP in your browser
Since this tool is cloud-based, there's no need to download and install anything. You can simpy run it from the browser.
Pro RDP/VNC Support
Pro Always up to date
Pro Your devices are available on any device
Pro Tunnel support
Pro RDP/VNC In your browser
Remote desktop your servers from the browser.
Pro Telnet Support
Pro It's free
Open source.
Pro Import/Export feature
Allows to share connections.
Pro Can open multiple sessions in different tabs
Pro Connection manager
Lets you organize your connections into folders with icons as well and allows nested folders as well.
Pro Supports multiple protocols
RDP (Remote Desktop/Terminal Server)
VNC (Virtual Network Computing)
ICA (Citrix Independent Computing Architecture)
SSH (Secure Shell)
Telnet (TELecommunication NETwork)
HTTP/HTTPS (Hypertext Transfer Protocol)
rlogin
Raw Socket Connections
Pro Inheritance from folder properties
Inheritance makes it possible to store properties on folder basis and let the underlying connections inherit this info.
Cons
Con Expensive
$3.90 per month
Con Not free
In fact not only not free, but only available at a subscription basis.
Con Sluggish output
It's ok for a quick session, but compared to native apps it's output is slow.
Con Lack of configurability
Not enough options to trim it to your needs.
Con Can't access LAN servers
Con Private keys needs to be managed on PuTTY
Since mRemoteNG is integrated with PuTTY (included in the installation), all private key needs to be configured on PuTTY itself and then the PuTTY session needs to be selected on mRemoteNG.
