Access remote devices with Remote.It
Introduction
Remote.It Packages
Installing the Remote.It Device Package
Remote.It CLI
Connections
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  45 min
Last updated:  03 Aug 2026
Skill level:
  Introductory
Reading time:
  45 min
Last updated:
  03 Aug 2026
Author:Brenda Strech, Remote.It
Arm IP:Neoverse Cortex-A
Tags: CI-CD Linux Windows macOS Remote.It
Author:
  • Brenda Strech, Remote.It
Arm IP:
Neoverse Cortex-A
Tags:
CI-CD Linux Windows macOS Remote.It

Who is this for?

This is an introductory topic for software developers who want to use Remote.It to establish private network connections between users and devices or devices to device.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Install Remote.It on target devices (devices you would like to access remotely)
  • Access your Remote.It enabled devices from anywhere
  • Understand the different types of network connections (proxy vs. Peer to peer)

Prerequisites

Before starting, you will need the following:

  • A Windows, macOS, or Linux computer which you will use to configure your devices as well as connect to your remote devices.
  • A device/computer to which you would like remote access. A device can be a Windows, Mac, or Linux computer including development kits such as Raspberry Pi or cloud-hosted such as within Arm Virtual Hardware or within AWS. You will need a method to control this device before Remote.It is deployed which can be local access or access via another remote connectivity solution (Remote Desktop, VPN, etc.)
  • Determine if your device that you would like to access remotely also needs to make connections to other Remote.It devices.

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll install the Remote.It device package on a target system and establish private access to services such as SSH. You’ll use the Remote.It Web Dashboard to create proxy connections, compare them with peer-to-peer connections, and route traffic through either a Remote.It server or a direct path. You’ll also use the Remote.It CLI for headless or scripted initiators. Then, you’ll verify SSH access and choose the connection method that fits your requirements.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
What result should I expect after installing the Remote.It device package on the target?
The device appears in the Remote.It Web Dashboard. Start a connection and reach it with a standard tool such as SSH from the initiator.
Do I need to install anything on the initiator to make the first connection?
No. For a proxy connection created in the Web Dashboard, use SSH from the initiator without additional software. Install the Remote.It CLI only for a headless or scripted workflow.
Which connection type should I use for my first test, proxy or peer-to-peer?
Use peer-to-peer when you need a direct path between the initiator and target. Otherwise, use a proxy connection. Only the target needs Remote.It, and traffic goes through a Remote.It server.
How do I run the Remote.It CLI on Linux without a desktop environment?
Download the CLI binary for your platform, rename it if needed, and make it executable. Use the CLI to create connections from the initiator without installing the Desktop app.
What should I check if SSH fails after I start a connection?
Verify that SSH is installed and configured on the target. Confirm that the device is visible in the Web Dashboard and that the connection is active before retrying the SSH command.
Next