Skip to content

Install on Windows

The Windows source node runs as a Windows Service and starts automatically on boot. It uses a single pre-built binary — no Python runtime needed. It supports self-updating: new versions (engine packs) are applied automatically when signalled by the Hub.


Prefer containers? The source node also ships as a container image with a Helm chart — same engines, same credentials.

  • Windows 10/11 or Windows Server (x64)
  • Administrator privileges
  • Network connectivity to the Hub host and port (outbound TCP — no inbound rules needed)
  • A node created on the Nodes screen, with its Client ID and Client Secret — shown once when the node is created

  1. Download the nexomatic-source-node-setup-windows-x86_64.exe installer from your platform administrator.
  2. Run it as Administrator.
  3. Enter your Client ID and Client Secret when prompted.
  4. The installer registers the Nexomatic Generic Source Node service, seeds its configuration (Hub endpoint, node type, version) in the service’s registry Environment key, and starts it.
Terminal window
# From an elevated PowerShell prompt
.\nexomatic-source-node-setup-windows-x86_64.exe

The installer ships the node binary to C:\Program Files\Nexomatic Source Node\ and registers the service with automatic restart on any exit (so a clean self-update exit restarts the service on the new version). Upgrading from the pre-rename AutomaticsSourceNode service copies its configuration over and removes the old service.

The installer writes configuration to the service’s registry key:

HKLM\SYSTEM\CurrentControlSet\Services\NexomaticSourceNode\Environment

The values that matter most:

ValueMeaning
CLIENT_ID / CLIENT_SECRETNode credentials from the Nodes screen
CLIENT_TYPESOURCE_NODE
HUB_HOST / HUB_PORT / HUB_TLSHub endpoint (defaults to the platform’s public hub with TLS)
NODE_VERSIONInstalled version (set by the installer)
UPDATE_BASE_URLBase URL for self-update packages
Terminal window
sc.exe query NexomaticSourceNode
sc.exe start NexomaticSourceNode

Event log / service output shows Registered node … followed by heartbeats. Once connected, your self-hosted sources appear on the Sources screen.


Uninstall from Settings → Apps (or the installer’s uninstall mode). The service is stopped and removed; source configuration and cursors under the install directory are removed as well.