Shooter · Lightweight
Run a Team Fortress 2 Dedicated Server with Swarm Hosts
Launch a persistent Team Fortress 2 server on your own Linux host, select maps and player limits, use closed Source actions, and share its relay endpoint.
Team Fortress 2 uses Valve's Source dedicated server. Swarm Hosts installs the server anonymously through SteamCMD and persists the runtime and configuration under /home/steam/tf2.
- Server Actions
- Guided settings
- Backups
Validated public launch
Hardware and runtime
What Team Fortress 2 needs
Catalog minimums are a starting point. World size, player count, content, and game settings can require more resources.
- CPU
- 2+ cores
- Memory
- 2+ GiB
- Player traffic
- TCP and UDP
- Persistent backup scope
- 2 catalog-declared paths
The guided launch form exposes the server name, password, map, maximum players, and LAN mode. The RCON credential is reserved for the image-local Server Actions adapter and must never be shared with players.
- Gameplay and query: 27015/udp
- Private local RCON transport: 27015/tcp
- Persistent data: /home/steam/tf2
- Default map: cpbadlands
- Minimum resources: 2 CPUs and 2 GB RAM
Launch workflow
From host to running server
- Open Launch and choose Team Fortress 2.
- Set the server name, starting map, maximum players, and an optional player password.
- Keep LAN mode disabled for an internet-accessible server.
- Confirm the requested CPU and memory fit the selected Swarm Host, then launch and wait for the server to report Running.
Networking
How players connect
When the Swarm Server is running, copy the managed relay host and UDP port from its connection details. In Team Fortress 2, open the developer console and use connect host:port, adding the player password when prompted. Share only that player endpoint; the container's private RCON port is not a player connection address.
Managed shared relay when the game, host, and current relay path support it.
Catalog-backed Server Actions
Tools Swarm Hosts exposes for Team Fortress 2
Availability comes from the production catalog and verified game guide. Controls stay typed and bounded to the workflow the game supports.
Server status
Read the current map and player summary.
List players
Refresh the verified connected-player list.
List installed maps
Refresh maps installed in the pinned runtime.
List bans
Refresh identities currently banned by the Source server.
Broadcast message
Send a server-authored chat message.
Change map
Change immediately to a freshly verified installed map.
Kick player
Disconnect a freshly verified connected player.
Ban player
Ban and disconnect a freshly verified connected player, then persist the ban list.
Remove ban
Remove a freshly verified Source identity ban and persist the ban list.
Mods & Content status
Plugin Ecosystem
SourceMod plugins are untrusted executable code. Upload compatible files manually and restart the server.
SourceMod plugins are untrusted executable code. The first release records a manual plugin strategy only; provider resolution, automatic updates, and rollback are not promised.
Know before launch
Current boundaries
- Production hosting supports Windows 10/11 or Linux with Docker Desktop in Linux-container mode on Windows, or Docker Engine or rootful Podman on Linux.
- Managed shared relay when the game, host, and current relay path support it.
- Exact-image managed-relay, status, discovery, broadcast, map-change, injection rejection, and zero-restart proof passed on 2026-08-27. Player-targeted client behavior is queued for owner-led manual acceptance.
Windows 10/11 + Linux
Ready to host Team Fortress 2?
Connect the Windows or Linux computer you already own, then follow the game-specific launch path.