Supported Platforms
The compatibility position for Windows, SQL Server, Azure SQL, and virtualisation — and how to ask about a version this page doesn't list yet.
"Is Infohub supported on Windows Server X / SQL Server Y?" is asked every time Microsoft ships a release. This page holds the position in one place — and, because OS releases will always outrun documentation, the reasoning that lets you evaluate a version this page has not caught up with.
The principle#
Flow 7.2.0 is a .NET 8 application suite against Microsoft SQL Server. Compatibility follows from those two facts:
- Any Windows that .NET 8 supports is a candidate; Infohub adds no OS-version-specific dependencies of its own beyond the historian client libraries some connectors need (which have their own vendor support matrices).
- Any SQL Server the .NET 8 SQL client supports, at a compatibility level the schema runs on, is a candidate.
So when Server 2025 or SQL 2025 lands: the realistic answer is "expected to work; certified after validation" — and the formal statement for a given release comes from support, because certification lags availability. Ask with your exact target versions; do not infer silence as "no".
Windows#
| Platform | Position |
|---|---|
| Windows Server 2019 / 2022 | Supported — the mainstream deployment base |
| Windows Server 2025 | .NET 8 supports it; confirm current certification with support before committing production |
| Windows 10/11 (64-bit) | Fine for evaluation and Config workstations |
| Linux (Ubuntu, x64 and ARM64) | Supported for the Bootstrap and everything it hosts — Platform, engines, servers — since 7.0, as a TAR distribution or a Docker image. Flow Config and the MSI installer remain Windows-only, so a Linux site still needs one Windows workstation for configuration. See Installing Infohub Beyond the Wizard. |
In-place OS upgrades under an existing Infohub: stop the Bootstrap service, upgrade the OS, start it again — the licence is unaffected (it binds to the database identity, not the OS). Verify historian client libraries survived the upgrade; vendor clients are the usual casualty.
SQL Server#
| Platform | Position |
|---|---|
| SQL Server 2017–2022 | Supported; 2019/2022 the mainstream base |
| SQL Server 2025 | Same principle as Server 2025 — expected via the standard client; confirm certification before a production commitment |
| SQL Express | Works, for evaluation/small models — remember its hard caps (10 GB per database, memory/CPU limits). A growing site will hit them; the move to Standard is a restore plus licence re-request: Instance Lifecycle Administration |
| Azure SQL Database (PaaS) | Not supported. Infohub's schema deployment and maintenance assume full SQL Server; historical attempts fail at instance creation |
| Azure SQL Managed Instance / SQL on Azure VMs | SQL on a VM is simply SQL Server (supported). Managed Instance is closer to full SQL but is not the certified base — ask before building on it |
| Availability Groups / HA pairs | Supported, with the licensing caveat: AG membership changes reset the licence binding — plan keys into AG work: Licence Keys in Practice |
Compatibility level: after moving a database between SQL versions, mismatched compatibility levels have produced upgrade-time errors. Set the database's compatibility level to the host version's norm as part of any SQL platform move.
Virtualisation and cloud VMs#
Fully supported (VMware, Hyper-V, Azure/AWS/GCP VMs) with the two operational cautions from the requirements article: don't overcommit CPU (interval-boundary bursts), and keep Infohub and SQL close in network terms.
Browsers and clients#
The web client targets current evergreen browsers (Chromium-family, Firefox, Safari). Flow Config requires a Windows machine (net8.0-windows). Flow Mobile: current iOS/Android via the app stores — see Flow Mobile.
Historian client libraries — the hidden matrix#
Connector-side compatibility is frequently the real constraint: AVEVA/Wonderware and some OPC connectors depend on vendor client libraries installed on the Platform host, and those have their own OS/version matrices (a 2018-era vendor DLL against a 2023 historian is a documented failure class). When planning an OS upgrade or new server, check the vendor client compatibility alongside Infohub's — per-connector notes are in the data source articles.
When this page and reality disagree#
This page is maintained per release; Microsoft ships continuously. For anything newer than the table: state your exact Windows/SQL versions to support and get the current certification position in writing. What this page guarantees is the reasoning — .NET 8 + full SQL Server + vendor clients — so you can tell a probably-fine gap (new Windows point release) from a structural no (Azure SQL PaaS, Linux).