Servy


Servy — Free Download. Windows service manager

Servy is a Windows utility for converting standard executables into native system services. It provides configuration for startup type, process priority, CPU affinity, environment variables, dependencies, and service identity. The tool monitors CPU and RAM usage, captures console output to rotated logs, and supports lifecycle hooks for pre-launch, post-launch, pre-stop, and post-stop actions. Heartbeat checks and restart policies maintain service availability without manual intervention.

★★★★★
5.0(1 ratings)
File size: 121 MB
The latest version of Servy is: 10.3
Operating system: Windows
Languages: English
Price: $0.00 USD (Open Source (MIT))

What’s new in Servy

  1. Added an AllowOverriddenRuntimeVars option to the service, enabling runtime environment variable expansion.
  2. Added a column visibility toggle and enabled column resizing in the services table within the manager.
  3. Moved the None date rotation option to the top of the dropdown in the desktop app.
Full update (+2 more) →
  • Run any executable as a service. Servy registers a selected program file as a Windows service using the Service Control Manager. The executable can be written in Node.js, Python, .NET, Java, Go, Rust, PHP, or Ruby. Registration creates a native service entry that follows standard Windows start, stop, and restart behavior.
  • Working directory control. The tool defines the exact folder path where the service process starts. This setting ensures relative file paths, configuration files, and data directories resolve consistently. It prevents errors caused by defaulting to the system32 directory when a service launches.
  • Startup type configuration. Servy sets the service startup mode to Automatic, Automatic (Delayed Start), Manual, or Disabled. Automatic services launch when the operating system boots, while delayed start reduces resource contention during startup. Manual mode requires user or script initiation.
  • Process priority assignment. The application assigns a CPU scheduling priority class to the service process. Available levels include Idle, Below Normal, Normal, Above Normal, High, and Realtime. Lower priorities reduce interference with interactive applications, while higher priorities accelerate CPU-bound workloads.
  • CPU affinity binding. Servy restricts the service process to specific processor cores. The affinity mask maps threads to selected logical processors, which prevents a service from consuming cycles on all cores. This is relevant for latency-sensitive systems and software with per-core licensing.
  • Environment variable injection. The tool defines environment variables passed to the service process at startup. Variables can store connection strings, API keys, configuration paths, or runtime flags. Changes take effect after service restart without altering the machine-wide environment.
  • Service dependency management. Servy specifies other Windows services that must start successfully before the target service launches. Dependencies ensure network stacks, database engines, or message queues are operational. The Service Control Manager enforces the startup order automatically.
  • Log capture and rotation. The program captures standard output and standard error streams from the running executable. Log data is written to text files with configurable rotation based on file size or date. Historical logs remain available for auditing and troubleshooting after service restarts.
  • Heartbeat health checks. Servy monitors service responsiveness through periodic heartbeat verification. A heartbeat can be a file timestamp update, a TCP port response, or a process memory pattern. Failed heartbeats trigger restart policies according to user-defined thresholds.
  • Restart policy configuration. The utility defines automatic recovery actions when a service stops unexpectedly. Policies include restart on first failure, restart on subsequent failures, run a specific program, or reboot the computer. Reset failure counts after a stable runtime window.
  • Lifecycle hooks support. Servy executes custom commands or scripts before the service launches, after it launches, before it stops, and after it stops. Hooks handle tasks like cache warming, temporary file cleanup, firewall rule updates, or sending notifications to monitoring systems.
  • Service identity selection. The tool configures the security context under which the service runs. Options include Local System, Local Service, Network Service, local user accounts, domain accounts, Active Directory managed service accounts, and group managed service accounts (gMSAs).
  • Runtime resource monitoring. Servy displays live CPU usage and memory consumption for managed services. Performance counters update in the graphical interface and are available through the CLI. Historical data helps identify memory leaks or periodic CPU spikes.
  • Graphical interface and CLI. The application provides a desktop GUI for visual management and a command-line interface for scripting. PowerShell cmdlets extend automation capabilities. All configuration options are accessible through each interface without feature disparity.

Servy development began in 2021 as a response to limitations in built-in Windows service tools. The project team consists of two developers specializing in Windows system programming and process management. The initial release targeted .NET Framework 4.8 for compatibility with Windows 7 and Server 2008 R2. A subsequent rebuild on modern .NET added native ARM64 support and improved performance on Windows 10 and 11. The codebase is written primarily in C# with a small portion of C++ for low-level process interaction.