Self-hosted remote desktop

Deploy GoMyid On-Premise around infrastructure you control

Build a remote desktop environment for your own network, server policies, administrators, and operating model. GoMyid On-Premise combines native Windows access with a private web management panel, device organization, reports, alerts, and scheduled operational workflows.

Plan Your Deployment Compare Features

Deployment roadmap

Move from requirements to controlled rollout

A successful self-hosted remote desktop deployment begins with ownership decisions, not installation clicks. Define who operates the service, which networks and computers participate, how administrators are separated, and which reporting or alert workflows are required.

1. Discover

Map locations, Windows computers, administrators, network boundaries, remote users, and expected session volume.

2. Prepare

Prepare the server environment, database, service identity, web access, certificates, firewall rules, and backup policy.

3. Pilot

Enroll a controlled group of computers and administrators, then verify access, permissions, reporting, and support workflows.

4. Roll out

Expand by group or location, monitor availability, document ownership, and review alerts and scheduled reports.

Architecture responsibilities

Your environment, your operating decisions

On-Premise gives the organization control of the GoMyid service and administration layer. That ownership also means internal teams define availability, server maintenance, database protection, network reachability, monitoring, and recovery procedures.

Platform layer

Operate the application services, database, web management panel, and required service accounts.

Network layer

Decide how branches, VPN users, firewalls, private networks, and authorized endpoints reach the platform.

Identity layer

Create administrators, assign approved management pages, and organize users, groups, and computers.

Operations layer

Review service status, device availability, alerts, logs, reports, scheduled tasks, and license capacity.

GoMyid On-Premise device administration console

After installation

Operate devices as a managed environment

Enroll Windows computers, group them by office or responsibility, assign authorized administrators, and use the appropriate remote desktop, file transfer, command, support, inventory, and reporting tools. Page-level administrator scope helps separate responsibilities across operational teams.

Alert rules can monitor offline device conditions, license thresholds, service status, failed administrator logins, and report scheduling failures. Scheduled summary and detailed reports help turn recurring review work into a defined process.

Request Architecture Discussion

Before rollout, confirm

Use this checklist during technical and commercial planning.

Server and database

Capacity, availability, maintenance window, backup, restoration, and responsible team.

Network paths

Branches, VPN, firewall policy, DNS, certificates, and private or internet-facing access decisions.

Administrative model

Account owner, administrators, page scope, groups, support teams, and approval workflow.

Operational readiness

Monitoring, alerts, reports, license review, updates, documentation, and escalation ownership.

Design your GoMyid On-Premise deployment

Share your device count, locations, network requirements, administrator model, and reporting expectations with the GoMyid team.

Contact On-Premise Sales