Appearance
Getting started
Choose the outcome you need:
| Outcome | Start here |
|---|---|
| Reach and support one Linux device | Connect your first device |
| Manage Home Assistant on the free plan | Manage Home Assistant with Dataplicity |
| Prove a device through your first customer's branded portal | Build your first connected product |
| Add portal and operations capabilities to devices already online | Expand beyond remote access |
| Understand the architecture and boundaries first | How Dataplicity fits |
The first path ends with engineering access. The connected-product path continues through Device Class, product data, customer UI, customer organisation, placement, and a portal login. Use that second outcome as the activation test for a product you intend to sell.
What you need
| You need to | Open |
|---|---|
| Sign in or recover an account | Sign in or reset a password |
| Install the agent on one Linux device | Quick start |
| Understand what the field agent installs and runs | Dataplicity agent |
| Confirm the device can reach the internet | Internet connection |
| Put the agent on a factory image | Install on many devices |
| Allowlist outbound traffic on a restricted network | Firewall requirements |
| See whether this Linux image is a supported starting point | Supported systems |
Install and first connection
| Guide | Description |
|---|---|
| Quick start | Install the agent, confirm the device is online, and open a remote shell. |
| Manage Home Assistant with Dataplicity | How people run one free-plan HA host: shell when it breaks, Wormhole when away, plus one monitor, task, and dashboard. |
| Dataplicity agent | On-device architecture, requirements, layout, and health checks. |
| Internet connection | Ethernet and WiFi setup. Skip this if the device already has a working route. |
| Supported systems | Linux agent requirements, image validation, and the agent or CLI distinction. |
| Command-line tools | Install the workstation CLI or use the in-app Web CLI. |
| Firewall requirements | Outbound HTTPS URLs and NTP requirements for restricted networks. |
| Agent lifecycle | Upgrade, uninstall, and data left on the device. |
| Data consumption | Baseline agent traffic when idle. |
| Improving reliability | Network reconnect handling on embedded devices. |
Before you install
- Device Check - free Linux diagnostics without an account (guide)
After your first device is online
- Turn your hardware into a customer SaaS product - build the product model, live customer page, branded portal, and repeatable fulfilment path
- Expand beyond remote access - add evidence, monitors, product UI, Customer Portal, and fleet operations without reinstalling the device
- Core concepts - devices, fleets, logs, and monitors
- Set up roles - who else may use this organisation
- Remote access - shell, desktop, and web service tunnels
- Production rollout - prepare devices for customer networks