Operate connected products after they ship

Provision products, observe fleets, respond to incidents, support customers, and govern access from first connection through field operations.

Connect your first device

How Dataplicity connects IoT operations

Business workflows

Build with the API

Diagnose a difficult device

Run a temporary 20-minute Device Check to capture health, network path, clock, and process evidence without installing permanent software.

Run a Device Check

Run IoT as a business

Short stories for internal fleets and connected-product companies - when and why to use Dataplicity across network, hardware, software-age, and support realities.

Explore business workflows

Picture an OEM on Dataplicity

SiloSentry is a fictional grain-bin sensor company used as a worked example of post-shipment ops - illustrative, not a real customer product.

Open the SiloSentry walkthrough

Know the state of every device

Organise inventory with networks, classes, tags, customers, and sites. Use logs, monitors, dashboards, and event history to understand current state.

Explore fleet operations

Support devices without site visits

Move from alerts to logs and monitor context, then use Remote Shell, Wormhole, or resilient file retrieval only when an interactive response is needed. Dataplicity Lens adds structured host inspection once a shell is open.

Choose a remote access method

Detect and act earlier

Monitor HTTP services, DNS, CORS, scheduled work, user journeys, and fleet connectivity. Where incidents and status surfaces are enabled, route through acknowledgement, escalation, resolution, and reviewed status updates.

Follow the response playbook

Operate across the lifecycle

Design device classes, provision securely, hand supported inventory to customers, run guarded fleet jobs, and verify changes through history and monitoring.

Provision deployed products

Give customers trusted visibility

Publish selected service, journey, heartbeat, and incident widgets. Build internal dashboards and use customer modules only within their access boundary.

Design customer visibility

Integrate your own systems

Use scoped organisation API keys and the published Gateway API. Keep provisioning credentials, user identity, and private dashboard endpoints separate.

Manage integration credentials

What you need

You need to	Open
Connect a Linux device and open a shell	Getting started
Decide if Dataplicity is the post-shipment operations layer	After devices ship
Design who can see and change what	Set up roles
Diagnose a difficult device before or after enrolment	Device Check
Integrate from your own systems	Gateway API