Run a Foundry server on your own VPS with ZapX. You have full control over the system, and the Game Server Installer gets your server set up in just a few minutes—no Remote Desktop connection required. This guide explains what you need, how to install the server, and how to manage it afterward.
| Requirement | Foundry |
|---|---|
| Operating system | Windows Server 2019 or later |
| Memory | 4 GB minimum |
| Free disk space | 8 GB minimum on drive C: |
Foundry is only available for Windows in the Game Server Installer. If your VPS runs Linux, install a Windows Server template under Settings > Reinstallation. This deletes all data on the VPS. Learn more in Server Reinstallation.
- Open your VPS in the ZapX dashboard and go to the Tools tab. Select the Game Server Installer.
- Under Your server's operating system, select the Windows tile.
- Under Choose game, search for FOUNDRY and select it.
- Under Set up server, choose the Server name and Player slots. You can find the Game port and Query port under Advanced settings.
- Click Install on this VPS, then click Start installation.
The installer downloads and sets up the Foundry server through SteamCMD, then starts it. For details on how the installation works, see the Game Server Installer guide.
Foundry generates the world the first time it starts. This takes 1.5 to 8 minutes, depending on the load. Subsequent starts take around 90 seconds. Wait for the world to finish generating before connecting.
A join password is only prompted for when you run the command in PowerShell (the password is hidden as you type). If you install from the dashboard, the server has no password.
You can also install Foundry yourself using a command. To do so, copy the command shown in the last step, connect through Remote Desktop, and run it in Windows PowerShell as an administrator.
When the installation is complete, the installer displays your server address under How to connect. To learn how to connect, see Foundry: Connect to the Server.
Your server files are located on the VPS at C:\ZapX-GameServers\foundry\:
| Folder/File | Contents |
|---|---|
server\ | Foundry server files |
server\app.cfg | Server settings |
data\save\ | Your world and automatic saves |
data\IntergalacticArchive\ | The game's archive |
logs\foundry.log | Game log |
logs\server.log | Server output |
Your Foundry server starts automatically when the VPS boots and restarts if it crashes. To manage it, connect through Remote Desktop and use the desktop shortcuts:
FOUNDRY (foundry) - StartFOUNDRY (foundry) - StopFOUNDRY (foundry) - Restart
Foundry's settings are stored in server\app.cfg. You can add other settings there, such as the automatic save interval, whether the game pauses when no players are online, or the map seed. Stop the server before editing the file. The installer overwrites the name, player slots, ports, join password, and data folder every time you install or update the server, so change these settings through the installer. See Foundry: Server Configuration for an explanation of all options, and Foundry: Manage Save Games to learn how to upload custom worlds.
Updates are not installed automatically. To update, open the Game Server Installer again and select FOUNDRY. The installer detects the existing installation and displays Update. Alternatively, use the FOUNDRY (foundry) - Update shortcut on the VPS. Your settings and save files will be preserved.
| Port | Protocol | Use |
|---|---|---|
| 3724 | UDP | Game |
| 27015 | UDP | Query |
The installer opens these ports in the Windows Firewall. If you start the installation from the dashboard, it also opens them in your VPS's Network Firewall. If you installed using a command, check and open the ports there yourself.
Use the FOUNDRY (foundry) - Backup shortcut to back up your world, archive, and app.cfg as a ZIP file in C:\ZapX-GameServers\_backups\foundry\. Use FOUNDRY (foundry) - Restore to restore a backup.
Your entire VPS is also backed up automatically every day. With an active ZapX Pass, you can restore these backups yourself and create your own. Learn more in Daily Backups, Restoring Backups, and Restricted Actions.