A field guide to your control room.
The same DST tools, a clearer view of the work. Classic remains the default; opt into Command Deck when you want the World view and focused workspaces.
Screenshots show the shipped v15 interface in isolated offline, built-in demo, or static states. They are not live personal-server captures. Select an image to inspect it.
Command Deck
An optional World/dashboard view and focused workspaces put the next task within reach. The persistent bottom dock includes the static DD Atlas, Solo Mode, Players, Bases, Economy, Commands, and Database. Find a tool searches the wider collection. Classic remains the default, and the Classic control takes you back.
Classic, still at home
Keep the familiar sidebar and Server Health dashboard. When connected, inspect VM, battlegroup, database, gateway, game pods, public ports, and restart information. Raw output and log exports help distinguish missing information from a healthy server.
Read the Deep Desert
Browse all twelve Coriolis layouts using sector grids, POI filters, and confidence notes. The shipped DD Atlas is a static community reference, not a live map. When server seed data is available, DST distinguishes a running Deep Desert seed from the next farm seed; exact POI placement remains approximate.
People, not database rows
Find a character and open Manage Player for focused administration: inventory, currency, progression, identity, and supported gameplay actions. Availability and offline checks remain authoritative. Teleport tracing records diagnostic evidence; it does not guarantee that the game executes a teleport.
Give your bases a second life
Blueprints has a dedicated place inside Bases, alongside base management and storage inventory. Inspect the catalogue and use supported import/export tools without hunting through unrelated pages. Import stays unavailable until the live game database is connected.
Your save. Your pace.
Manage one supported local Retail Solo save without a VM or Self-Hosted installation. Start with connection and validation, then use retained backups, typed settings, inventory, currencies, and supported tools. The shipped adapter targets the supported Retail Solo save format; older or custom saves may not be compatible. Save mutations require the game to be closed.
Deliberate configuration
Edit UserGame.ini and UserEngine.ini with typed controls, restore points, and isolated managed blocks. Client Engine.ini management is a separate opt-in. Proven controls stay in Game Config; recovered, unconfirmed controls belong in Experimental Lab.
The right controls, together
Command Deck groups commands by Battlegroup, VM & Power, Configuration, Network & Access, Database, Logs & Files, and Terminals & Tools. Review each action's requirements before running it. The custom layout remains available when you prefer your own arrangement.
A recovery path before a change
Back up, restore, import, mirror, inspect, and query PostgreSQL without tracking pod names. SQL starts read-only, and restore guidance calls out Deep Desert risks. Backups are recovery tools, not a promise that a destructive restore can be undone.
Keep control of access
Choose appearance, updates, host configuration, and remote access in one place. Browser Portal with Tailscale Funnel is the recommended remote path. Legacy Cloudflare configuration is retained but its portal is disabled by default until explicitly re-enabled in local Settings.
Leave the desk.
Keep the portal.
The full Browser Portal adapts to phones, tablets, and PCs. Host-created Owner and Admin accounts have different permissions; local-only tools such as Solo Mode and PowerShell stay on the host.
For new remote setups, use Tailscale Funnel. No separate native mobile app is required. Enabling account login retires the legacy paired native-app path.
Set up Browser Portal