How it works Book a 20-min discovery
Remote support · Asset management · On-prem

KRUV Connect: remote support, with consent

Remote control and asset management in one place. Connect from the asset list in one click or with a one-time code, with the user’s approval, and keep an audit-ready record of every session.

1 clickfrom asset list to session
9-digitone-time code for any PC
Consentrequired for every session
Audit logtamper-evident, exportable

Fix it faster, from one place

Remote support usually needs three tools: an asset list, a remote tool and an audit trail. KRUV Connect puts them in one place, so technicians connect instead of hunting.

Faster fixes

Connect from the asset list in one click, or share a one-time code for any PC.

One inventory

Assets come from your patch tool over its API. No second list to keep up to date.

Audit-ready

Every sign-in, session, control request and file transfer is logged in a tamper-evident record.

How a session works

Four steps, with the user’s approval at the start.

01 Request

The technician starts a session from a device, or with a one-time code.

02 Approve

The person at the PC allows screen sharing, and control if needed. Nothing is shared until they allow it.

03 Work

View, click, type, chat and send files inside the session. Either side can end the session or control instantly.

04 Record

Start, control, files and end are written to the audit log.

Two ways to connect

Asset list

Pick an enrolled device and press Connect. The agent opens the join page on that PC.

Quick code

Share a 9-digit code that works once and expires. The person opens a web link and enters it.

Linked to your patch tool, read-only

KRUV Connect reads your asset list. It never changes your patch tool or its data.

  • A read-only API link: assets flow in, nothing is written back
  • Every machine with name, IP and OS, grouped as in your patch tool
  • API key stored encrypted
  • Machines link to their agent by computer name

Asset management at a glance

One view of every device, whether it came from your patch tool or from the agent.

Online and offline

Live agent status with each agent’s last check-in, so offline devices stand out.

Coverage

Assets your patch tool reports versus assets with an agent, so gaps are visible.

Per-device detail

Health (CPU, memory, uptime), session history, and whether the device can be connected right now.

Reports

Session history by technician and device, plus a CSV export of the audit log.

Secure file transfer

Drop a file on the session and it goes straight to the other PC. Files move device to device and are never stored on the server.

  • Fast: sent in chunks with flow control, with a size limit you set
  • Resumable: pause and resume at any time, for large files too
  • Verified: a checksum confirms the file arrived intact
  • Logged: every transfer records the file name, size and checksum

Lightweight agents

A small agent on each PC reports its health and carries the technician’s mouse and keyboard to the screen.

Windows

Deploy by script, GPO, Intune or your patch tool.

Linux

Install script (X11).

macOS

Planned. Browser view already works.

Built-in safeguards

Token-based enrolment, outbound-only connections, encryption in transit, and it runs in the user’s own session.

Security and roles, built in from the first release

Roles

Admin, technician and viewer, each with least-privilege access.

Two-factor

Authenticator-app codes at sign-in. Admins can be required to use it.

Lockout

Five failed sign-ins lock the account for 15 minutes.

Consent

No screen is shared and no control starts without approval.

Tamper-evident log

Each audit entry is chained to the last, so edits show.

Encrypted

Screen, files and chat travel device to device, encrypted.

Compliance targets and secure development

Design commitments and targets for this build. These are not certifications held today.

SOC 2

Controls designed to align with SOC 2 Type II.

VAPT

Tested by an independent firm before release.

SAST

Static analysis with SonarQube on every build.

On-prem and data residency

Runs on your servers, so hosting and data stay in your network.

Our release path: SAST scan, SDLC review, third-party VAPT, fix and retest, then go-live once all findings are closed.

On-premises deployment

Server

Runs on one of your servers, with Docker or Node.

HTTPS

Served on your own certificate, as browsers require.

Agents

Installed by script, GPO or your patch tool.

Patch API

Linked to your patch tool for the asset list.

What comes next

Planned after the first rollout, in the order you choose. Order and dates are agreed before work begins.

Native app

Unattended access, multiple monitors and the sign-in screen.

Wider reach

macOS support and clipboard sync between the two PCs.

Folders

Folder transfer and drag-and-drop onto the remote screen.

Enterprise

Single sign-on, high availability and a Postgres database.

Book a 20-min KRUV Connect discovery

Tell us your device estate and the patch tool you use. We will confirm scope, platforms and compliance targets, then agree a pilot on a few PCs.

Booking calendar

Email us or use WhatsApp to book a 20-minute call.

Book a 20-min discovery