No Laptop. No RDP. No Friction.

Enterprise Windows Server control from your phone or tablet.

iOS, iPadOS, Mac

Try WinPulse Free View How It Works

Download on theApp Store Get it onGoogle Play Download on theMac App Store

Why IT Teams Choose WinPulse

Not a thin RDP client
No agents installed on target servers
No exposed WinRM endpoints
Built on native Windows protocols
Manage multiple servers from a single secure gateway
Operates within your existing Windows security model

Focused server control — without RDP dependency.

See it in Action

Essential Windows Server Administration Tools

Everything you need to monitor, manage, and maintain your Windows servers — securely from anywhere.

Live view of CPU, memory, services, and event logs on the target server.

Activity dashboard — See health at a glance without Task Manager or RDP.
Process monitor — Find and inspect heavy or suspicious processes in seconds.
Service manager — Check and control critical services without a console.
Event logs — Review errors and security events before a meeting or during an outage.

Try WinPulse Free

Need Active Directory management? See ADSignify

Security and Architecture

WinPulse connects to a single Windows gateway over SSH. The gateway talks to your servers using native Windows protocols—no agents on targets and no exposed WinRM endpoints.

No agents on target servers
No exposed WinRM endpoints
Single secure gateway (SSH); internal protocols only
Built on native Windows management (WinRM, WMI, CIM)
Aligns with your existing security and deployment practices

For the full architecture description and diagram, see WinPulse security and architecture .

Gateway requirement and configurations

The WinPulse gateway must run OpenSSH (SSH on port 22) and use PowerShell as the default shell for SSH sessions. Run the script below on the gateway server (elevated PowerShell) as a quick, idempotent way to install OpenSSH, open the firewall, and set PowerShell as DefaultShell. For a full step-by-step UI walkthrough (Settings, Services, firewall, registry), see the blog post linked below.

How to Configure SSH on Windows Server — step by step (UI-based installation)

Quick setup (PowerShell)

#Requires -RunAsAdministrator
# Install OpenSSH Server on Windows, set PowerShell as default shell.
# Idempotent: safe to run multiple times.

$ErrorActionPreference = 'Stop'

# --- 1. Install OpenSSH Server (use latest available capability) ---
$cap = Get-WindowsCapability -Online | Where-Object { $_.Name -like 'OpenSSH.Server*' }
if (-not $cap) {
    throw 'OpenSSH.Server capability not found on this image.'
}
if ($cap.State -ne 'Installed') {
    $result = Add-WindowsCapability -Online -Name $cap.Name
    if ($result.State -ne 'Installed') {
        throw "OpenSSH Server install failed. State: $($result.State)"
    }
}

# --- 2. Start service and set auto-start ---
Set-Service -Name sshd -StartupType Automatic
Start-Service -Name sshd

# --- 3. Firewall rule (create only if missing) ---
$ruleName = 'OpenSSH-Server-In-TCP'
if (-not (Get-NetFirewallRule -Name $ruleName -ErrorAction SilentlyContinue)) {
    New-NetFirewallRule -Name $ruleName `
        -DisplayName 'OpenSSH Server (Inbound)' `
        -Enabled True `
        -Direction Inbound `
        -Protocol TCP `
        -Action Allow `
        -LocalPort 22
}

# --- 4. Set PowerShell as default shell and restart SSH ---
$regPath = 'HKLM:\SOFTWARE\OpenSSH'
$shellPath = 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe'
if (-not (Test-Path $regPath)) {
    New-Item -Path $regPath -Force | Out-Null
}
Set-ItemProperty -Path $regPath -Name 'DefaultShell' -Value $shellPath -Type String -Force
Restart-Service -Name sshd -Force

Write-Host 'OpenSSH Server is installed, firewall rule added, and PowerShell set as default shell.'

Full setup guide

What Teams Like About WinPulse

“Server reboots and service restarts from my phone have been a game-changer. No more jumping on a laptop for quick fixes.”

— Systems Administrator

“We manage dozens of servers across environments. WinPulse's connection profiles and multi-target support save us hours.”

— Infrastructure Lead

“Event logs and process monitoring on the go—exactly what we needed for after-hours support without RDP.”

— IT Manager

Questions

What do I need on the server side to use WinPulse?

You need one Windows machine (gateway) with OpenSSH Server and PowerShell as the default shell. Target servers only need WinRM enabled—no agents or extra software. If you can manage them remotely today (e.g. via WinRM or WMI), WinPulse can connect through the gateway.

Does WinPulse work over Wi-Fi, cellular, or from outside the network?

Yes. WinPulse works over Wi-Fi and cellular. You connect to your gateway over SSH (port 22). From outside your network, use VPN or a secure tunnel to reach the gateway, then manage all targets from the app.

What Windows Server versions are supported?

WinPulse supports Windows Server 2019, 2016, 2012 R2, and Server Core. The app runs on iOS, iPadOS, and macOS (Apple Silicon).

Is there a free tier? How does licensing work?

You can manage one gateway server with full functionality at no cost. In-app subscription is available to manage additional target servers. All features are included; there are no tiered restrictions. Cancel anytime in your Apple account settings.

How do I get support or documentation?

Documentation and setup guides are available at www.signifium.com/winsignify. For technical questions or enterprise support, contact us at www.signifium.com/contact-us or winsignify@signifium.com.

Screenshots & Visual Proof

Recommended: dashboard overview, service control, event log filter, multi-server switching, report generation, network diagnostics. Short GIF loops (5–8 seconds) help demonstrate key workflows.