Docs

Reach your Linux devices. Resolve problems remotely.

Reach equipment behind customer networks, investigate faults and manage your fleet. Keep your hardware and software. Add a branded customer application when you need one.

See what your team and customers get
Dataplicity device list beside a selected device and its remote Linux terminal, shown with demo data

Your fleet and a remote Linux terminal in one workspace. Shown with demo data.

Connect one device. Open its terminal.

  1. Keep your product

    Use the Linux device and application you already have, from a prototype to equipment in the field.

  2. Install the agent

    Run the install command on a device you can reach. The agent runs alongside your existing software.

  3. Open Dataplicity

    Once the device connects, open its terminal in your browser and try remote access.

The agent connects outbound. No inbound ports or customer VPN needed; your network must allow the connection.

Not ready to install? Try Device Check, free with no account

Your team needs control. Your customers may need an application.

Operate your Linux devices, build a customer application, or do both.

For your team

Operate your Linux devices

Reach devices, spot unexpected changes and investigate faults with logs and diagnostics.

Use Dataplicity for your engineering and support team. Keep your existing customer application.

Explore remote access & fleet operations
Dataplicity terminal cockpit with fleet device list and a live device shell session

Dataplicity fleet workspace: device inventory and a live Linux terminal.

For your customers

Give customers an application of their own

Let customers see their equipment, check readings and use permitted controls in your brand.

Your team connects the device data and controls. Add schedules, service requests or other workflows as your product needs them.

Explore customer portals & applications
Silo level monitor showing 24 hours of readings declining to 18.5 cubic metres, with a low-level warning and threshold of 25

Example customer application: silo levels, reading history and device controls.

Use either independently, or combine them around the same connected devices.

Keep your product. Add the capabilities it needs.

Start with the problem you have today. Operate an existing fleet, release software, keep essential work local or build a customer application. You do not need to adopt everything.

Reach and support devices

Reach Linux devices behind customer networks. Investigate with Pulse, diagnostics and collected logs without replacing the application you already run.

Manage releases when you want to

Fleet operations works with the software and updater you already have. If useful, add managed application releases or RAUC fleet rollouts later.

Keep essential work local

Use explicit Edge execution, selected local data and bounded buffering for products that must tolerate unreliable connectivity.

Give customers an application

Provide scoped device views, records, controls and workflows in your brand while keeping engineering tools with your team.

See what you keep and what Dataplicity suppliesCompare platforms and adoption paths

One device looks wrong. Follow it through to the result.

Keep the device, site and operating evidence together as you investigate and act.

Illustrative investigation, not a measured customer result.

Gateway-14North site · 12 comparable gateways · Online

  1. Spot the change

    Pulse flags a gateway whose disk use and installed packages differ from similar devices. Decide whether the difference needs investigation.

    Finding: disk 91% full; packages differ

  2. Inspect the logs

    Open the collected logs for that device and time. In this example, repeated retries are filling a service log.

    Evidence: retries and a growing log file

  3. Reach the device

    Open its remote terminal. Your engineer checks the service and corrects the configuration causing the retries.

    Action: check and correct the service

  4. Check the result

    Review fresh logs and readings. Confirm retries have stopped and disk use is stable before treating the problem as resolved.

    Check: fresh readings; no further retries

If you add a customer application, customers can see readings from this same equipment. Your engineers keep the diagnostics and remote access tools.

Explore fleet operations

One device is enough to try remote access. To evaluate Pulse, connect comparable devices in a Device Class (a group of the same device type) on a paid plan and allow evidence to accumulate.

Start where your product is.

Connect a prototype, prepare your first batch, or add Dataplicity through the installation or update process you already use in the field.

Find your starting point
Explore operating capabilitiesFleet health, logs, remote access, jobs and incident handling.Plan a customer applicationSee what your team builds and what Dataplicity provides.Browse product walkthroughsWorked examples, from Linux fleet support to customer workflows.

Try it on a device you can reach.

Prove remote access on one device, then choose the operating capabilities your team needs.