One controller is easy. Twenty, in four buildings, from four vendors is the real job. The CODESYS Automation Server registers every device, watches their health from one browser dashboard, and pushes application updates over the air — even to a device that's offline right now. Deploy a new app to the fleet below and watch it roll out.
Four CODESYS targets from four vendors are registered to one Automation Server. Each reports online status, its running app version and a little health. Hit Deploy v1.3.0 and the server pushes the new boot application to every device — the online ones update with a progress roll, and the offline Eaton is queued to update the moment it reconnects.
| Device | Status | App version | Deploy | Health |
|---|
The Automation Server keeps the boot application and source for every device, so a rollout is one action instead of twenty USB sticks. An offline device doesn't miss out — the update is queued and applied on reconnect. Because it's pure CODESYS, the same dashboard manages a WAGO, a Raspberry Pi, a Festo and an Eaton side by side — the runtime is the common denominator, not the brand.
☁️ Central registry. Every controller enrols once and appears in one browser console — no VPN-hopping to each panel. Group devices by line, site or customer.
📦 OTA application deployment. Push a tested boot application to one device or a whole group, scheduled or now, with version history and rollback — the fix reaches the whole fleet in minutes.
💚 Monitoring & alerts. Online/offline state, runtime metrics and trends, with notifications when a device drops or a value crosses a threshold — the operations view your engineering tools never had.
🔐 Secure by design. Devices connect outbound to the server over TLS — no inbound ports to open — with user roles and audit logging. It's an optional add-on to the runtime you already ship.
This is the layer above the IDE: the Development System builds and tests; the Automation Server operates what you shipped. It turns a pile of independent PLCs into a managed estate — the same leap from "log into each box" to "manage the fleet" that DevOps brought to servers.
You deploy a new app version to the fleet, but one controller is powered down for maintenance. What does the Automation Server do with it?