A live shell on any endpoint, without touching the network
Open PowerShell, bash, or zsh on any managed device from the console. Sessions ride the agent’s outbound channel, so there is no VPN, no port forwarding, and every command lands in the audit log.
Ad-hoc SSH and slow VPNs stall every diagnosis
When an endpoint misbehaves, the technician loses minutes just getting to a prompt.
VPN detours
Reaching a laptop at home means VPN credentials, RDP hops, or asking the user to read out commands.
Open inbound ports
SSH or WinRM exposed for support becomes a permanent attack surface that must be watched and patched.
No record of what ran
A technician fixes a box over SSH and the change is invisible to the rest of the team and to auditors.
Key and password sprawl
Shared SSH keys and local admin passwords float around inboxes and wikis with no central control.
Shell power with enterprise controls
The speed of SSH, with the oversight SSH never had.
Live shell on any endpoint
Open an interactive PowerShell, bash, or zsh session on Windows, macOS, and Linux endpoints straight from the console.
No VPN or inbound rules
The agent dials out to your Center, so shells work behind NAT and on remote laptops without opening any inbound port.
Script library handoff
Run a saved script on one device or a whole group, then drop into a live shell only when the output needs a closer look.
Full command audit trail
Every session is logged with technician, device, timestamps, and executed commands. Nothing runs off the record.
Role-based shell access
Grant shell rights per device group. Read-only diagnostics roles can query without ever getting a prompt that changes state.
Works air-gapped
Sessions ride the same on-premises relay as remote desktop. In isolated networks the shell works over LAN without internet.
Every command stays under control and on the record
A remote shell is only acceptable when you can answer who opened it and what ran inside. Moftgate records it all.
- ✓Shell sessions are established over TLS through your own relay; commands never transit a third-party cloud.
- ✓Role-based access decides who can open a shell on which device group.
- ✓Every command, its output summary, and the session duration are written to the audit log.
- ✓Destructive patterns can require a second approval before the session reaches the device.
- ✓Idle sessions close automatically and every open shell is visible on the Remote Sessions page.
From endpoint to prompt in four steps
Find the device
Search by hostname, user, or group in the endpoint list and open the device card.
Open the shell
Start a terminal session with one click. The right shell launches per OS: PowerShell, bash, or zsh.
Diagnose and fix
Inspect services, logs, and processes live, then apply the fix without leaving the console.
Close with a record
The session, commands, and duration are archived to the audit log automatically.
Remote Terminal: frequently asked questions
An audited prompt on every endpoint
Remote terminal is already inside the agent you deploy for Endpoint Management. The first 200 endpoints are free for the first year.