Module - Linux remote terminal

Secure remote access without VPN or inbound SSH.

Open a browser-based shell from the device record over its outbound Dataplicity connection—no static IP, DynDNS, port forwarding, or customer firewall exception required.

  • Remote shell access stays inside Dataplicity.
  • Commands are tied to the device record.
  • Audit history captures remote actions.
Remote shellsecure access
$ tail -n 50 /var/log/syslog12:05:42 alert routed to robotics@device online - 2ms latency

Remote terminal requirements

Install the Dataplicity agent on an internet-connected Linux device. The remote terminal uses its outbound connection, so you do not need an inbound port, VPN, static IP, DynDNS, or on-site network access.

Port forwarding
VPN
Static IPs
Edge device
Internet access
DynDNS
Firewall exceptions
On-site visits

Works anywhere

If the device can reach the internet, you can reach it too, even behind firewalls or private networks.

Easy access via browser

Log in, pick a device, and open the remote terminal or web UI right in your browser.

Simple and secure

Connections are outbound-only and encrypted, so you don't need VPN clients or firewall changes.

Secure access

Open shells from the same UI used for alerts and inventory.

Shell

Remote access

Launch a secure shell over the outbound connection.

Context

Device metadata

Stay in context with inventory and logs.

Policy

Access controls

Restrict access by role and cohort.

Audit history

Remote actions are tracked and reviewable.

Audit

Command history

See who ran which commands on each device.

Incidents

Incident notes

Attach terminal actions to incident timelines.

Security

Access review

Review terminal usage in security activity.