Remote Core documentation

Development documentation — public release validation is still in progress.

Your laptop is the technician console

The Windows technician console remains your main administration software. The agent runs visibly on each authorized Windows device. A separate API and relay coordinate authentication, permissions, consent, and sessions.

Connection architecture

Production hosting is planned at api.devtechskills.com for HTTPS and relay.devtechskills.com for WSS. These are planned deployment addresses, not confirmation of running services. This static website cannot run the .NET API, relay, agent, or PostgreSQL database.

Security and release status

The prototype includes device identities, permissions, consent, signed messages, session visibility, audit events, and explicit disconnect. TLS encrypts each connection hop; the relay can see relayed content. End-to-end payload encryption is not implemented.

Windows service/helper code and an unsigned structural MSI exist. Trusted signing, installed-service acceptance, and real two-device testing remain pending. RDP and multiple concurrent interactive users are unsupported. Public installers are not available.

Local testing

Local API: https://localhost:7443. Local relay: wss://localhost:7444. Start the backend, enroll an authorized device with a short-lived deployment token, launch its visible agent, and request a session from the technician console. Do not put enrollment tokens or credentials in this website.

← Remote Core

CONTACT DEVTECHSKILLS

Need help with your business IT?

For IT support, networking, structured cabling, cybersecurity, Microsoft 365, or consulting in Calgary and surrounding areas, contact DevTechSkills.