Signed device identity
A device creates its key locally in Windows DPAPI or Android Keystore-backed storage. Its public ID routes requests but never authorizes them.
SV_REMOTE / SERVICE IT
sv_remote: consent-first remote support for managed devices
An independent Service IT remote-support product for Windows and Android. Pair authorized devices, organize them as a tree, see online state and request an end-to-end encrypted screen session that the target user must approve locally.
WORKING VERTICAL SLICE
What the controlled pilot already does
One-time pairing
The target shows an eight-digit code valid for five minutes. A controller uses it once to create the managed relationship.
Device tree and presence
Paired devices can be grouped into nested folders, given local aliases and shown as online or offline with last heartbeat.
Explicit target decision
The target sees the requesting controller and chooses Continue or Reject. Closing the dialog or denying OS capture means rejection.
Encrypted screen channel
The target encrypts screen frames with an ephemeral per-session key before direct or relay transport. The server is not given that content key.
Windows and Android
The pilot includes Windows agent/controller acceptance builds and an Android app that can act as a controller or visible target.
HOW A SESSION STARTS
A device ID is an address, not permission
Register
The client signs registration with the device key and accepts the current B2B legal version.
Pair
The target shows a one-time code to the intended controller.
Request
The controller requests one specific paired target; the request expires quickly.
Approve and stop
The target approves locally and can stop from the permanent indicator at any time.
DELIBERATE PILOT LIMITS
No hidden access and no overclaiming
- No unattended access or hidden start-up
- No remote input or shell execution
- No clipboard or file transfer
- No server-side screen recording
- No public download or app-store release yet
- No SLA, CRA conformity declaration or CE claim in the pilot
The control plane coordinates; endpoints hold the screen key
PostgreSQL stores necessary device, relationship, session and audit metadata. Redis holds short-lived presence, rate-limit and signalling state. STUN discovers network paths and TURN relays encrypted packets when direct connectivity fails. The participating endpoints, not the control plane or relay, encrypt and decrypt the screen.
sv_remote is not an AI system and makes no automated employment or access decision.
LEGAL · 2026-08-23-pilot
Legal documents for the current pilot
The B2B terms, product privacy notice and security/retention page are versioned together. A target's Continue action authorizes only that screen-viewing session; it is not blanket GDPR consent.