Your email will not be shared with any third-party.
After the registration will receive up to 10 emails during the next 4 weeks with tips and tricks about the perfect RPort setup and how to get the most out of the RPort solution.
The RPort client (required for remote access and control) runs on all Windows and Linux operating systems, including i386, x86_64 and ARM architectures. While the RPort server also runs on any operating system, we only provide ready-to-use binaries for Linux x86_64.
No. The most common scenario is to run the server on a public server so that all clients can connect from anywhere. You can also run the server on a private network. It is also possible to use port forwarding to make the RPort server available on the Internet.
Installing the RPort server is quick and easy. However, some basic knowledge of Linux is required. You should be familiar with accessing a Linux OS via SSH and be able to edit text files from the console.
Our recommendation is to start simple and expand later if required. Choose a dedicated virtual machine for the first installation! Do not use Docker or reverse proxy. RPort is clean and lean software with everything built in.
The RPort server requires a Linux operating system running on x86_64 or arm64. We recommend Ubuntu or Debian because RDP over the browser works out of the box thanks to the Guacamole DEB packages. Running the rport server on RPM-based distributions or Alpine Linux is also supported. However, you won’t be able to start a remote desktop session from your browser. Using an RDP application such as Microsoft Remote Desktop Client or remina is always supported.
The server runs fine on systemd with just 2GB of RAM and a tiny CPU. It runs perfectly on a Raspberry PI.
RPort includes monitoring of CPU, disks, RAM and processes. The longer you want to store historical data, the more disk space you will need. You can configure how long data is stored or turn off monitoring altogether.
Yes, we do. We currently support
No! We recommend using RealVNC On-Demand Assist as an additional tool.
Yes. See support packages.
That depends on your use case. Let’s say you’re an IT service company or a department within a large organisation and only your organisation’s staff uses rport, free use is covered by our EULA. Sharing access to rport with external staff, such as third party technicians, also doesn’t require a special licence if you don’t charge for the use of rport. As soon as you charge someone for using rport, you need a paid licence. Please contact sales Including RPort in a paid product bundle also requires a paid licence.
Yes and no. The rport server is released under the MIT Open Source Licence. You can freely edit the source code without asking for permission. However, if you plan to add features to the rport server, we recommend that you contact us first. We will be happy to integrate your changes into the main code base. This will ensure that you can apply any future updates.
You can’t make changes to the user interface, as we don’t release the sources. Please send us a note with your desired changes.
Version 1.0 will be certified to manage 10,000 concurrent client connections. Need more? Please ask.
Nothing is impossible. We try to release clients for any platform. Please ask. Fast response promised.
