Appearance
Beyond remote shell
If you know Dataplicity as a way to open a terminal on a Raspberry Pi or another Linux device without inbound port forwarding, Remote Shell remains a core feature. Existing devices continue to use their supported agent and account configuration.
The product has expanded to cover more of what teams need after devices ship.
What has not changed
- One-line agent install on Linux devices
- Browser-based Remote Shell without inbound port forwarding
- Agent-initiated connections for devices behind NAT, subject to permitted outbound network access
- Wormhole for exposing web services on devices
- Resilient file retrieval for intermittently connected devices
Use the install command and compatibility guidance currently shown for your organisation when adding or rebuilding a device.
What is new
| Area | What it gives you |
|---|---|
| Fleet visibility | See all devices, online status, and properties in one dashboard |
| Logs | Collect and view device output without SSHing in to tail files |
| Monitors | Watch services, journeys, scheduled work, and connectivity |
| Scheduled tasks | Run maintenance scripts across one device or a fleet |
| Support workflows | Give support teams access without sharing passwords |
| Audit trails | Review supported platform access events where recorded; coverage, fields, and retention depend on the event type and organisation configuration |
| Customer visibility | Customer-facing status pages where status surfaces are enabled for the organisation |
| Commercial team use | Teams, roles, permissions, and SAML SSO or SCIM where enabled for the organisation |
Where to start
If you only need Remote Shell, keep using the supported dashboard and agent path for your devices.
For structured host inspection during a shell session - processes, services, logs, storage, networking, and hardware - see Dataplicity Lens. Lens is an open-source WildFoundry toolkit that complements Dataplicity; it is not part of the cloud service.
If you are managing more than a handful of devices, or supporting customer-deployed hardware:
- Add tags to organise your fleet
- Set up a team instead of sharing login credentials
- Review the security model before production deployment
- Read what Dataplicity is for to see the full operational picture
- After devices ship - the narrative from remote access to post-shipment operations
Continue with the operating connected products series for identity, stack fit, incident response, and production trust.