NodePilot
ProjectUse cases
Documentation
DEEN

Evaluate an open-source alternative to System Center Orchestrator

Evaluate NodePilot for SCOrch migration: import runbooks, review import reports and test Windows workflows in your own environment.

Start with your existing runbooks

Replacing System Center Orchestrator involves more than copying visible activities. Connections, conditions, Published Data and execution identities also determine a runbook's behaviour. NodePilot imports SCOrch exports in .ois_export format to use existing automation as a starting point.

What the import does and what needs review

Supported activities are mapped to NodePilot activities. Unsupported activities remain visible as disabled placeholders. An import report records areas that need attention. Encrypted credentials are not reconstructed, and imported workflows start out disabled.

The article Importing SCOrch runbooks and reviewing the result explains the process and its limits. NodePilot does not promise to replace every System Center Orchestrator integration or behaviour.

Evaluate a migration in small steps

  1. Select a representative runbook and define its expected results.
  2. Import the export and review every warning in the import report.
  3. Check target machines, service accounts, data references and schedules.
  4. Compare successful and failing cases with the previous behaviour in a test environment.
  5. Explicitly enable the reviewed workflow only after those checks.

Your own infrastructure and an open licence

NodePilot runs in your Windows environment and is released under Apache 2.0. Review the self-hosting requirements and installation guide during evaluation. An open-source licence does not include a support contract or an operational guarantee.

Example: Migrate a daily status check

Start with a runbook that reads a service state on a test machine and passes the result on. Record its expected output and failure behaviour. Import the export, replace placeholders where needed and test both an existing and a deliberately invalid service name. Compare output, branching and logs before enabling the schedule.

Review areaSCOrch starting pointCheck in NodePilot
ActivitiesRunbook and Integration PacksMappings in the import report; replace placeholders
Data flowPublished Data and link conditionsVariable references and branches with real test values
IdentityExecution account and stored credentialsReconfigure credentials and verify target access
ScheduleExisting triggersReview triggers; imported workflows start disabled
NodePilot LiveOps view for monitoring workflow executions
LiveOps helps inspect execution. This screenshot illustrates the interface, not a documented migration test.

SCOrch import, activity mapping and limitations · Explore execution and troubleshooting in the browser demo.

INSTALL NODEPILOT

Where should NodePilot run?

Try it on your own machine or run it as a service in your environment.

On my Windows PCDesktop app for Windows 11 x64. Database and runtime included.Go to downloads On a Windows ServerInstalled as a Windows service. Requirements and setup are covered in the docs.Installation guide
Build it yourself? Source code on GitHub
Free · Open source · Apache 2.0
ORIGINAL WEB UI
Original-Screenshot · Workflow DesignerOpen at full size Source file on GitHub