Questions and answers
Short answers about the free plan, consent and security, remote support, SSH and AI assistants.
RemoteAccessApp is a free remote desktop and remote support app for Windows 10 and 11 and Linux (X11 and Wayland). You can see and control your own PCs, or help someone with theirs, over the internet without port forwarding or a VPN. The person at the PC is asked first and sees a banner while you're connected. It also includes an SSH terminal, SFTP, FTP, RDP and VNC.
Yes. No account is needed to get started: install it and connect with a code. The free plan covers 5 PCs in your account plus 5 saved PCs and 5 saved hosts, with 3 open at once, for personal and commercial use, and no card is needed. It includes unattended access, chat, a remote command prompt, access from a web browser, an SSH terminal, SFTP, FTP, RDP and VNC. There are no session time limits.
No. Since version 0.12.39 the app opens straight to Home with no sign-in. Read your PC's 8-digit code to the person helping you, or type someone else's code to help them; the person at that PC clicks Allow. PCs you connect to are kept in Recent PCs on that computer. Sign in when you want more: a free account adds your own PCs in one list, access from a phone or any browser, and saved PCs on all your computers, and it keeps your Recent PCs.
Yes, Pro is on sale on the website, and everything in the free plan stays free. Pro adds unlimited PCs, saved hosts and open sessions, screenshots, the PC's sound and every monitor, Bedtime, synced saved passwords, Teams, apps through winget on many PCs, schedules and maintenance windows, and the MCP Desktop Connection for AI assistants.
Yes. The free plan is for personal and commercial use alike, within its limits of 5 PCs, 5 saved PCs and 5 saved hosts, with 3 open at once.
The Windows apps run on Windows 10 and Windows 11, 64-bit. The Agent also runs on 64-bit Linux PCs with an X11 or Wayland desktop, so you can reach those too. From a Mac, Linux, an iPhone, iPad or Android device, open your PCs in a web browser at remoteaccessapp.com instead. The remote command prompt needs Windows 10 version 1809 or later on a Windows PC.
Linux, yes: RemoteAccessApp for Linux includes the Agent (so this PC can be reached) and the Console (to reach your other PCs). It runs on 64-bit Linux PCs whose desktop runs on X11 (Xorg) or Wayland, such as Ubuntu, Debian, Linux Mint and Fedora. On Wayland the desktop asks once at the PC to approve screen sharing, and remembers it. The Console for Linux has nearly everything the Windows Console has. There's no Mac app; from a Mac you control your PCs in a web browser. The Windows app also reaches Linux and macOS machines over SSH and SFTP.
1. Download RemoteAccessApp-Setup from remoteaccessapp.com/download and run it on both PCs; no administrator rights are needed. 2. Open it: it starts on Home, with no sign-in. The PC that needs help reads out its 8-digit code. 3. On the other PC, type that code under "Connect to a PC" and the person at the first PC clicks Allow. To keep your own PCs in one list, on your phone or in any browser, sign in (free) and choose "Set up this PC".
No. The installer installs just for you, with no administrator rights and no Windows prompt, and updates itself the same way. IT can install it for every user with the /ALLUSERS switch (needs an administrator once). One installer always installs both the Agent (for the PCs you reach) and the Console (for your own PC).
No. PCs connect out to RemoteAccessApp on their own, so it works behind home and office routers without port forwarding, a VPN or a fixed IP address. PCs set up for local-network access can also connect directly on the same network.
Yes, unless unattended access was turned on at that PC. The PC asks the person there to Allow each session and shows nothing until they do. While anyone is connected, a banner stays on their screen with a chat button, and they can switch to view-only or quit at any time.
Unattended access lets you reach your own PC when nobody is there, free. It can only be turned on at the PC itself. Even then, a console or browser connects without a click only if someone at that PC allowed it once and ticked "connect without asking next time", or if it is signed in to the account that owns the PC (a setting at the PC can turn this off). The PC keeps its trusted list itself, never on the server, and removing a console disconnects it at once. The banner still shows.
With attended access, someone at the PC accepts each connection by clicking Allow, which suits helping a person. With unattended access, the PC lets your own trusted consoles and browsers in without a click, which suits reaching your own PCs when nobody is there. RemoteAccessApp does both with one free download: every PC starts attended, and unattended access is switched on at the PC.
Yes. From the Windows Console, sessions are end-to-end encrypted between your Console and the PC, and the relay only forwards data it can't read. In a web browser the connection is encrypted too, but not end to end: the website server decodes the picture so your browser can show it. Use the Console when that matters.
Whatever is on the PC's screen while the session is open, and, while remote control is on, anything they open with the mouse and keyboard. They can't connect until someone at the PC clicks Allow (unless unattended access was turned on there), a banner shows the whole time, and switching off remote control makes the session view-only. RemoteAccessApp doesn't record sessions.
Your account password isn't sent to the server: since version 0.11.2 the apps and the website send only a key derived from it. Synced saved host passwords (a Pro feature) are end-to-end encrypted, so the server stores only data it can't read. RemoteAccessApp doesn't record sessions.
Only let someone connect to your PC if you contacted them first and know who they are; genuine companies don't cold-call about viruses, refunds or your bank. With RemoteAccessApp nobody sees your screen until you click Allow (unless you turned on unattended access yourself), a banner shows while anyone is connected, and you can quit at any time to end the session.
Installed apps update themselves and accept only updates signed with RemoteAccessApp's key, and the Agent never updates while someone is connected. The website also checks each installer download against the signed release before serving it. The release notes and changelog list what changed in each version.
Ask them to install RemoteAccessApp (free) from remoteaccessapp.com/download and read you the 8-digit code on its Home screen. Type it in your RemoteAccessApp (no account needed) or under Help someone on the website. They click Allow, and you can see their screen, chat and fix things while a banner shows them you're there. Their PC is kept in your Recent PCs, so next time you can reconnect without a new code.
Yes, from the Windows Console. During a session you can open PowerShell or Command Prompt on the PC, or pick several PCs and run one command on all of them, with each PC's output and exit code. Commands run only while "Allow remote control" is on at that PC, and the banner shows when a command prompt is open.
Yes, on the free plan. Sign in at remoteaccessapp.com on any computer, phone or tablet and open your PC in the browser; on iPhone you can add it to the home screen. The browser connection is encrypted, but not end to end.
After a restart, once Windows is signed in again. The Agent runs in your signed-in Windows session and starts when you sign in, so someone has to sign in at the PC (or Windows has to sign in by itself) before it shows as online. Remote tools can't unlock the Windows lock screen, so avoid locking a PC you'll need to reach while nobody is there.
No. A session stays open for as long as you need it, and it reconnects on its own if the network drops.
Yes, with a free account: drop files on a session, copy them either way in two panes, browse the PC's files, or send files to several PCs at once. Without an account (code-only connections) you can still send pictures and files as chat attachments.
Yes. The Windows Console has an SSH terminal in tabs where full-screen programs like htop and vim work, SFTP and FTP file managers, and saved RDP, VNC and web-panel connections. Type a command once to send it to every open SSH tab, or run a saved script. The free plan saves 5 hosts.
Yes, free. In the SSH terminal, the Scripts & History panel (Ctrl+Shift+S) keeps labeled scripts you paste or run with one click, and startup scripts that run every time you connect to a host. In the Windows app you can run a script on many saved hosts at once and see each host's output and exit code. Scripts sync to your account and also appear in the website's browser terminal; command history stays on your own PC and skips passwords.
Any server you can reach over SSH, SFTP or FTP (Linux, macOS, or Windows with OpenSSH Server), plus RDP and VNC servers and web admin panels. Windows PCs running the RemoteAccessApp Agent get the full remote desktop, command prompt and Windows tools.
Yes, with RemoteAccessApp Pro and Claude Code. RemoteAccessApp for Windows includes an MCP server that lets the assistant list your PCs, open a session, take screenshots, click, type and run commands, and run commands on your SSH servers. The PC still asks the person there to Allow, and its banner names the assistant.
MCP (Model Context Protocol) is an open standard for connecting AI assistants to tools. RemoteAccessApp's MCP server comes with the Windows Console, runs on your own PC signed in as you, and is added to Claude Code with one command from the app's MCP page. It is part of Pro; on the free plan it connects to nothing. The help article on how to let an AI assistant help through MCP walks through the setup and what the person at the PC sees.
Only with safeguards, because AI assistants make mistakes: approve each action, keep backups, and keep it away from systems where a mistake would be serious. With RemoteAccessApp the PC still asks the person there to Allow (unless unattended access is on), the banner names the assistant, a view-only PC accepts no input or commands, and Claude Code asks before each tool unless you allowed it. Screenshots and command output go to the assistant's provider under their terms.
The Console's MCP page shows what the assistant is doing, with Disconnect and Stop buttons and a switch that cuts off every assistant at once. Claude Code also asks before each tool unless you allowed it, and the person at the PC can quit the session or switch to view-only.
RemoteAccessApp is made by an Australian business, ABN 64 683 623 065. About us explains why we built it and what we stand for: consent first, your devices under your control, and fair, simple pricing.
No. RemoteAccessApp is proprietary software with a free plan. It uses some open-source components, and their licenses are installed with it in THIRD-PARTY-NOTICES.txt.
PCs set up for local-network access keep connecting directly on the same network. The status page at remoteaccessapp.com/status shows the server's state and the latest release.
Free for 5 PCs, 3 open at once - at home or at work.
