Termius can scale with the needs of your team. It can handle setups from a home lab with a handful of IOT devices to a data center with thousands of pieces of infrastructure. Information management and navigation are much easier if you utilize the below-mentioned elements.
Termius is built around the concept of a host, which represents a remote machine. This remote machine can be accessed via several protocols like SSH, SFTP, Mosh, or Telnet. More information about supported protocols.
Icon and label are optional parameters for easier host identification if the host address does not provide this mechanism. The icon is assigned during the first connection for the systems where Termius can detect it automatically—more information about detecting OS.
Credentials are often reused and could be used for accessing any number of hosts. Rotating keys and passwords is a standard security practice in most engineering teams. Identities provide an easy way to manage credentials used for authentication on multiple hosts.
Groups allow bundling together of hosts that either belong to the same environment, like development or production or could be bundled by the type, like database cluster nodes. Groups support multiple levels of the hierarchy to maintain thousands of hosts easily.
Often hosts in a group have similar parameters like port or startup command. Those options are better to assign to a group for easier editing in the future. The hosts inside a group inherit the setting from the group. This feature is also flexible and provides a way to set up an exception in a host in case there is a need to use a custom value for a host without taking it out of the group.
Tags are a simple mechanism to mark and search a host with a particular trait. It could be used in many different ways to keep track of software installed on a host(MySQL, nginx, Hadoop) or the purpose of the host(DB, web, cluster). A few tags are created by default for each host: enabled protocol, username, OS, or Linux distro.