Servy functions as a service wrapper that transforms ordinary executables into managed Windows services. The application handles process isolation, working directory mapping, and environment variable propagation. Administrators select the service account, set CPU affinity, and define restart behavior through a structured interface. The tool records stdout and stderr streams to rotating text logs.
The program monitors registered services for abnormal termination and excessive resource consumption. Configurable heartbeat checks verify that a service remains responsive rather than merely alive. When a check fails, Servy executes the defined recovery action, which may include restarting the executable, running a diagnostic script, or rebooting the host system.
Servy targets system administrators, DevOps engineers, and developers who deploy long-running background processes on Windows. It manages Node.js web servers, Python workers, .NET microservices, and database agents as first-class Windows services. The CLI and PowerShell modules enable automated provisioning across fleets of servers without manual GUI interaction.
| Service Control Manager registration for arbitrary language runtime executables | Explicit working directory prevents system32 path resolution failures |
| Configurable boot startup modes including delayed automatic initialization | CPU scheduling priority classes range from idle to realtime |
| Processor affinity masks restrict service threads to selected cores | Per-service environment variables isolate runtime configuration from machine scope |
| Dependency chains enforce prerequisite service readiness before launch | Stdout and stderr capture with size or date rotation |
| Heartbeat verification through file timestamps, TCP responses, or memory patterns | Failure-triggered recovery actions with stable runtime reset windows |
| Pre and post lifecycle hooks execute custom orchestration scripts | Service identity supports gMSA, domain, and local security contexts |
| Live CPU and memory telemetry for managed service processes | GUI, CLI, and PowerShell parity without feature disparity |
| Connection strings and API keys injected without machine-wide changes | Latency-sensitive core binding prevents cross-core thread migration overhead |
| Audit-grade historical logs retained across service restart cycles | Restart policies execute custom programs or force reboot actions |
| Cache warming and firewall updates via lifecycle script triggers | Memory leak detection through historical performance counter trends |