Docs

Open a remote Linux terminal in your browser.

Reach an online device through its outbound Dataplicity agent connection. No inbound SSH port or customer VPN is needed. The device must be able to reach Dataplicity under the customer’s outbound network policy.

Get terminal commandFind your starting point
Dataplicity terminal cockpit with fleet device list and a live device shell session
  • Open a shell from the device record.
  • Use role-based access for your team.
  • Session opens are recorded; terminal contents and keystrokes are not.

What the connection needs

Install the agent on a supported Linux device you can access. Live remote access begins when the agent is online and can reach Dataplicity. Outbound network policies still apply.

Installed Linux agent
Required
Outbound access to Dataplicity
Required
Inbound SSH port
Not needed
Customer VPN
Not needed
Static public IP
Not needed

Connect from the device

The agent makes the outbound connection, including from behind NAT or a cellular network when policy permits it.

Use the browser

Select an online device and open its remote terminal with the appropriate account access.

Review access events

Session opens are recorded. Terminal contents and keystrokes are not recorded.

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

Review access events. Terminal contents and keystrokes are not recorded.

Audit

Access record

See who opened access and which device actions they invoked.

Incidents

Incident notes

Record your investigation and resolution steps in incident notes.

Security

Access review

Review terminal usage in security activity.