Core concepts

Dataplicity is a post-shipment operations layer for Linux IoT devices. These pages explain the building blocks and how they help teams manage devices after they leave the lab.

Product overview

Page	Description
What Dataplicity is for	Operational problems Dataplicity solves after devices ship.
How it works	Agent, IoT Router, and outbound connection architecture.
Dataplicity vs generic tools	How Dataplicity relates to log platforms, monitors, VPNs, and spreadsheets.
If you used Dataplicity for remote shell	What's new beyond remote terminal access.

Device and fleet context

Page	Description
Devices	Individual Linux devices in your account.
Fleets, groups, and tags	Organising devices at scale.
Customers, sites, and ownership	Mapping devices to customers and deployment locations.

Access and connectivity

Page	Description
Remote access	Shell, desktop, SSH, and file transfer options.
Wormhole	Outbound tunnels to web services on devices.
Remote access	Remote shell, Wormhole, and resilient files.

Operations

Page	Description
Logs	Collecting and viewing device output.
Configure logs in the dashboard	Add sources, search, and filter.
Monitors	Service, journey, heartbeat, and connectivity checks.
Create monitors and alerts	Health checks and notifications.
Alerts	Notifications when something needs attention.
Scheduled tasks	Running scripts across devices on a schedule.
Create scheduled tasks	Dashboard walkthrough.
Status pages	Customer-facing device or service visibility.

Teams and governance

Page	Description
Users, teams, roles, and permissions	Who can access what.
Audit trails	History of operational access and actions.
Security model	Outbound connections, authentication, and production security.
Production deployment	Moving from prototype to managed fleet.

Comparisons

Page	Description
Port forwarding compared	Dataplicity vs inbound port forwarding.
Dynamic DNS compared	Dataplicity vs DDNS for portable devices.