RustDesk takes control of the machine. Hippolit knows whose machine it is, who asked for access, and whether it was allowed. The session never touches our servers: RustDesk stays the transport, Hippolit becomes the system of record.
The remote-control tool does its job very well. What is missing is everything around it — which is exactly what Hippolit already knows.
“Device 938 471 205 just got controlled. Whose laptop is that?” RustDesk cannot answer. Hippolit can: the device, its employee, its office, its asset category.
When a technician leaves, you revoke their Google and Slack accounts. Their ability to take control of 200 machines is written down nowhere — so nobody revokes it.
One remote session = one request, one consent, one record. With no Hippolit agent on the machine, and no password ever changing hands.
From the device sheet in Hippolit. The request is dated, signed, and visible to the employee it concerns.
They receive a notification, install RustDesk from the source your company provides, declare themselves ready and share their device ID. Never a password.
You connect to the ID you received. The employee accepts the connection on their own screen: they have the final say, on their machine.
Request, consent, launch: every step is dated and journaled — who asked to control what, when, and with whose agreement.
The RustDesk ID is bound to the device, its employee and its office — entered by hand, reported by the employee themselves, or detected automatically where the Hippolit agent already runs.
Every session rests on an explicit request and an “I'm ready” from the employee, both journaled. Requests expire: last month's agreement does not cover today.
On every device sheet, the history of access requests: who asked to take control, when, and what the employee did with it. Enough to answer an access review without reconstructing anything.
Remote control is the most privileged access there is. The scope of this integration is deliberately narrow — and it is written down.
The integration is under construction. Tell us about your deployment: the first conversations shape the V1.