Skip to content

Remote access #

Reach authorised Linux devices through their agent-initiated Dataplicity route, without configuring a per-device inbound rule or site VPN. Restricted networks may need the documented outbound destinations allowlisted.

Already connected? Choose the access method below. If the device is not yet in Dataplicity, connect it and open the first shell. If a previously connected device is offline, use offline-device diagnosis; no remote-access method can open a new session until the device reconnects.

Who may open a session is a Dataplicity role. What the session can do on Linux is the agent's OS identity. See Shell privileges and Trust on someone else's network.

Current Dataplicity device support workspace with Terminal, Wormhole, Timeline, Diagnostics, and Agent Log tabs
The current device workspace brings remote support and device context together.

Choose a method #

NeedUse
Quick diagnostics or a command-line fixRemote Shell
Structured host inspection in that shellDataplicity Lens
Web dashboard or REST API on the deviceWormhole
Retrieve a file from an intermittent deviceFile retrieval
A graphical desktop on the deviceDevice desktop

Remote shell #

GuideDescription
Getting started: open a remote shellFirst shell session.
Remote shell guidesPrivileges, clipboard, process view, background scripts, and pausing access.

Wormhole #

GuideDescription
Wormhole overviewExpose web services without port forwarding.
Host a websitePublish a web interface from a device.
Securing Wormhole servicesApplication-level security. Required before you expose anything.

Files #

GuideDescription
Resilient file retrievalRequest a file and let connectivity catch up.

If your devices are already online, choose another operating job to add logs, diagnostics, Pulse, or monitoring, or manage the fleet. These do not require a Customer Portal or Product Application. Use expand beyond remote access when you want one decision page covering both operations and optional customer-facing capabilities.