Skip to content

Flowgate on Windows

Supported platform

  • Windows on x86-64. The same Flowgate codebase runs on Windows and Linux, and Windows nodes are part of the permanent validation lab.
  • There is no packaged Windows installer yet: deployment is currently a manually installed binary plus a configuration file, done together with H2 Innovations. A packaged installer is planned.
  • No .NET, Java, or container runtime is required; the node is a single native service binary with its TLS libraries alongside.

Service

Service integration is built into the binary itself:

flowgate service install --config C:\ProgramData\H2Innovations\Flowgate\node.yaml

registers the Windows service FlowgateNode (display name "H2 Innovations - Flowgate"), with matching uninstall, start, and stop commands. The service can be registered under a dedicated service account with --username and --password. Service lifecycle events are reported to the Windows Event Log.

Network

Identical to Linux: OPC UA endpoint on 17070, Reverse Connect listener on 17071 where enabled, management console on 8080 over HTTPS, and outbound dialing to a parent's 17071 or 17070 depending on link configuration. Configure Windows Firewall inbound rules only for the ports the node's role actually uses; a node that only dials outward needs none.

Storage

Windows nodes state their storage locations explicitly in the configuration file rather than relying on built-in defaults. The recommended layout keeps everything under one tree, C:\ProgramData\H2Innovations\Flowgate (the folder the Windows installer creates from 0.33.0 on; the updater keeps its own tree beside it in C:\ProgramData\H2Innovations\Flowgate-Update): the node's PKI directory is set there, and the node then keeps its state (store and forward spools, snapshots, audit trail, connector certificates, log files) in sibling folders of that directory.

Protect the state directory with NTFS permissions

On Windows, file permissions the node sets in POSIX terms have no effect; NTFS ACLs are the only real control. Restrict the configuration and state tree to SYSTEM and Administrators so that local non-administrator accounts cannot read the node's private key or configuration.

Hardware

Same guidance as Linux: no formal minimum published yet; the measured reference figures on the Performance Baselines page were recorded on 8 core, 16 GB nodes.