Titan Server Launcher

Run your DayZ server from one calm control room

Run your DayZ server from your own machine. Manage it from the interface or the command line – even with an AI agent.

AI agent ready

DayZ hosting usually means SteamCMD windows, hand-edited config files, mod folders, key copies, firewall checks and a separate web panel. Titan Server Launcher gathers those steps into a guided local tool that still keeps the owner in control.

Local authority on the host

The launcher runs where the server files live, so it can see paths, processes, ports and Workshop content directly.

Profiles instead of loose files

Each server keeps its own settings, ports, map, mod list, keys, profiles, backups and publish state. Restart schedule, warnings and auto-update are set per instance too.

Checks before risky actions

Preflight validation, key sync and restore rules help catch common launch mistakes before players feel them.

What is new in 1.5.x?

1.5.0: each instance starts its own executable with a relative profiles path. Configuration saves preserve unknown lines and comments; previews, responses and logs redact passwords.

1.5.1: the DayZ update watchdog defers in SteamClient mode and in Auto while Steam is running. The launcher handles client copies; otherwise the watchdog checks and updates the server anonymously.

Titan Server Launcher CLI reference
Steam sources - 1.5.x

Update without signing out of Steam

Titan can reuse completed server and Workshop downloads from your signed-in Steam client. During maintenance it copies ready files into its own server instances. It blocks account-based SteamCMD login while Steam is signed in, so updates do not sign you out. The client is not started or controlled by Titan; copies need extra disk space.

Choose a source in Steam settings
  • Auto (default) prefers ready client content when Steam is signed in. SteamClient requires ready client content; missing content is deferred. Subscribe to the reported Workshop IDs and wait for Steam downloads to finish.
  • SteamCmd selects SteamCMD; server app 223350 uses anonymous login. Account login remains blocked with signed-in Steam or detection failure, even in SteamCmd mode. The UI and logs explain the source or deferral.
Main functions

Everything a server owner reaches for first

The launcher keeps the operational pieces close: setup, config, mods, runtime, backups and web control. All of it is available from the command line as well.

Server install and updates

Detect SteamCMD, install the DayZ Dedicated Server and validate files before launch.

Workshop mod management

Add Workshop IDs, scan local mod folders, sync keys and build clean -mod / -serverMod launch arguments.

Configuration editor

Generate serverDZ.cfg from structured settings and keep per-server profiles consistent.

Start, stop and monitor

Start the DayZ server process, monitor health, check ports and recover from crashes. Recurring and one-off restarts, scheduled independently.

Web dashboard bridge

Publish server state, heartbeat data and manifests so the web panel can become a remote admin surface.

Backups and maintenance

Create ZIP snapshots, restore stopped instances and clean old log or crash files.

Automation

Agent-friendly server management

Titan Server Launcher is not built for humans only. An AI agent can run it end to end: Claude Code, OpenAI Codex, Google Antigravity or any agent that can use a command line. Ideal for developers and server operators who want to automate.

The titan CLI controls the running launcher through a local, administrator-only named pipe. Risks: read, write, destructive (explicit authorization and --yes), forbidden (never executed). Unknown commands fail closed. The CLI is not a remote network listener.

titan command-line client Installed alongside the launcher. Everything in the interface also works as a command: create a server on free ports, start, stop, restart, settings, Workshop mods, backups, RCON and maintenance.
Per-instance settings Every server instance has its own restart schedule, warnings, auto-update and backups.
Independent restarts Recurring (every N hours) and one-off (at a set time) restarts, independent of each other. If they coincide, the server restarts only once.
Security Local only and administrator only – never reachable over the network. Unknown commands are rejected, and dangerous actions need explicit confirmation. Every call is logged, with passwords redacted.
Output agents understand Machine-readable JSON output and clear exit codes. From the built-in help (titan help) and the command reference generated in the install folder, an agent learns how to use it.
Example commands
titan server create --name "Test" --auto-ports --open-firewall --wait
titan server settings <id> --restart-every 6h --restart-warnings 30,15,5
titan mod list <id> --json
titan server restart <id> --in 15m
Titan Server Manager (TSM)

Remote control with Titan Server Manager

Titan Server Manager (TSM) is the DayZ server mod for live players, telemetry and explicitly permitted game actions. The website relays authenticated owner actions through the API. Availability depends on installed versions, fresh capabilities and successful negotiation.

  1. Owner dashboard
  2. API
  3. launcherLocal / directRemote
  4. Titan Server Manager · DayZ

launcherLocal: through the host

The designated launcher exchanges commands, snapshots and results with the mod through local profile files protected by OS permissions. It connects the host to the backend. The local mod link requires no API token; host authentication remains separate.

directRemote: mod to API

The optional transport uses POST /titanmod/v2/{register,negotiate,poll,report,result,ack}: bind the installation, negotiate, poll commands, report state and acknowledge terminal results. Local and remote mutation are mutually exclusive. API support alone does not prove live integration.

Deny-all until explicitly allowed

permissions.actors[].allow is the complete allowlist for immutable actor IDs, intersected with enabled capabilities and adapter policy. A role or display name grants nothing. Keep install-bound credentials in secure configuration, never in command payloads, public pages or logs.

Know the limits before acting

HTTP 2xx or queued is not execution success. Inspect terminal results; never automatically switch transports after an unknown outcome. restartMission affects the mission; process restart belongs to the launcher. DayZ engine TLS identity verification is not established: use a trusted isolated network or authenticated tunnel and a proxy validating upstream TLS.

DayZ Knowledge Base

Server file reference in one place

A searchable reference for common DayZ server files, folders, editable values and risky operations. Useful before config, economy, mod and BattlEye RCON changes.

Open DayZ Knowledge Base
Detailed coverage

Built around real DayZ admin work

The product is not just a download button. It is the local operator layer between Steam, DayZ server files, BattlEye RCON, Workshop content and the owner dashboard. Through the titan command-line client, scripts and AI agents can use it too.

SteamCMD and server files Detects or installs SteamCMD, runs app updates, handles login prompts and validates the dedicated server install.
serverDZ.cfg generation Turns structured profile settings into the config DayZ expects, while preserving a clean per-server workflow.
Mod folders and bikeys Downloads Workshop items, scans @mod folders, separates client and server mods, and synchronizes required keys.
Runtime control Builds launch arguments, starts and stops the server, monitors process state and reports health. Recurring and one-off restarts are scheduled separately; if they coincide, the server restarts only once.
RCON actions Keeps BattlEye RCON available for common admin commands such as messages, player actions and live checks.
Backup and restore Creates snapshots of config, profiles, missions and keys, with restore rules that protect running servers.
Publishing and heartbeats Sends public server state, player counts, manifest revisions and online/offline signals to the website.
Approved automation Can apply approved file and RCON plans through controlled scopes instead of giving blind remote access.
Operator flow

From empty machine to managed server

01

Prepare

Install SteamCMD and DayZ server files, then create the local server workspace.

02

Configure

Set map, ports, passwords, profile paths, mods and server visibility.

03

Launch

Run preflight checks, sync keys, generate config and start the DayZ process.

04

Operate

Use RCON, live status, backups, logs and remote dashboard actions during daily admin work.