A browser terminal
Open Remote Shell from the device record for interactive Linux diagnosis. Keep the fleet, customer and recent evidence in view.
Explore this capabilityBring your tools to the fleet. Keep access under control.
Use a Network Connector on a Linux host to reach permitted TCP services on your connected devices through stable fleet IPs and private DNS. Keep the client tools your engineers already use, with device and port access controlled from Dataplicity.
- Network Connector is available on all plans, including Free; device allowances and port entitlements still apply.
- Install the connector on a Linux host. The target device needs an online Dataplicity agent and permitted outbound connectivity.
- Access is granted for selected devices and TCP ports. A fleet IP alone does not grant access.
Choose how your team needs to reach the equipment.
A browser terminal, a device web interface and a tool on your own host solve different jobs.
A device web interface
Use Wormhole to reach an HTTP service running on the device through its outbound connection.
Explore this capabilityYour existing client tools
Run the connector on a Linux workstation or server, then use a TCP client to reach an authorised device service through its fleet IP or private DNS name.
From a workstation to the service you need.
Illustrative setup: an engineer needs SSH and a diagnostic service on a tagged group of gateways.
Choose a fleet address range
An administrator selects a suitable fleet IP range that avoids local network conflicts. Device addresses persist across connector enrollment and access-rule changes.
Enroll the Linux host
Install the connector package and register with a short-lived, single-use enrollment key. Give each host its own connector identity so access can be managed and revoked.
Grant the devices and ports
Choose device tags and the TCP ports the connector may reach. Grant the gateway group SSH and the required diagnostic port instead of opening every device service.
Use the tool and review the access
Connect with your normal client using the assigned fleet IP or private DNS name. Review connector activity and remove grants or revoke the connector when the work is finished.
Explore this capabilityDevice identity survives changes in how you connect.
The fleet address belongs to the device within the organisation, rather than to a particular workstation session.
Stable fleet IPs
Authorised connectors can refer to the same device address. Eligibility, online state and port permission still determine whether the service can be reached.
Private DNS
Use device DNS names and readable aliases from the authorised inventory. Private DNS is provided through the connector; it does not publish a device service to the internet.
A searchable inventory
Find devices by name, serial, tags, online status or IP, and inspect which connectors can reach them.
Keep the authority with your team.
Connector identity and policy are managed in the same organisation as your fleet.
Scope each host
Assign device-tag and TCP-port rules to each connector. Dataplicity also enforces the enrolling administrator’s current permissions and the organisation’s device and port allowances.
Change or revoke access
Manage grants centrally, rotate credentials and revoke connector identities. An existing connector cannot grant itself more fleet access.
Keep an access record
Enrollment, credential changes, policy denials and channel authorisation feed the existing Activity and security audit path. Session events are evidence of access, not a recording of every action inside the remote service.
Explore this capabilityReachability is one part of the operating picture.
When many devices disappear together, look at the shared dependency as well as the individual device.
Compare provider performance
ISP reporting groups available connection-quality history by provider and ASN, with latency, health and reporting coverage. Missing samples stay visible as missing evidence.
Monitor the affected group
Use fleet monitors to watch an ISP or site cohort, compare it with devices outside that group, and carry the evidence into an incident.
Explore this capabilityProve one useful connection first.
Use a representative Linux host, device and service before expanding access.
Test the permitted service
Select an address range, enroll a connector and grant one device group and required TCP port. Confirm your client reaches the intended service.
Test the boundary
Confirm an ungranted device or port is denied. Review the activity record, then revoke the test connector and check that it cannot open new access.
Check availability
The connector is available on all plans; reachable devices and ports follow your allowances. ISP connection-quality reporting is a separate capability whose availability depends on your plan.
Explore this capabilityConnect the equipment. Choose the access your team needs.
Start with an online Linux device, then evaluate a connector with a bounded device group and one useful TCP service.