RRemoteLink
Sign InGet Started

Architecture

How RemoteLink fits together

RemoteLink is built in two halves. The cloud looks after accounts, sessions, consent and the short setup conversation between two computers. The screen picture itself never passes through it — it travels directly between the technician and the customer.

        REMOTELINK CLOUD
  ┌──────────────────────────────┐
  │ Authentication               │
  │ User Accounts                │
  │ Session Management           │
  │ Device Management            │
  │ Signaling                    │
  │ Permissions                  │
  └──────────────┬───────────────┘
                 │
           Secure Signaling
                 │
       ┌─────────┴─────────┐
       │                   │
 Technician             Customer
  Browser             Windows Agent
       │                   │
       └────── WebRTC ─────┘
                 │
           Screen Stream

Inside the cloud

Authentication

Built

Email and password or Google sign-in, handled by the hosted auth service. Passwords never touch our own tables.

User accounts

Built

A profile record per technician, created automatically at sign-up and readable only by its owner.

Session management

Built

Every support session is a stored record with a short-lived nine-digit code, an expiry time, and one shared state that both sides read.

Device management

Coming soon

Technicians can register the computers they support. Devices stay offline until a real agent checks in.

Signalling

Built

A realtime channel per session that carries the short setup messages two computers need to find each other.

Permissions

Built

The customer sees exactly what is being requested and approves it. Only screen viewing can be switched on today.

The connection path

  1. 1

    Technician browser

    Built

    Creates the session, shows the code, waits for approval, and displays the incoming screen once the connection is genuinely established.

  2. 2

    Customer Windows agent

    Coming soon

    The program the customer runs. It registers the device, captures the screen and answers the connection request. It has not been built yet.

  3. 3

    Secure signalling

    Built

    Both sides join the same private channel and exchange the details needed to open a direct connection. Nothing here carries picture data.

  4. 4

    Direct screen stream

    Coming soon

    Once connected, the picture travels straight between the two computers rather than through our servers.

How a computer gets added

This is the planned path for the RemoteLink agent. None of it runs yet — a computer you add today is a label only, and will stay offline until the agent exists.

  1. 1

    Install the agent

    Coming soon

    The customer, or the technician on their behalf, installs the small RemoteLink program on the computer that needs support.

  2. 2

    Generate a device identity

    Coming soon

    On first run the agent creates a unique identity for that computer and keeps its private half on the machine.

  3. 3

    Connect to RemoteLink

    Coming soon

    The agent opens an outbound connection to the service, so no ports need to be opened on the customer's network.

  4. 4

    Authenticate and register

    Coming soon

    The service checks the identity and links the computer to the right account, recording its name, operating system and agent version.

  5. 5

    The device appears in your dashboard

    Coming soon

    Once registered, the computer shows up under My Devices with a genuine online or offline state and the time it was last seen.

How the screen reaches the technician

The viewing side in the app is finished and waiting. The capture and encoding steps live inside the agent, so the picture only starts flowing once that program exists.

  1. 1

    The Windows screen

    Coming soon

    Whatever the customer can see on their own display, and nothing more — no hidden or background access.

  2. 2

    The RemoteLink agent

    Coming soon

    Only starts after the customer has approved the request, and stops the moment either side ends the session.

  3. 3

    Screen capture

    Coming soon

    The agent reads the display frame by frame, at a rate it adjusts to suit the connection.

  4. 4

    Video encoding

    Coming soon

    Frames are compressed on the customer's computer so they can travel over an ordinary internet connection.

  5. 5

    Direct connection

    Coming soon

    The compressed video is sent straight to the technician rather than being stored or relayed through our servers.

  6. 6

    Technician browser

    Built

    Plays the incoming picture in the session view. This side is already built and shows a waiting message until a real stream arrives.

If the connection drops

A live session never pretends to be healthy. The status you see follows the real connection, including while it is trying to come back.

CONNECTED
   |
NETWORK INTERRUPTION
   |
RECONNECTING...
   |
CONNECTED
  1. 1

    Connected

    Built

    Both sides are joined and the session is live. The status shown comes from the connection itself, never from a guess.

  2. 2

    Network interruption

    Built

    If the link drops — wifi, a dead spot, a router restart — the session does not silently look fine. The status changes straight away for both people.

  3. 3

    Reconnecting

    Built

    The connection tries to rebuild itself for a short while. The picture is paused during this time and both sides can still end the session.

  4. 4

    Connected again

    Built

    If it comes back, the session continues where it left off. If it cannot, the session is marked as failed and closed cleanly rather than left hanging.

When a session ends

Ending is a clean shutdown, not just a closed window. Nothing stays open behind it.

  1. 1

    Connection closed

    Built

    Whoever ends first — technician or customer — the direct link between the two computers is shut down immediately.

  2. 2

    Session marked ended

    Built

    The session is recorded as ended with a timestamp, so both sides and the history page show the same thing.

  3. 3

    Session code invalidated

    Built

    The temporary code stops working the moment the session ends, so it can never be reused to reach that computer again.

  4. 4

    Agent returns to ready

    Coming soon

    The customer's agent stops capturing the screen and goes back to idle, waiting for the next approved request.

How remote mouse control works

Built

