Vintage Story Server Manager 0.1.0 alpha

Vintage Story Server Manager 0.1.0 — alpha

An open-source desktop app, CLI, web dashboard and Linux Remote for managing Vintage Story servers on infrastructure you control. This is an early development release, not a stable release or an official Anego Studios product.

Cloud costs and responsibility

This software is not a hosting service. You supply and manage your own cloud account or host. Creating and running resources can incur charges, including VM compute, disks, IP addresses, network traffic and backup storage. Stopping the game, closing or uninstalling the app, and deallocating a VM do not necessarily stop all charges. Estimates and cost-saving features are not spending limits or guarantees.

You are responsible for all charges and for any subscriptions, commitments, contracts or other agreements you enter into with a cloud provider or third party, including those arising from using this software. You must monitor billing and remove resources you no longer need through your provider when necessary. The project and its contributors do not provide hosting, enter into those agreements on your behalf, or accept liability for those costs or agreements, to the extent permitted by applicable law. The warranty disclaimer and limitation of liability in the Apache-2.0 license apply.

Included

• Desktop setup with an automatically started Local Manager, cloud-account management and resource planning.
• Azure, Hetzner, DigitalOcean and Vultr adapters, existing Linux hosts over SSH, local Docker and Docker over SSH.
• Game lifecycle, console and activity logs, configuration and world forms, player administration, files, ModDB releases and custom mod ZIP installation.
• Local recovery copies, optional encrypted restic backups, Azure resource discovery and reconnect workflows.
• Shared CLI and MCP administration tools for server management and troubleshooting, with durable operation status and logs.

Provider adapters do not imply complete live acceptance testing on every provider. See status and limitations.

Downloads and Windows setup

Desktop installers are included for Windows x64 (.exe/.msi), macOS Intel and Apple Silicon (.dmg), and Linux x64 (.deb/.AppImage), with CLI archives for each platform and a Linux x64 Remote agent. All platform builds completed in GitHub Actions from commit cafa6e9. Checksums accompany the downloads. Source ZIP/tar.gz downloads contain source code, not installers.

1. Download the Windows x64 .exe installer or .msi when listed under Assets. Verify its SHA-256 against the corresponding checksum file.
2. Install and open Vintage Story Server Manager. Its Local Manager starts automatically; no separate local service or access-token setup is required.
3. For SSH/cloud setup, install OpenSSH Client. Azure sign-in also requires Azure CLI and your own Azure subscription. The app guides account sign-in and server setup. Local Docker needs a Linux x64 Docker engine, such as Docker Desktop configured for Linux containers.
4. Choose Create server, select your deployment method, and review the resource plan and costs before applying it. Follow the SSH identity and server-software installation steps before starting the game.

Desktop and CLI downloads are development binaries without publisher signing. Windows packages are unsigned; macOS packages, if attached, use ad-hoc signatures and are not notarized. Operating-system trust prompts are expected. Checksums verify download integrity; they are not publisher signatures. Native installation on every supported platform and clean-machine acceptance remain incomplete.

Game binaries and mods are not included. The Manager fetches supported game downloads from official Vintage Story sources; game and mod licenses remain separate. A game client and its licensing requirements are also separate from this project.

CLI and MCP plugin

Extract the CLI archive for your platform and add its directory to PATH. With the desktop app open, use vsm --desktop admin list to discover administration workflows or vsm --desktop mcp as an MCP stdio server. See the administration guide.

The vintage-story-server-manager-plugin-v0.1.0.zip asset contains the portable plugin definition and administration skill, not a platform executable. Extract it and configure your MCP/plugin client using its README. Its default command is vsm --desktop mcp, so vsm must be on PATH. The archive contains no credentials or Manager inventory.

Validation and known limits

Local Rust, CLI/MCP and UI validation has exercised operation status, request validation, configuration preservation and administration workflows. The installed Windows desktop and actual MCP stdio process were tested against an existing Azure server running Vintage Story 1.22.7: VM wake/deallocation, game restart, console/player checks, mod removal and reinstallation, and reconnection after a desktop restart. The original mod set and idle policies were preserved. These checks do not establish multiplayer join performance, every MCP mutation, off-host disaster recovery or acceptance on every cloud provider.

• A player attempting to join a deallocated VM does not wake it. Wake it from the Manager; starting the game separately may be required.
• Azure idle deallocation requires a Manager running outside the game VM. Keep the desktop app open, or run a separate hosted Manager. Disk/IP and other retained-resource charges can continue.
• SSH game hosts target Ubuntu 24.04 x64; Docker requires a Linux x64 engine. Windows/ARM game hosts are unsupported.
• Mod/game changes create recovery copies, but rollback is currently operator-driven. Keep independent backups of important worlds and recovery credentials.
• A hosted dashboard requires deliberate deployment and security configuration; it is not a hosted service provided by this project.

Report reproducible issues in the repository. Keep credentials, private keys, tokens and private server logs out of public reports; follow the security policy for vulnerabilities.