Appearance
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.
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.
Choose a method
| Need | Use |
|---|---|
| Quick diagnostics or a command-line fix | Remote Shell |
| Structured host inspection in that shell | Dataplicity Lens |
| Web dashboard or REST API on the device | Wormhole |
| Retrieve a file from an intermittent device | File retrieval |
| A graphical desktop on the device | Device desktop |
Remote shell
| Guide | Description |
|---|---|
| Getting started: open a remote shell | First shell session. |
| Remote shell guides | Privileges, clipboard, process view, background scripts, and pausing access. |
Wormhole
| Guide | Description |
|---|---|
| Wormhole overview | Expose web services without port forwarding. |
| Host a website | Publish a web interface from a device. |
| Securing Wormhole services | Application-level security. Required before you expose anything. |
Files
| Guide | Description |
|---|---|
| Resilient file retrieval | Request a file and let connectivity catch up. |
If you first used Dataplicity as a Raspberry Pi terminal, read Beyond remote shell for the path into fleet and support operations.
Related
- Dataplicity Lens - open-source host inspection during Remote Shell sessions
- SiloSentry - fictional OEM walkthrough where terminal and Wormhole sit on the same device record as ops (illustrative)
- Beyond remote shell
- What Dataplicity is for