Run workflows in your own environment
NodePilot is a self-hosted workflow orchestrator for Windows. Its API, engine and scheduler run as a Windows service, controlled through a browser or desktop app. Remote Windows systems are reached over WinRM. No additional NodePilot agent is required on those targets.
Choose desktop or server
The desktop edition provides a local starting point. A server installation requires a Windows environment and a supported PostgreSQL or SQL Server database. The installation documentation lists version requirements, installation paths and the components involved.
Open code, your own operations
The source code is available under Apache 2.0, without paid feature tiers. You can inspect and modify it. Operating your installation also means managing updates, backups, recovery tests, service accounts and access rights.
Self-hosting does not mean that every configured action works without an external connection. REST calls, email and an optional AI integration use the services you configure. The actual workflow and integration configuration determines those connections.
Try it before introducing it
The browser demo shows the interface with simulated data. For your own installation, Creating a first workflow provides a small functional test. Why NodePilot exists explains the motivation and limits of the project.
Example: An internal daily status report
Run NodePilot on an internal Windows host with your own database. A scheduled workflow uses WinRM to query an approved test server, records the result and reports deviations through your configured email service. Start with a read-only query; service restarts belong in a separately reviewed process.
Limit the service identity to the targets and permissions it needs. Verify WinRM, HTTPS configuration, database backups and recovery before relying on the report in operations. The hardening guide and remote execution configuration explain these requirements.
