ForumGet started

Choose the access path for the service you need.

Use browser terminal for a managed Linux device, Wormhole for its web service, Network Connector for ordinary TCP clients against granted devices, or named CLI development tunnels for a private bench service. Each has a different target, permission and connection lifecycle.

Find your starting point

Get the install command by email. Remote access is free on one device. Pricing

Dataplicity device workspace with SiloSentry gateway sessions, read-only device checks, Pinguïno assessment and a working terminal
  • Reach internet-connected devices even behind firewalls or private networks.
  • Correlate telemetry, logs, alerts, and incidents in a single timeline.
  • Open remote shell sessions with role-based access and an access-event audit history.
  • Keep on-call response and customer updates in one control plane.

What the connection needs

Install the agent on a supported Linux device you can access. Live remote access begins when the agent is online and can reach Dataplicity. Outbound network policies still apply.

Installed Linux agent
Required
Outbound access to Dataplicity
Required
Inbound SSH port
Not needed
Customer VPN
Not needed
Static public IP
Not needed

Connect from the device

The agent makes the outbound connection, including from behind NAT or a cellular network when policy permits it.

Use the browser

Select an online device and open its remote terminal with the appropriate account access.

Review access events

Session opens are recorded. Terminal contents and keystrokes are not recorded.

Which access path should we use?

Managed-device paths need an online agent and permitted outbound traffic. Development services do not require device enrolment.

Browser terminal and SSH tooling

For interactive diagnosis of managed equipment. Select an online device with the required account access. Review support evidence before intervening.

Remote Shell guide

Wormhole

For a web service on a managed device. Configure the supported HTTP exposure and access settings; keep application authentication and exposed content deliberate.

Wormhole

Network Connector

For normal client tools on a supported Linux host. Use stable fleet IPs/private DNS with explicit device-tag and TCP-port grants; an address does not authorise access.

Connector and device access policy

Named development tunnels

For private temporary TCP services between authorised CLIs in a paying organisation. No device-agent enrolment, public webhook URL or UDP network.

Share a bench service

Remote Desktop for operational computers

Open a Windows, Linux or macOS computer’s screen for an interactive support session. Free for up to five registered computers; every paid plan includes unlimited computers, users and sessions at no additional Remote Desktop charge.

Remote Desktop

Screen access or active device management?

Choose by what you need to do. A Remote Desktop computer and an agent-managed Linux device have separate allowances.

Remote Desktop: work on the screen

See and operate the installed desktop application during a session. Registering a computer for Remote Desktop does not enrol it in Linux device monitoring, log collection or fleet management.

Explore Remote Desktop

Linux agent: monitor and manage the device

Use a remote terminal and live diagnostics, collect configured logs, and monitor the device without keeping a desktop session open. Works on headless Linux. Free includes one managed device, one monitor, one scheduled task and 24-hour log retention; paid plans expand capacity and capabilities.

Compare exact plan inclusions

Telemetry and logs

Metrics and syslog arrive over the same outbound connection.

Ops dashboard

Fleet health metrics and per-device drill-down.

Log search

Tail and search syslog across devices and servers.

Event history

Deploys, restarts, and config changes in one timeline.

Alerts and incidents

Route alerts and document incidents without leaving the ops view.

Alert rules

Thresholds, heartbeats, and expression-based alerts.

On-call escalation

Route alerts to the right rota and log the response.

Incident management

Attach notes and resolution steps to each incident.

Remote access

Open a secure shell without poking holes in the network.

  • Outbound-only access keeps customer infrastructure closed.
  • Session opens and device actions are logged with device and incident context.
  • Access respects org roles and cohort scopes.

Remote shell

Open secure shells on devices through Dataplicity.

Saved commands

Run repeatable commands on target cohorts.

Access record

Review remote session opens as access events. Terminal contents and keystrokes are not recorded.

The connection is one part of a field investigation.

History, comparison, authorised intervention and fresh outcome evidence complete the job.

Diagnose and resolve the customer fault

Keep Linux, your application and updater; configure evidence and choose the permitted access path.

Remote fault resolution

Try the workflow on a device you can reach.

Connect one Linux device free to try remote terminal, live diagnostics and configured monitoring. Compare plans for device capacity, log retention, Pulse and fleet workflows.

Find your starting point