Built for safer remote sessions.
Remote access is one of the scariest things a non-technical user can be asked to do. We designed ioJump so the person being helped is never confused about who is connecting, never has to install anything, and always sees what is happening.
Verified sessions
Before any screen sharing or remote control begins, the session is verified — via SMS, email, or both. The person being helped sees who is connecting and why, then accepts on screen.
End-to-end encrypted
Sessions run peer-to-peer between browsers when network conditions allow. When firewalls require a relay, traffic is routed through encrypted relay infrastructure you can self-host on your own hardware.
Nothing installed
On the customer side, nothing is downloaded. No background agent left running. No privileges to revoke later. The session lives entirely in a browser tab and ends when the tab closes.
Explicit on-screen consent
The person being helped accepts the session on their own device, with the technician’s name shown. No silent connections, no background takeovers, no surprises.
Audit trail by default
Every session is logged in your dashboard — who started it, who joined it, when, from what IP, for how long. Useful for compliance reporting and for chasing down "what happened on Tuesday."
Tenant isolation
Multi-tenant from the schema up. One technician console, many isolated client organizations. No accidental cross-tenant access; per-customer audit and roles.
The threat model we designed against
The riskiest moments in remote support aren’t the encryption — they’re the social ones. ioJump is designed to make sure your end users never have to make a snap decision about whether to trust a stranger:
- "Is the person calling me really from my MSP?" — Sessions are verified via SMS or email tied to the customer record before any access. The verification code is sent through a channel they already trust, not just shown on a screen.
- "What is this software being installed on my computer?" — Nothing is. The customer side is browser-only.
- "Are they watching me now?" — No. They see an explicit consent dialog before any screen share or control begins, and a clear indicator while the session is active.
- "What did they do while connected?" — Every session is logged for the tech’s tenant; for unattended access, every remote command is audited.
What we don’t claim
ioJump is in public beta. We are not yet SOC 2, HIPAA, or ISO 27001 certified. The product is built with those audits in mind, and we’ll publish progress as we move toward them. Until then, the technical controls above are what we lean on — and they’re the same controls many certified products use.
Reporting a security issue
If you believe you’ve found a vulnerability, please email [email protected] with details. We’ll acknowledge within one business day and keep you updated through resolution.
Try a verified support session — free.
Set up your free account, send a 6-digit code, and feel the difference between “download this installer” and “type six digits.”
Free during beta. No credit card.