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.
Remote shell
| Guide | Description |
|---|---|
| Getting started: open a remote shell | First shell session in minutes. |
| Remote shell guides | sudo, clipboard, htop, background scripts. |
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. |
When to use each method
| Need | Use |
|---|---|
| Quick diagnostics or 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 |
See Trust on someone else's network before production deployment.
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