NSSM vs WinSW

NSSM is a Windows service helper that runs an application as a service, watches its process, and responds when it exits. A graphical interface installs or removes services, while command-line options support scripted configuration. On exit, NSSM can restart the application, ignore the event, terminate itself, or exit uncleanly so Windows recovery actions can run. It records its own progress in the Windows system Event Log and can redirect the monitored program’s input and output. Output files can rotate at a configurable size, including while the program continues running. Administrators can set process priority and CPU affinity, and start, stop, or query services. NSSM provides 32-bit and 64-bit binaries and says it should work on Windows 2000 or later. It is public domain, with source usable for any purpose. The site lists version 2.24 from 2014-08-31 as latest, plus a 2017 prerelease. Administrator access is required; documented bugs affect newer startup, XP, and large log rotation.

WinSW is a free, open-source Windows service wrapper licensed under MIT. It hosts any executable as a Windows service, with behavior defined in a required XML configuration file. Command-line controls cover installation, removal, starting, stopping, restarting, status checks, and configuration refreshes. The configuration can direct WinSW to restart a failed process or reboot Windows. It captures standard output and error streams, offering append, reset, ignore, and log-rotation modes. Before launch, it can download resources from URLs with authentication and proxy options. Service settings include service accounts and an SDDL security descriptor; documentation warns that Basic credentials over HTTP are sent in clear text. WinSW 3 runs with .NET Framework 4.6.1 or later, or through supplied native 32-bit and 64-bit .NET 7 executables. Binaries are distributed through GitHub Releases, with other packages and CI builds listed.