When comparing PuTTY vs Bitvise SSH Client, the Slant community recommends PuTTY for most people. In the question“What are the best SSH clients for Windows?” PuTTY is ranked 1st while Bitvise SSH Client is ranked 14th. The most important reason people chose PuTTY is:
PuTTY is one of the oldest and most popular clients. It has earned the trust of a great number of users over a long period by being reliable, offering useful features and helpful support. It got into the [15 Essential Open Source Tools for Windows Admins list by InfoWorld](https://www.infoworld.com/article/2854954/microsoft-windows/15-essential-open-source-tools-for-windows-admins.html).
Ranked in these QuestionsQuestion Ranking
Pro De facto standard client for SSH, Telnet and Rlogin
PuTTY is one of the oldest and most popular clients. It has earned the trust of a great number of users over a long period by being reliable, offering useful features and helpful support. It got into the 15 Essential Open Source Tools for Windows Admins list by InfoWorld.
Pro Source code available
Full source available. Compile and modify it yourself.
Pro Lightweight and portable
Pro Built-in SFTP window
The client comes with built-in SFTP window to easily move files between the client and the server.
Pro Great option for small businesses
Bitvise is one of the few SSH clients that offers all features free for all types of users, including organizations. At the same time, there are no compromises in terms of functionality. It has an advanced GUI, corporation-wide single sign-on, learning resources including guides and FAQs, and other features.
The SSH client software is free without any limitations.
Pro Can save and load profiles
Profiles can be used to save connection information and connection specific settings.
Con Lacks features
It is JUST an SSH client. There are many other options with built in X-servers, Multitabbing, etc.
Con Can not save passwords
Anyway, you can use "PuTTYgen" to generate a key pair, then use "Pageant" to do a password-less SSH remote login.
Con Ugly design, too simple
Con Tedious logging/tracing
Its tedious to set up logging and tracing (e.g. for serial connections).
Con No global settings
If you want to change a setting for all your connections, you'd have to do it individually.
Con No login scripting
Con Saved profiles(sessions) feature is not good
Why not have a panel to show saved profiles that the user can easily to open sessions?