Open the same app.
Both people run RDPTR on their Windows computers. There is no separate support viewer to hunt down.
REMOTE SUPPORT, A LITTLE CLOSER
Different places.
One shared
desktop.
A Windows remote support app for the person who needs a hand and the person ready to help. Same application. Both sides.
In development · Public downloads are not open yet.
+THE SAME APP. ON BOTH DESKS.
RDPTRInterface concept · not a live session
Ready when you are.
One place to give and receive support.
YOUR DEVICE ID · EXAMPLE
482 903 176
OR CONNECT TO SOMEONE
Partner's device ID
Windows application preview
The person at the screen decides.
Local approval. Visible access. A way to disconnect.
01 / WINDOWSOUR FIRST PLATFORM
One Windows application+Your existing desktop+Access on your terms
01 / THE CONNECTION FLOW
A familiar way
to lend a hand.
This is the experience we are building. The first release will focus on Windows and the desktop already in front of you.
Share a device ID.
The person receiving support shares their ID. The helper enters it in their own RDPTR application.
Approve. Then connect.
For attended support, control starts after local approval. The session stays visible and can be ended locally.
02 / ACCESS MODES
A quick hand.
Or a planned return.
Two distinct ways to connect, with the device owner's permission at the centre.
Flow preview · these controls do not change device settings.
03 / WINDOWS RELEASE
The next step
is a working connection.
A public download will appear here after the Windows package and its real remote connection flow pass verification.
WINDOWS · 64-BIT
RDPTR for Windows
Client development is in progress. There is no public installer yet.
No account or email required to view release status.
The interface above is an illustration. Remote desktop control, service behaviour, optional connection 2FA and end-to-end encryption remain subject to implementation and real-device testing.
A FEW THINGS TO KNOW
Before you connect.
Can I download RDPTR today?
Public downloads are not available yet. We will publish a real Windows package with its version, integrity information and release notes after the remote connection flow is verified.
Does the other person need the same application?
Yes. The intended experience uses the same RDPTR Windows application on both computers: one person shares a device ID, the other enters it and requests a connection.
Is two-factor authentication mandatory?
For unattended access, connection 2FA is an optional device-owner setting. When enabled it must be verified at connection authorisation. A device-specific password or revocable key is required even when 2FA is off. Panel-account MFA is a separate protection.
Who controls an attended session?
The intended attended flow requires local approval before screen control starts, a visible session and local disconnection. Rejection or timeout must not open a session. These are release acceptance criteria.