A DDRace server on ddnet.org's standalone Linux build, running the version you choose: for map testing, clan events and tournaments.

Select from our wide range of optimized game servers. Each server is configured for maximum performance and comes with DDoS protection.







Compare recommended use, plan hardware and monthly prices.
| Plan | Recommended for | Hardware | Monthly price |
|---|---|---|---|
| Bronze 4GB | Test, event or race server (recommended)Around 256 MB of memory is enough; 4 GB RAM and 50 GB NVMe leave a huge margin. | 4 vCore Ryzen 9950X · 4 GB DDR5 6000MHz · 50 GB NVMe SSD Samsung 990 PRO | ₺240.00/mo |
| Silver 6GB | Unlimited demo recording60 GB of disk for demos piling up with sv_auto_demo_max 0; no speed difference. | 4 vCore Ryzen 9950X · 6 GB DDR5 6000MHz · 60 GB NVMe SSD Samsung 990 PRO | ₺345.00/mo |
| Gold 8GB | Long-term teehistorian archive70 GB of disk for teehistorian's full gameplay logs; CPU is the same as Bronze. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | More than DDRaceNetwork needsOne server process never gets near this memory; only for the 100 GB disk. | 4 vCore Ryzen 9950X · 10 GB DDR5 6000MHz · 100 GB NVMe SSD Samsung 990 PRO | ₺530.00/mo |
| Diamond 12GB | Not recommended12 GB RAM sits idle here; with the same 4 vCores it is no faster than Bronze. | 4 vCore Ryzen 9950X · 12 GB DDR5 6000MHz · 110 GB NVMe SSD Samsung 990 PRO | ₺617.50/mo |
| Emerald 16GB | Not recommendedExtra vCores do not speed up a single DDNet-Server process. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | Not recommended32 GB and 12 vCores are never needed for a DDRace server. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
Tools that stand out when a DDRaceNetwork server works more like a workshop than a public race server.
The install can pull the latest stable release, a specific version such as 17.0, or the nightly build from ddnet.org. No surprise update lands halfway through a tournament.
sv_test_cmds, which only works from the initial config, enables the testing commands the docs also call cheats. On a private test server you can probe every corner of a map fast.
sv_solo_server removes player interaction, sv_hit controls whether hammers and weapons hit other players, and sv_endless_drag toggles endless hooking. Give each event its own rule set.
sv_auto_demo_record records matches automatically and sv_auto_demo_max caps how many demos are kept. sv_tee_historian writes complete gameplay data to disk, so plan storage around it.
Set ec_port and the mandatory ec_password and the server opens an external console. Bots and scripts you write can read chat and send commands through that channel.
Instead of a shared password, auth_add gives each staff member a key with their own name, level and password. access_level lets you change which level may run which command.
DDRaceNetwork server hosting at TheCrewHost starts at ₺240.00 ($6.00) a month and sets up DDNet-Server from the standalone Linux release on ddnet.org, running on Ryzen 9 9950X hardware in İstanbul. No Steam account is involved, and you can install the latest stable release, a specific version number or the nightly build. That flexibility suits event organizers who need one version frozen for a whole tournament, and mappers who want to try new features early. In data/autoexec_server.cfg you control solo mode, hit and hook rules, spectator slots, demo recording and the external console (econ). If you want the environment that follows the Steam release instead, see our DDNet page.
The DDRaceNetwork environment installs DDNet-Server straight from the standalone Linux package on ddnet.org instead of Steam, and it leaves the choice of version to you. The server program and protocol are identical to our DDNet environment, and players see both kinds of server in the same client. The difference is the distribution channel and version control.
Here you can pick the version to install in three ways: the latest stable release, a specific version number, or nightly. Stable is the right default for most communities. Pinning a version number keeps an update that changes behavior from landing in the middle of a tournament or a long clan event. Nightly is for mappers and test teams who want new game features and fixes before they reach stable.
No Steam account is needed for the install, since the files come from ddnet.org. If most of your players launch DDNet from Steam and you want the server to always track the Steam release, the DDNet environment is more convenient. If you want full control over the version, you are in the right place.
However good a new DDRace map looks in the game's built-in editor, it is not ready to release until a few people have run it on a real server. A DDRaceNetwork server is made for this. Start by leaving sv_register at 0 and setting a password so only your test team can join. Upload the map to data/maps over SFTP and open it with change_map through rcon. After edits in the editor, re-upload the file and change_map to the same map so everyone downloads the new version.
sv_test_cmds 1 only works from the initial config, and it turns on testing commands that the docs also refer to as cheats. That lets you retry hard sections over and over without replaying from the start just to see the end of a part. Never enable it on a server that keeps ranks; it belongs on test servers only.
Nightly helps here too: if your map relies on a new game feature, you can test it before that feature reaches the stable release. When testing is done, move the server to stable and open it to the community.
An event server's strength is that a handful of settings can reshape its rules entirely. sv_solo_server 1 enables solo mode, where players cannot affect each other at all, ideal for time trials where everyone runs the same map against the clock. It has to be set before the map loads, so it goes in the initial config.
sv_hit 0 stops players from hitting each other with hammer, grenade and laser, which shuts down trolling. sv_endless_drag toggles endless hooking and can completely change how hard some maps are. sv_team 2 makes teams mandatory, so in duo or four-player team tournaments everyone has to be in a team.
Spectators and streamers need room too. sv_spectator_slots reserves a number of slots for spectators only, and sv_reserved_slots holds places for special players such as staff. That way referees and the streamer can still get in when the server is full. And remember to keep the version pinned for the duration of the event.
After a tournament, recordings are what everyone asks for. sv_auto_demo_record 1 makes the server save matches as demo files automatically. sv_auto_demo_max keeps 10 demos by default and deletes older ones; set it to 0 to remove the cap, and your disk will start filling accordingly. Downloading important demos over SFTP and archiving them yourself is the easiest way to keep the server lean.
sv_tee_historian is a far more detailed record: it writes the entire game to disk, including every input from every player. As the documentation warns, that uses a lot of disk space. It is valuable for reviewing cheating suspicions or analyzing every moment of a tournament, but it is not a setting to leave on permanently.
Plan your disk with that in mind. For a normal server, Bronze's 50 GB lasts for years. If you keep unlimited demos or a long-term teehistorian archive, Silver's 60 GB or Gold's 70 GB provides a sensible safety margin. Memory and CPU needs do not change in these scenarios.
On a small server, a single sv_rcon_password may be enough, but at an event with several referees and moderators, a shared password gets out of hand fast. The auth_add command gives each staff member a separate rcon key with their own name, permission level (admin, moderator or helper) and password. When someone leaves the team, you remove only their key instead of changing everyone's password. access_level adjusts which level may use a particular command.
Econ, the external console, is the door to automation. Set a port with ec_port and a password with ec_password, and the server opens a console you can connect to from outside; without a password, econ never activates. A bot you write can use that channel to relay chat to Discord, collect tournament results or switch maps at set times.
Only open econ with a strong password, and share its port with your own tools alone. The panel console is always at hand as well: any command you type there is processed by the server immediately.
A DDRaceNetwork server is remarkably light; its packagers list 100 MB of memory as the minimum, 256 MB as recommended and around 1 GB of disk. That makes Bronze 4GB more than enough for a single DDNet-Server, whether it is a test or an event server. Bigger plans bring no speed for this game; their only justification is extra disk for demo and teehistorian archives.
sv_register adds the server to the master list, and it also accepts a comma-separated list of protocols such as ipv4 and ipv6. With registration off, players open the F1 console and type connect with the IP:port; the default port is 8303. Since sv_sixup is on by default, clients connecting over the Teeworlds 0.7 protocol can join as well.
If you run nightly or a pinned older version, tell your players which one; very different client versions can make some features look different from what they expect. The İstanbul location gives test teams and tournament players joining from Türkiye low latency.
A DDRaceNetwork server runs on a few hundred megabytes. If you plan heavy demo or teehistorian archives, look at Silver or Gold for disk.
Once payment is confirmed, the standalone Linux package downloads automatically and the server appears at gamepanel.hostingmerkezi.net. No Steam account needed.
Stay on stable for a community server, pin a version number for a tournament, and use the nightly build for map testing.
In data/autoexec_server.cfg set sv_name, password and sv_map, plus event-specific values like sv_solo_server, sv_hit and sv_team.
Create a separate rcon key with auth_add for each referee and moderator. If you use a bot, enable econ with ec_port and a strong ec_password.
Share the IP:port and the DDNet version in use. Turn on sv_register for a public server, and keep it off for private tests.
Questions from people setting up a DDRace server for map testing, events or a pinned version.
Our İstanbul datacenter runs on Ryzen 9 hardware, delivering low latency to players in Türkiye and good connectivity to Europe, the Middle East and the Caucasus.
Turkey
Everything your project needs — from game servers to VPS, dedicated servers, web hosting and Discord bot hosting.
Connect with our community of gamers and developers
Get instant support, share experiences, and stay updated with the latest news