IoT Edge Device Management Software

Industrial IoT Device Management Platform – Built for Scale, Reliability, and Remote Control

Daployi is a comprehensive industrial IoT device management platform that provides a centralised control plane to securely deploy, monitor, and maintain Docker-based hardware at any scale.

Get Started Contact Us
Managing edge devices in industrial environments – factories, power plants, mines, remote monitoring stations – introduces a different class of infrastructure challenge. Devices are distributed across locations that are difficult or impossible to physically access. Networks can be unstable. Downtime is costly. Manual device-by-device management simply does not scale.
 
Daployi is an industrial IoT device management platform designed to solve exactly these problems. It provides a centralised control plane for deploying, monitoring, and maintaining Docker-based edge hardware at any scale – from a handful of gateways to tens of thousands of remote sensors – without requiring physical access to individual devices.
Industrial IoT Device Management at Scale

The Core Challenge: Fleet Scale and Maximum Uptime

Industrial IoT operators face a specific and difficult trade-off: the more devices you deploy, the more complex maintenance becomes – but the less tolerance you have for downtime or inconsistency. A configuration error that would be a minor inconvenience on a single server can cascade across an entire sensor network if it is not caught and corrected quickly.
 
Daployi addresses this by shifting the operational model from reactive, device-by-device intervention to proactive, fleet-wide automation and visibility.

Golden Templates: Fully Automated Device Provisioning

In industrial deployments, getting a new device from bare hardware to fully operational is one of the most time-consuming and error-prone steps in the process. Daployi’s golden template capability eliminates this problem entirely.

A golden template is a single, comprehensive deployment template that handles the complete setup of a device from scratch. It executes setup scripts before any containerised services even begin to run — automatically creating required directory structures for data streams, building log folders, assigning security certificates, mounting drives, and configuring any host-level prerequisites.

When a new device comes online and installs the Daployi agent with a single command, running the golden template handles everything else automatically. A new device can go from bare hardware to fully configured and operational with minimal manual intervention – regardless of whether it is the first device in a fleet or the ten-thousandth.

Daployi · Device provisioning
Golden templates
From bare hardware to fully operational — in a single command, at any fleet scale.
Bare hardware
Linux + Docker
Single command
Installs agent
Run golden template
One template, all setup
Operational
Ready to run
What gets handled — automatically
Directory structures
Builds folders for data streams and logs.
Security certificates
Assigns credentials at provision time.
Drive mounting
Mounts storage before containers start.
Host prerequisites
Configures OS-level dependencies.
1template
Handles complete device setup end-to-end.
1command
Installs the Daployi agent on bare hardware.
10,000+devices
Same process — first device or ten-thousandth.

Host-Level Access: Bypassing Broken Containers

One of the most critical limitations of traditional container management tools in industrial environments is that they stop working when the container stops working. If an application bug causes a container to crash, many orchestration tools leave administrators completely locked out of the device.
 
Daployi solves this by providing direct access to the raw host operating system – not just the container layer. Through the in-browser terminal and file browser, engineers can bypass a broken container entirely, access the host OS directly, troubleshoot the root cause, and restore service without needing to physically reach the device. In remote industrial environments, this capability alone can be the difference between a 10-minute fix and a multi-day site visit.
Daployi · Remote troubleshooting
Host-level access
Bypass broken containers. Reach the host OS directly. Restore service without a site visit.
Traditional container tools
Engineer attempts access
Container layer
Crashed — access blocked
Host OS
Unreachable
Result: physical site visit required.
With Daployi
Engineer in browser
Container layer
Crashed — bypassed
bypass
Host OS
Direct access — terminal & files
Result: root cause fixed remotely.
What host-level access enables
In-browser terminal
Shell access without SSH or VPN.
File browser
Navigate the host filesystem directly.
Root-cause diagnostics
Inspect logs and processes on the host.
Remote restoration
Restart services without a site visit.
10minutes
Typical remote fix time via host access.
0site visits
No travel to remote industrial sites.
2layers
Container and host — both reachable.

The Daployi Tunnel: Secure Remote Access Without Network Expertise

Industrial teams often include field technicians who are experts in their domain – but not necessarily in network engineering. Traditional remote access tools require understanding of firewall rules, port forwarding, and VPN configurations that field staff simply should not need to manage.

Daployi’s secure Tunnel feature solves this directly:

Pre-configured port mappings — Administrators define specific port access rules within a template, so the configuration travels with the device.

No network expertise required — Field staff access critical TCP/UDP ports or PLC programming interfaces instantly, without understanding firewall rules or port forwarding.

Granular per-device security — Administrators can toggle specific port access rules on or off on a strict per-device basis, preventing unauthorised access.

Cross-platform desktop applications – The Tunnel operates via dedicated apps for Windows, Mac, and Linux.

Container Management Platform Daployi Variable Edits

Advanced Script Triggers for Automated Maintenance

Industrial environments demand maintenance workflows that are reliable, repeatable, and safe. Daployi’s advanced script trigger system gives engineering teams precise control over when and how scripts execute across the fleet:

Run Once

Ideal for initial device setup, such as creating directory trees or mounting permanent drives.

Run at Startup

Useful for checking system states after a hardware reboot, such as verifying that a USB serial device mount point has not changed unexpectedly.

Run at Interval

Perfect for automated maintenance, such as checking DNS resolution every hour and automatically restarting the networking service if it drops.

Manual Run

Reserved for tasks that carry risk if fully automated, such as safely clearing system logs or forcing a batch data upload.

Scripts can be parameterised with global variables, allowing field operators to execute complex maintenance tasks – such as data recovery with a specific date range – through a simple form interface, without needing to understand the underlying commands or access individual devices directly.

Fleet-Wide Remediation: Resolving Issues Across Thousands of Devices at Once

When the same issue affects multiple devices simultaneously – a common scenario in industrial IoT where devices share firmware, configurations, or network conditions – Daployi’s batch execution capability means you can select all affected devices, run a remediation script or deploy a corrected template, and resolve the issue across all of them in a single action. What would otherwise require logging into each device individually becomes a task that takes seconds, regardless of fleet size.

Real-Time Monitoring and Proactive Alerting

Daployi provides live CPU, memory, disk, and network telemetry for every registered device, along with uptime monitoring and a process viewer.

Customisable alerts for device state changes, container failures, and resource threshold breaches are delivered directly to Slack, Discord, Google Chat, or any webhook endpoint – so engineering teams are notified the moment something goes wrong, before it escalates.

Secure Credential Handling for Edge Hardware

In industrial environments, edge devices can be physically accessible to third parties or even stolen. Daployi’s memory-based credential system ensures that container registry credentials are never written to device storage. Credentials are encrypted on the Daployi server, passed to the device strictly in-memory during deployment, and flushed immediately after the image pull completes. Even if a device is physically compromised, your code repositories remain secure.

Connectivity: Designed for Unstable and Cellular Networks

The Daployi agent initiates outbound connections to the server – devices do not require inbound ports to be open and work through standard network connections including cellular SIM cards. Deployments and script executions can be queued and applied when connectivity is restored, making Daployi well suited to remote environments where network reliability cannot be guaranteed.

Supported Hardware

Daployi works with any Linux-based host running Docker or Podman, covering a wide range of industrial hardware – from standard industrial gateways and IIoT controllers to Raspberry Pi-based edge nodes and remote monitoring hardware. If the device runs Linux and a supported container runtime, it can be managed through Daployi.