The below terms are commonly used in remote.it and can help you understand and use the remote.it systems.
Term |
Definition |
|---|---|
Application |
Software or a program running on a device to which you make a connection. Examples: |
Connection Settings |
When making a connection from one device to another, there are configurations which set the behavior for a connection. Connection Name: A friendly name that you can set to distinguish a connection from another Routing: When using the remote.it desktop, CLI or mobile applications, it will reconnect automatically when the initiator device attempts to use the connection again after the idle time is exceeded. |
Initiator Device |
The local computer that has remote.it installed. Connections are outbound. |
License |
remote.it is free for up to 5 non-commercial devices. A license and subscription authorizes the user to connect and run scripts for more than 5 devices. When a user doesn't have an active professional or enterprise license, connection and scripting access is limited to the first 5 devices by create date. |
Organization (coming soon) |
A grouping of users who can have access to devices which belong to organization. The user who creates the organization will be the owner and all of their devices will automatically transfer to the organization. The owner can add users to the organization making them members. The owner is also responsible for licensing of users in the organization |
Organization Member |
Users who have been added to an organization (admins and members). The owner of the organization is responsible for licensing the organization's users by purchasing seats. Licensed: The owner has assigned a seat license to the user and the user has full access to the organization's devices/services Unlicensed: The owner has not assigned a seat license to the user and the user will only have access to the first 5 devices (by create date) of the organization. |
Peer to peer connection |
A remote.it connection to a target device that is initiated from your computer. Click here for more on connection types |
Peer to peer with proxy failover |
A remote.it connection which attempts to use the peer to peer connection method first and if unavailable will rollover to using a proxy connection. Click here for more on connection types |
Proxy connection |
A remote.it connection to a target device that is initiated from our servers and remaps the port. Click here for more on connection types |
Registration |
The process of adding a device and/or services to the remote.it system. |
Reverse proxy connection |
A type of remote.it Service, used only to connect to web servers, which does not remap the port |
Service
|
A configuration registered on the target device which you will use to access remote applications. The target device can have many services. There is a bulk service created by default and does not require entry of any service attributes. The bulk service provides the basis for a target device and enables scripting functionality.
Attributes of a service:
|
Service Agent |
The remote.it daemon which is associated with the target device service which enables remote.it connections. |
Scripting |
The remote.it feature which allows you to run a script on any number of target devices. This uses interpreted languages such as bash, Python, Ruby, Node, etc., assuming you have the interpreter installed on your system. This feature is only available via the remote.it portal https://app.remote.it For more on this feature, visit the scripting articles Examples: Fetching device information for a group of devices Updating devices deployed in the field |
Target Device |
The remote computer or VM you want to connect to and/or run scripts against with remote.it installed. Connections are inbound. Examples: Raspberry Pi AWS AMI Windows Server |
User |
A person with a remote.it account. They may create devices/services and perform functions against their own devices such as connection, sharing, and script execution. |