Build, ship and support connected products.
Support equipment in the field. Ship improvements. Give customers their own application.
Keep your Linux and application. Start with the agent.
Remote support workspace · Northstar demo fleet
What do you need to do?
Fix equipment remotely
Open a terminal, inspect logs and check the recovery.
Give customers their own app
Show readings and permitted controls in a branded customer app.
Get hardware and firmware help
Work through circuits, Linux GPIO and product integration with Equidna.
Equidna
Hardware and firmware
Connect and hand over devices
Install the agent, verify the unit and assign its customer.
Catch a shared fleet failure
Compare affected devices and coordinate the response.
Improve devices already shipped
Run a controlled job and inspect each device’s result.
Start with a connection.
Your OS and updater can stay. Add monitoring, software delivery or a customer app when you need them.
Choose your starting point →RAUC image updates require a prepared, qualified image.
Find the fault. Check the recovery.
Follow device history, logs and diagnostics into an authorised support session.
See the remote-support workflow →
Device and platform events · Northstar demo fleet
Your tools. Their application.
Manage the product in your workspace. Give customers their own readings and permitted controls.
Manufacturer workspace
Device definitions · Northstar demo fleet
Customer experience
Customer readings and controls · level-monitor reference
Equidna
Hardware and firmware
Work through circuits, board interfaces and Linux integration.
Pingüino
Technical support
Investigate devices, logs and connectivity.
Nutria
Customer success
Plan adoption and get more from your product.
From the circuit to the customer.
24/7 AI help: Equidna for hardware and firmware, Nutria for customer success, Pingüino for technical support.
Plan and usage limits apply. Shared-room help is read-only.
Let a teammate try your local API.
dataplicity tunnel publish test-api --port 3000Install the Dataplicity CLI and sign in on both computers. Publish your local port, then let your teammate connect by name.
Available on paid plans. Give your teammate access to the tunnel before they connect.
See both sides of the connection →Interactive illustration. Traffic and latency are simulated; no live tunnel is opened. Choose any step.
Your CLI publishes test-api from local port 3000. It maintains its own connection to the relay.
↑ Sending · payload
0.0 B/s · Peak 0.0 B/s
↓ Receiving · payload
0.0 B/s · Peak 0.0 B/s
CLI–relay RTT · heartbeat
8 ms
Concurrent TCP streams
0 active · Window max 0
Ctrl+C stops the CLI · relay RTT is not service latency
See equipment like yours.
Reference product views; configuration and integration are required.