Get 20% off your first order using the coupon code
Run the community build with its own weapon set and gamemodes, four-team maps and VIP escorts included, on hardware chosen to hold a steady Source tick rate.
from $5.00/mo · unlimited slots
Enterprise hardware and every feature you need, at a fraction of the price. Not feeling it? We offer a no-questions-asked 7-day refund window.
Need more than 50 GB of NVMe? Just ask.
Keep up to ten backups at once.
Split your server into more than one.
Switch to any supported game, any time.
Modpacks, worlds, mods and plugins.
Every version, mod, and modpack.
We'll tell you when and why it crashed.
No AI or bots here. Only humans.
2 GB at $5.00 holds a 24-slot pub without strain, and 6 GB at $15.00 leaves headroom for four-team maps, custom content, and a full 32 players.
Every plan: Unlimited Slots · Unmetered Allocations/Ports · Unmetered Databases · Enterprise Hardware · Unmetered NVMe Storage
Need help choosing? Talk to a human or check the docs.
A busy Source server is a single-thread workload judged on tick consistency, so these nodes run Ryzen 9 7900-class CPUs with DDR5 ECC memory and filtering enabled by default.
The install is automated after checkout, so you can be changing level from the console within a few minutes.
Instant deploy · Automated install · No manual files
Hitscan fights punish inconsistent frame times, so servers sit on Ryzen 9 CPUs with DDR5 ECC memory and NVMe storage.
Ryzen 9 · 3 to 5 cores · NVMe SSD
Issue commands live, edit server.cfg in the browser, and swap the map cycle without waiting on a support ticket.
Live console · Config editing · Map uploads
Slot counts are never sold by the seat here, so a 32-player four-team night costs no more than a small private server.
Unlimited slots · Player list · Subuser admins
Attack traffic is filtered before it reaches the game port, included on every plan rather than sold as an upgrade.
Included free · All plans · Every region
Nine regions, from Salt Lake City and New York City to Brussels, keep your regulars inside a sensible ping band.
9 locations · NA and EU · Choose at order
Team Fortress 2 Classic is a community rebuild that follows an earlier design direction than the game it branches from. It runs as its own standalone install rather than an add-on to a live TF2 server, brings back the Civilian class and four-team play, and keeps weapons and mechanics that were cut or reworked years ago. Hosting it means running that build, not a TF2 server with a plugin bolted on.
Source servers take their orders from configuration files, and the FSH file manager puts them one click away. Your server.cfg sets the hostname, round timers, team balance limits, and rcon password, the map cycle file decides what comes next, and custom .bsp files upload straight into the maps folder over SFTP. The live console accepts the same commands you would type at an rcon prompt, so testing a cvar needs no restart.
Mode variety is the reason to run this build. VIP asks one team to escort a defenseless target while the other hunts it, four-team maps split the server between Red, Blue, Green, and Yellow, and Domination turns control points into a rolling score race. Each mode has its own map prefixes and cvars, so keep separate config files and load the right one from your map cycle.
Compare all 9 game server locations for node hardware and the regions each one covers.
Common questions about running a Team Fortress 2 Classic server with us.
No. Team Fortress 2 Classic is a separate community build with its own weapons, the Civilian class, and four-team modes. It installs as its own game server rather than as content layered on TF2, so you select it at checkout and manage it independently of any Team Fortress 2 server you also run with us.
Two gigabytes at $5.00 handles a 24-slot server with a standard rotation, and 6 GB at $15.00 gives four-team maps, custom content, and a full 32 players plenty of room. Those tiers include three CPU cores, which matters more than raw memory when you are chasing a consistent tick rate.
Yes. Upload .bsp files into the maps folder with the file manager or over SFTP, add them to the map cycle file, and change level from the live console. Unmetered NVMe storage means a large map pack is not a problem, and you can keep separate cycle files for different theme nights and swap them between rounds.
Yes. Everyone connecting needs the same Team Fortress 2 Classic release, since it is a standalone build rather than server-delivered content. When a new version lands, move the server with the one-click version changer and tell your regulars, otherwise they are refused for a version mismatch when they try to connect that evening.
The server files are entirely yours: upload plugin directories over SFTP or through the file manager, edit your config files in the browser, and restart from the console. Whether a specific community plugin works depends on that project tracking this build, so test on a spare allocation before a busy evening. Ten allocations come with every plan.
