DevTools
CI/CD is hard -especially for PLCs. Manual builds in the IDE don’t scale. There’s no standard toolchain like in classic software, builds are hard to reproduce, and “works on my machine” turns into production risk. Teams need automated builds, tests, and docs without running their own Jenkins farms or fighting TwinCAT’s tooling.
Zeugwerk offers CI/CD tools for TwinCAT so you can get there: build and test in the cloud, generate documentation from source, and create type-safe bindings for C# or C++. zkbuild-action and zkdoc-action are available for all major Git hosts (GitHub, GitLab, Bitbucket). You can also license our tools for on-premises and private use.
| Tool | What it does | How you use it |
|---|---|---|
| zkbuild | Build PLCs and run unit tests in the cloud. Reproducible artifacts, no build servers. | zkbuild-action (GitHub, GitLab, Bitbucket) or commercial/on-prem. |
| zkdoc | Generate API docs from PLC source and publish (e.g. GitHub Pages). | zkdoc-action (GitHub, GitLab, Bitbucket) or zkdoc (licensed/on-prem). Syntax reference for writing comments. |
| zkbindings | Generate type-safe C# or C++ bindings from your PLC for external apps. | GitHub Action or licensed/on-prem. |
Free tiers for public repos (e.g. 30 builds/month). For private repos, higher volume, or on-premises licensing, see pricing or contact us.
When you use the framework to implement your own applications and libraries, we recommend following Coding Guidelines (naming, structure, style) and IDE settings (TwinCAT options) so your code stays consistent with the framework and works well with our tooling and CI.