Centralized asset and project view
Controllers, associated projects, applications and versions can be organized and managed from a central platform.
CODESYS · Controller and project management
CODESYS Automation Server
Centralized Device, Project & Lifecycle Management for CODESYS Systems
CODESYS Automation Server provides a centralized operations layer for connected CODESYS controllers and engineering projects. It supports device management, project/application versioning, remote engineering access, controlled rollouts, certificates, users and data analysis while local controllers continue to execute machine control independently.
Controller inventoryProject deploymentRemote monitoringUser rolesEdge Gateway
RoleFleet & project operations
AccessCentralized / browser-based
ConnectivityCODESYS Edge Gateway
Control executionRemains local
Product role
Operations layer for connected CODESYS controllers
CODESYS Automation Server provides a centralized operations layer for connected CODESYS controllers and engineering projects. It supports device management, project/application versioning, remote engineering access, controlled rollouts, certificates, users and data analysis while local controllers continue to execute machine control independently.
Centralized asset and project viewControllers, associated projects, applications and versions can be organized and managed from a central platform.
Controlled remote engineering and rolloutThe platform supports remote access, debugging/maintenance workflows and application rollout with defined permissions and records.
Lifecycle and cybersecurity functionsCertificates, users, auditability, project protection and secure connectivity become part of the controller operations model.
Architecture role
Central management above local machine execution
Define the interfaces and ownership boundaries first; version, licence and target selection should follow the architecture rather than lead it.
01CODESYS controllers
02Secure connectivity / gateway
03Automation Server
04Projects / users / certificates
05Operations / maintenance
Confirm the exact target, product version, device package, protocol role, licence and—where applicable—certified safety scope before release to production.
Engineering scope
Fleet, project, remote-access and lifecycle capabilities
These capabilities define what the CODESYS component contributes to the architecture and what must still be provided by the controller, host platform, network or machine design.
Controlled remote engineering and rollout
The platform supports remote access, debugging/maintenance workflows and application rollout with defined permissions and records.
Lifecycle and cybersecurity functions
Certificates, users, auditability, project protection and secure connectivity become part of the controller operations model.
Technical selection
Connectivity, identity, governance and deployment requirements
Use this table as a requirement-capture guide. The final implementation should be checked against current CODESYS product documentation, Store data, target documentation and—where relevant—certificates and safety manuals.
| Device and project management | Connected devices, projects and applications can be centrally organized, versioned and maintained. |
|---|---|
| Connectivity | The CODESYS Edge Gateway provides the controlled link between local controller networks and the Automation Server architecture. |
| Remote access | Secure centralized access can reduce the need for ad-hoc remote-access mechanisms; permissions and operational governance still need to be defined. |
| Security | Multi-factor authentication, certificate-based TLS communication, auditability, role management and project/application protection are part of the platform capabilities. |
| Deployment model | CODESYS provides cloud-based Automation Server services and has documented on-premises support in its current product roadmap/ecosystem. Confirm the currently orderable deployment for the project. |
| Control independence | Machine operation, restart and safe-state behaviour must remain correct if the management platform or WAN connection is unavailable. |
Project workflow
Secure onboarding and operations workflow
Move from architecture qualification to engineering, commissioning and lifecycle evidence in a controlled sequence.
Define the management scope
Identify controllers, sites, projects, users, certificates and operational responsibilities.
Establish secure connectivity
Design the Edge Gateway, firewall, proxy, identity and remote-access arrangements.
Govern deployment
Configure roles, approvals, versioning, backup and the application-update procedure.
Verify offline behaviour
Confirm that machine control and local safe behaviour are unaffected when the service is unreachable.
Platform context
Application scope for centralized controller operations
Automation Server is appropriate when controller fleets, remote support, project governance or repeatable rollouts justify a centralized operations layer.
Current page
CODESYS Automation Server
CODESYS Automation Server provides a centralized operations layer for connected CODESYS controllers and engineering projects. It supports device management, project/application versioning, remote engineering access, controlled rollouts, certificates, users and data analysis while local controllers continue to execute machine control independently.
View role in the platform →Control executionCODESYS Runtime
CODESYS Runtime is the execution layer that turns a compatible target into a programmable controller. The application is created in the Development System, compiled for the selected target, and executed by CODESYS Control—either already integrated by an OEM or installed as a ready-to-use Control SL SoftPLC on a supported platform.
View role in the platform →Virtual PLCCODESYS Virtual Control SL
CODESYS Virtual Control SL provides a containerized IEC 61131-3 runtime for virtual PLC deployment on supported Linux systems. The engineering workflow remains CODESYS-based, while controller instances, compute resources, networking, I/O access and lifecycle operations are managed on the host platform.
View role in the platform →Documentation & requirement capture
Official CODESYS documentation and project inputs
Use the official product page for current product information, then provide the project-specific details below so the architecture can be reviewed against the actual machine or system.
Official CODESYS Automation Server informationOpen CODESYS ↗Complete CODESYS platform architecturePlatform overview →
Application scopeMachine/process functions, operating modes, cycle-time expectations and whether the project is new design, retrofit or migration.
Target & software baselineController/IPC, CPU architecture, operating system, CODESYS runtime, device package, compiler profile and existing project version.
I/O & communicationLocal/remote I/O, fieldbuses, Industrial Ethernet, OPC UA, MQTT, controller-to-controller links and required protocol roles.
HMI & user accessDisplay hardware, browser clients, independent HMI requirements, alarms, trends, recipes, user roles and remote-service policy.
Motion & functional safetyAxis count, drives, kinematics, CNC/robotics requirements, safe I/O, safe communication and required PL/SIL where relevant.
Deployment & lifecycleController quantity, sites, licensing, backups, certificates, update process, rollback expectations and maintenance ownership.