One Windows server runs phaf. Check these points before you start — most installation problems come from a missing requirement, not from phaf itself.
Server
| Item | Minimum | Recommended |
|---|---|---|
| Operating system | Windows Server 2019, 64-bit | Windows Server 2022 or 2025, 64-bit |
| Processor | 2 cores | 4 cores |
| Memory | 4 GB | 8 GB |
| Disk for the application | 1 GB | 2 GB (room for the previous version kept during upgrades) |
| Disk for data | 20 GB | Size it for your message volume and how long you keep messages. A separate data drive is best. |
| Clock | Synchronised with your domain or an NTP server. Two-factor codes and certificate checks depend on the correct time. | |
phaf can share a server with other applications. Do not install it on a domain controller. Node.js does not need to be installed: the installer brings the runtime phaf uses.
Database
phaf keeps its transactions, message history, logs and audit trail in an application database. Choose one now — you can change later with the built-in migration assistant.
| Option | When to use it | What you need |
|---|---|---|
| SQLite (default) | One server, small to medium volume, quick start. | Nothing. The database is a file in the data folder. |
| SQL Server | Higher volume, central backups, your DBA manages the database. | SQL Server 2016 or later (Express, Standard or Enterprise), an empty database and a login. See SQL Server. |
| MySQL / MariaDB | Not supported as the application database in this version. See MySQL. | |
Network
| Direction | Port | Why |
|---|---|---|
| Users → server | TCP 443 | The web console, through IIS or nginx with HTTPS. |
| Inside the server | TCP 8181 (or the port you choose in the installer) | phaf itself. The installer checks that the port is free. |
| Server → SQL Server | TCP 1433 (or your instance port); UDP 1434 for named instances | Only if you use SQL Server. |
| Server → mail server | TCP 587, 465 or 25 | Email alerts. |
| Server → partners | TCP 22 (SFTP), 21 / 990 and the passive range (FTP/FTPS) | The servers your flows connect to. |
| Server → network shares | TCP 445 | Only if flows read or write Windows shares. |
phaf does not need internet access and sends no telemetry.
Accounts to prepare
- A Windows administrator to run the installer.
- A service account for phaf, if you do not want the service to run under the default system account — for example a domain account when flows read Windows network shares. See The Windows service.
- A SQL Server login for phaf, if you choose SQL Server.
- A TLS certificate for the name users will type (for example
phaf.your-company.local), issued by your internal or a public certificate authority. - An SMTP account or relay for email alerts.
Before you continue
- Windows Server 2019 or later, 64-bit, with the clock synchronised
- Database chosen: SQLite, or a SQL Server database and login ready
- Port 8181 free, or another port chosen
- TLS certificate and DNS name ready
- The installer and its SHA-256 checksum received