One script checks services, another copies files. A third queries a database. Each of them works on its own. But as soon as these tasks depend on each other, knowing where the files are is no longer enough.
Which step ran? What output did it produce? Why did the next step not start? And what has to change without affecting the rest of the workflow?
The work between the scripts
This is where NodePilot comes in. PowerShell remains the tool for the actual work on the systems. The workflow describes how the individual steps fit together: with conditions, error paths and parallel branches.
Working scripts stay as they are. They are simply embedded in a workflow that you can design, run and trace afterwards.
One workspace instead of separate views
NodePilot combines the visual designer with execution history, debugging and Live Ops. Target systems are reached over WinRM; they need no additional NodePilot agent. The application itself runs in your own environment.
Existing automation should not get lost either. That is why importing SCOrch runbooks is part of the project. An import does not replace a review, but it takes the existing structure as the starting point – instead of an empty canvas.
Open, limits included
NodePilot is released under Apache 2.0. You can read the source code, run it yourself and change it. There is no split into a free interface and product features locked behind a paywall.
That said, it is no substitute for a support contract. With an open-source project, careful evaluation, tests with your own workflows and a look at the documentation are part of the deal.
Technical background: NodePilot README. The documentation covers setup and operations.