Swarm Hosts / Guides

Satisfactory

Staging — awaiting client validation

Satisfactory is available for server evaluation. Player connection, server claiming, and gameplay have not been validated. Start with a test factory.

Satisfactory's dedicated server uses both TCP and UDP for its primary port, plus a separate reliable TCP port. Persistent storage retains its server files and factory data. See Staging games for evaluation limits.

Requirements

Start with 4 CPU cores and 8 GiB memory for evaluation. Larger factories need more memory and CPU. Leave free disk space for downloads, saves, logs, and backups.

Launch and settings

  1. Choose Satisfactory from Staging and select a suitable host.
  2. Keep the offered launch defaults for the first test.
  3. Launch and wait for the server startup logs before opening Server Manager.
  4. Use a client that matches the installed server version.

The runtime defaults are 7777/TCP+UDP and 8888/TCP. Older guides using 15000/UDP or 15777/UDP do not describe this port layout. See the publisher-linked dedicated-server guide.

Connect

For later client evaluation, open Satisfactory's Server Manager, select Add Server, and enter the displayed player address and primary port. The separate reliable TCP connection must also reach the server. Check both routes when using a relay or direct port forwarding. Satisfactory has specific limits on external port remapping; an arbitrary public primary port must not be assumed to work. Public network and relay reachability, server claiming, authentication, and gameplay remain unvalidated.

Persistent data and backups

Persistent storage is mounted at /serverdata. Backups target /serverdata/serverfiles/FactoryGame/Saved and /serverdata/serverfiles/.config/Epic/FactoryGame/Saved, preserving generated configuration and saves without the installed game binaries. The local restart check preserved server configuration; no factory was created or claimed. Back up before changes and test restoration before relying on a factory save.

Server Actions

Game-specific Server Actions are unavailable during staging. Platform lifecycle, settings, files, logs, and backup controls remain subject to your permissions.

Mods & Content

The content page records desired identifiers only; it does not install, resolve, verify, or roll back Satisfactory mods. Begin with vanilla. Any manual mod workflow needs compatible client and server versions and a backup.