Run your own server.

Downloads

The NOVA Swift Dedicated Server is one small standalone program. It doesn't need the game, a pilot or any EV Nova data: it carries the session (rules, chat, moderation, the plug-in check) while each player's own game runs their ship. You run it from a web admin panel in your browser.

• No game data. Nothing copyrighted to copy onto a VPS.
• Zero setup. It starts with sensible defaults, makes server.cfg next to itself and prints the admin address and a one-time password.
• Web admin panel on port 53737 with a four-step setup wizard, players (kick, ban, message), live settings, plug-ins from the catalog, the public listing helper, a network check and live logs.
• Plain-language errors, for example "Port 53735 is already in use. Is another server running?".
• Everyone plays together. Linux, Steam Deck, Windows and Apple players share the same server.

Where to run it

The server is light (a few MB of memory per player, no simulation). Anything that can stay switched on will do.

Set it up in 5 minutes

1. Download and start it

   Unpack the download. On Windows double-click Start Server.bat (or NovaSwiftServer.exe). On Linux or macOS run ./NovaSwiftServer in a terminal. It prints a box with your admin panel address and an admin password shown only once: write it down.

2. Open the admin panel

   On a desktop your browser opens by itself on http://localhost:53737 and signs you in for the first-run wizard. On a headless machine open the printed address from your own computer (or through an SSH tunnel, see below).

3. Answer four questions

   The wizard asks for a name, open or password (plus player slots and the rules: Safe, Full stakes or Custom), which plug-ins to run (optional, picked from the community catalog), and whether you want a public listing.

4. Open the ports

   Forward UDP 53735 and 53736 on your router, or open them in your VPS firewall (next sections). The panel's Network page has a "can players reach me?" check and an automatic router (UPnP) button.

5. Join it

   In the game choose Multiplayer, then Quick Connect, and type the address from the dashboard (it has a Copy button). Anyone on your network sees it under LAN automatically.

Pick your path

# docker-compose.yml (also in packaging/server/)
services:
  novaswift:
    build:
      context: ../..                       # the repository root
      dockerfile: packaging/server/Dockerfile
    image: novaswift-server
    restart: always
    ports:
      - "53735:53735/udp"
      - "53736:53736/udp"
      - "127.0.0.1:53737:53737/tcp"   # admin panel, this machine only
    volumes:
      - ./data:/data

docker compose up -d
docker compose logs novaswift | head -30   # admin password is printed once

Open the ports

# ufw (Ubuntu, Debian, Raspberry Pi OS); the installer does this for you
sudo ufw allow 53735:53736/udp

# firewalld (Fedora, RHEL)
sudo firewall-cmd --permanent --add-port=53735-53736/udp && sudo firewall-cmd --reload

New-NetFirewallRule -DisplayName "NOVA Swift server" -Direction Inbound -Protocol UDP -LocalPort 53735-53736 -Action Allow

The admin panel

server.cfg and the console

Everything lives in one server.cfg next to the program (or, if that folder isn't writable, in your user data folder; --data FOLDER picks one). The panel rewrites it when you save, so you rarely touch it. Changes made by hand need a restart.

[server]
name = Joshua's NovaSwift server
description = Friendly co-op, newbies welcome
port = 53735                  # UDP; port + 1 answers pings
max_players = 8
password =                    # empty = open
motd = Welcome, pilot!        # shown in chat when someone joins
region = eu
lan_announce = true
upnp = false

[rules]
preset = safe                 # safe | full | custom
# custom only: pvp_damage_real, death_real, friendly_fire, allow_pvp, allow_trade, game_speed

[admin]
port = 53737
bind = 0.0.0.0                # 127.0.0.1 = this computer only
password_hash =               # set from the panel

[plugins]
enabled = frozen-heart        # catalog ids and uploaded folder names

[public]
listed = false
address = play.example.com
owner = Jane
contact = discord: jane

[updates]
check = true
auto_update = false

[bans]
203.0.113.7 = griefing

Command line: --data DIR, --port N, --admin-port N, --no-browser, --no-stdin, --reset-admin-password, --version. Console commands (type them into the server window):

Security

The server is built for the public internet. The admin panel listens on this machine only by default (use an SSH tunnel; the installer enforces it), logins lock out with growing waits, passwords must be strong, and every admin action is written to an audit log. The Linux service runs as a no-login account inside a systemd sandbox (read-only system, no capabilities, filtered system calls); the Docker image runs unprivileged with a read-only file system.

On the game port the server rate-limits and size-limits every connection, blocks flooding addresses for ten minutes, refuses to answer oversized or unpadded status pings (so it cannot be used to amplify an attack), strips forged identities from relayed messages, and cleans player names and chat. Admins can kick, ban, mute and run an invite-only allowlist; players can /votekick, /report and block others. Updates install only from signed GitHub releases, and plug-in downloads are HTTPS-only, size-capped and unpacked safely.

Keep it running

The Linux installer sets up a systemd service that starts at boot and restarts after a crash: sudo systemctl status novaswift-server, journalctl -u novaswift-server -f. Docker uses restart: always. On Windows and macOS use Start with this computer in Settings. The server checks GitHub for new versions (tag server-v…) and shows a notice; it only installs them if you turn on automatic updates.

Get listed

The public server list is a JSON file in the NovaSwift-Plugins repository. Both the game's browser and the server list on this website read it. The panel's Public listing page does the paperwork:

1. Fill in the details

   A public address (a DNS name is best), your name and a contact such as a Discord name. The checklist tells you what's missing.

2. Copy your entry

   The panel generates the entry, including the content hash of every gameplay plug-in you require. Nothing is uploaded automatically.

3. Open the pull request

   The button opens servers/servers.json on GitHub in edit mode: paste the entry into the list and choose Propose changes. A check runs on it, and once it's merged your server appears in the game and on the website.

Rules for listing: a public address (no 192.168.x.x), no password, honest rules labels, plug-ins players can get from the catalog, family-friendly names, and a contact. Servers that stay offline for a month or two may be removed. Until you're listed players can join with your address.

{
  "id": "example-eu",
  "name": "Example Sector",
  "host": "nova.example.com",
  "port": 53735,
  "region": "eu",
  "description": "Friendly 24/7 server, safe rules, stock EV Nova.",
  "owner": { "name": "Jane", "contact": "discord: jane" },
  "rules": "safe",
  "plugins": [],
  "maxPlayers": 12,
  "added": "2026-10-13"
}

The old headless mode

Before the standalone server, the Linux game build could run headless with --server. It still works, but it needs your EV Nova data on the machine and has no web panel, so it is legacy: prefer the Dedicated Server above.

scripts/run-dedicated-server.sh --name "My Server" --port 53735 --max-players 8 --rules safe

FAQ and troubleshooting