Shooter · Lightweight
Host a Counter-Strike Source Server
Run a Counter-Strike Source dedicated server with persistent files, Source-query readiness, private RCON actions, and direct or relay access.
Counter-Strike: Source uses a shared TCP/UDP game port and stores persistent server files under /home/steam/css. Swarm Hosts waits for a Source-query response before marking the Swarm Server ready.
- Server Actions
- Guided settings
- Backups
Validated public launch
Hardware and runtime
What Counter-Strike: Source needs
Catalog minimums are a starting point. World size, player count, content, and game settings can require more resources.
- CPU
- 1+ cores
- Memory
- 1+ GiB
- Player traffic
- TCP and UDP
- Persistent backup scope
- 1 catalog-declared path
- Persistent data: /home/steam/css
- Network: one published port number on both TCP and UDP
- First start: installs the dedicated server before the readiness check can pass
- Public access: use the assigned host or relay address and published port
Launch workflow
From host to running server
After launch, open Settings → Counter-Strike: Source Settings to change the managed values. Saving settings recreates or restarts the server, so connected players will be disconnected.
- Choose Counter-Strike: Source.
- Set the server name, starting map, player limit, and optional join password.
- Set a private RCON password if you want to use Server Actions.
- Review bot quota, bot difficulty, team-play, starting-money, LAN, and tickrate settings.
- Launch and allow up to 15 minutes for a first-time install on a slower host.
Networking
How players connect
Players can join through the in-game server browser or client console:
The TCP and UDP mappings must use the same published port number. Share the endpoint shown by Swarm Hosts, not the container's default port.
Managed shared relay when the game, host, and current relay path support it.
Catalog-backed Server Actions
Tools Swarm Hosts exposes for Counter-Strike: Source
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
List connected players and their server user IDs.
List installed maps
List maps installed in the server data directory.
Broadcast message
Send a server-authored chat message.
Set bot quota
Set the number of bots maintained by the server.
Set bot difficulty
Change the difficulty used for newly managed bots.
Restart round
Restart the current round after a short delay.
Change map
Change immediately to an installed map.
Kick player
Disconnect a player using the numeric user ID from List players.
Mods & Content status
Manifest Only
Track mods in one place and apply them manually through the game-specific workflow.
MetaMod:Source and SourceMod are manually managed under the persistent cstrike/addons tree. Create a backup, stop the Swarm Server, upload a compatible plugin set through Files & Backups, then start and validate the server. Automatic plugin discovery and dependency resolution are not currently available.
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.
- Relay-backed Source-query validation passed on 2026-06-28 for the current Counter-Strike: Source image.
Windows 10/11 + Linux
Ready to host Counter-Strike: Source?
Connect the Windows or Linux computer you already own, then follow the game-specific launch path.