Appearance
If you have used Dataplicity for remote shell
If you know Dataplicity as a way to open a terminal on your Raspberry Pi without port forwarding, that still works exactly as before. Remote shell remains a core feature.
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 with no port forwarding
- Works behind NAT and firewalls via outbound connections
- Wormhole for exposing web services on devices
- resilient file retrieval for intermittently connected devices
Your existing devices and install commands continue to work.
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 | Record who accessed which device and when |
| Customer visibility | Status pages for end customers where appropriate |
| Commercial team use | Teams, roles, permissions, and SSO for larger organisations |
Where to start
If you only need remote shell, nothing changes - keep using the dashboard as you always have.
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