Mouse control is a second, separate approval — agreeing to screen viewing never turns it on. The customer can withdraw it at any time without ending screen sharing, and it stops on its own the moment the session, the connection or the permission goes away. Keyboard, file transfer and clipboard remain switched off. Windows itself still blocks input into the security prompt and other protected windows, and RemoteLink does not try to get around that.

  1. 1

    Technician

    Coming soon

    Moves or clicks the mouse over the live picture of the customer's screen. Keyboard, files and clipboard are still switched off.

  2. 2

    Control channel

    Coming soon

    A separate lightweight channel alongside the picture carries only small mouse messages, never video and never anything else.

  3. 3

    RemoteLink agent

    Coming soon

    Checks every message against the permission the customer actually approved, and drops anything that fails a check.

  4. 4

    Windows input

    Coming soon

    Only then is the action replayed on the customer's computer as a real mouse move, click or scroll.

  5. 5

    Customer computer

    Coming soon

    The customer sees that mouse control is active, can stop it on its own, and can end the whole session at any moment.

Inside the RemoteLink Agent

Coming soon

The agent is the Windows program that will run on the customer’s computer. It does not exist yet; these are the parts it is designed around, and each one has a matching place already prepared in the app.

RemoteLink Agent
 │
 ├── App
 ├── Authentication
 ├── Device Registration
 ├── Heartbeat
 ├── Session Manager
 ├── Permission Manager
 ├── Screen Capture
 ├── WebRTC
 └── Logging

App

Coming soon

The program itself: installs on Windows, runs quietly in the background, and gives the person at the computer a window showing what is going on and a way to stop it.

Authentication

Coming soon

Proves to RemoteLink that this computer is the one it claims to be, using its own stored token rather than the customer's password or the device name.

Device registration

Coming soon

Pairs the computer with an account once, using a single-use code, then reports its name, operating system and agent version so it appears under My Devices.

Heartbeat

Coming soon

Checks in every few seconds so the dashboard can tell whether the computer is really reachable. If check-ins stop, it is shown as offline rather than guessed to be online.

Session manager

Coming soon

Tracks which support session the computer is part of and follows the same states the cloud does: waiting, approved, connecting, connected, ended.

Permission manager

Coming soon

Holds what the person at the computer actually approved and refuses anything outside it. In this phase that means viewing only.

Screen capture

Coming soon

Reads the Windows desktop picture only while an approved session is running, and stops the moment it ends.

WebRTC

Coming soon

Holds the direct connection to the technician's browser, sends the picture over it, watches the real connection state and handles interruptions.

Logging

Coming soon

Keeps a local record of what happened and when — paired, requested, approved, connected, ended — matching the history shown on the device page.

What the agent does on a Windows PC

Coming soon

The same parts seen as a sequence: what happens on the customer’s computer, from installing the agent to closing a session. None of this runs today.

Windows PC
 │
 ▼
RemoteLink Agent
 │
 ├── Register computer
 ├── Receive support request
 ├── Ask user for permission
 ├── Capture screen
 ├── Establish WebRTC
 └── Stop connection
  1. 1

    Register computer

    Coming soon

    On first run it introduces the computer to RemoteLink and links it to the owner's account, so it appears under My Devices.

  2. 2

    Receive support request

    Coming soon

    It listens for a support request aimed at that computer instead of waiting for someone to open a web page.

  3. 3

    Ask user for permission

    Coming soon

    It shows the request on the customer's own screen — who is asking and what for — and waits. Nothing is captured before they agree.

  4. 4

    Capture screen

    Coming soon

    Only after approval does it start reading the Windows desktop picture.

  5. 5

    Establish WebRTC

    Coming soon

    It opens a direct connection to the technician's browser and sends the picture over it, not through our servers.

  6. 6

    Stop connection

    Coming soon

    When either side ends the session, capture stops, the connection closes, and the computer goes back to idle.

The build plan

Twelve steps from the product you can click today to a full commercial support service. The first four are done; everything from the Windows agent onwards is still ahead.

  1. 1
    Phase 1

    The product itself

    Built

    Pages, navigation, sign up and sign in, dashboard, session screens and history.

  2. 2
    Phase 2

    Accounts and security

    Built

    Database structure, roles kept out of reach of self-assignment, per-user access rules, secure one-off session codes with expiry and rate limiting.

  3. 3
    Phase 3

    Sessions and setup channel

    Built

    Shared session state, the full lifecycle from waiting to ended, the event log, and the realtime channel that coordinates a connection.

  4. 4
    Phase 4

    Direct connection plumbing

    Built

    The direct browser-to-computer connection layer: offer, answer, network candidates, real connection state and clean shutdown. Built and waiting for something to connect to.

  5. 5
    Phase 5

    Windows RemoteLink Agent

    Coming soon

    The program that runs on the customer's computer: identity, registration, session handling and local safeguards. Not started.

  6. 6
    Phase 6

    Real screen sharing

    Coming soon

    The customer's Windows desktop captured by the agent and shown live in the technician's browser.

  7. 7
    Phase 7

    Mouse and keyboard

    Coming soon

    Remote control, only with the customer's explicit approval. Deliberately switched off until then.

  8. 8
    Phase 8

    File transfer and clipboard

    Coming soon

    Sending files both ways and sharing copied text, each as its own approved permission.

  9. 9
    Phase 9

    Device management

    Coming soon

    Real online and offline states, last seen times and agent versions coming from the computers themselves.

  10. 10
    Phase 10

    Unattended access

    Coming soon

    Connecting to a registered computer without someone sitting in front of it, with strict consent rules set up in advance.

  11. 11
    Phase 11

    ABCLED technician platform

    Coming soon

    Team accounts, technician roles and the day-to-day tools a support team needs.

  12. 12
    Phase 12

    Commercial platform

    Coming soon

    Billing, plans, reporting and everything needed to run this as a paid service.

What is honestly working today

Accounts, sessions, codes, expiry, the customer approval step, the shared session state and the realtime setup channel are all real and running. Screen viewing and mouse control are wired end to end and need the RemoteLink agent running on the customer’s Windows computer. Remote keyboard, file transfer and clipboard are deliberately switched off and are not part of this phase.