All projects

VPS Manager

Overview

VPS Manager is a fully open-source project for managing any VPS. The code is available here: https://github.com/X5Coder/VPS-Manager

Installation relies on a single command: curl -fsSL https://raw.githubusercontent.com/X5Coder/VPS-Manager/main/install.sh | bash

This command installs the entire project inside one path, /vps-manager, on the server, and everything related to the panel lives inside this path. A management interface then becomes available on port 9090.

Securing the Install

At the start of installation, the user is asked to enter a valid Telegram account ID, and this ID becomes fixed and can never be changed afterward. The interface then shows a field to enter a Telegram bot token. After entering the token, the interface moves to a stage asking for a temporary code that was actually sent through that same Telegram bot to that same first-entered ID, and this code is valid for one device only. This way, only the owner of that Telegram account, who holds both the fixed ID and the bot token together, can ever log into the panel, and after the first login no one else can get in even if they know the password alone.

Panel Sections (Sidebar)

Server, Rooms, Root Shell, Logs, x5coder-agent, Backup, Settings

Server

This page shows live data about the VPS itself:

  • Quick cards: VPS disk, CPU, Memory, Load/Net.
  • VPS details split into: Identity (Hostname, OS, Kernel, Arch, Uptime, Hypervisor), Network (Public IP, SSH port), Hardware (CPU, Memory, Disk), Platform (Docker, Panel).
  • How each project uses disk section: shows each room's disk usage based on a data-only quota model (files + volumes + the container's writable layer), while the Docker images themselves are shared at the host level and are not counted against the quota; Multi-type rooms (such as Supabase) share the same image set on disk, so the image is not counted per room separately.
  • VPS Storage & Host Disk Breakdown section: splits the total host disk usage into layers: Docker Images, Project Data, Build Cache, Container RW, OS & Rest, Free Space.

Rooms

This section lists every room (project) created on the VPS, with the ability to create a new room and choose its type:

  • Single: one Docker container only.
  • Multi: more than one linked container, such as a full Supabase stack.

After creating a room, a project upload section appears: the project is converted into a zip file and uploaded from the browser, and the panel builds a Docker image from it automatically and shows it running.

Inside each room there are tabs: Overview, Images, Volumes, Secrets, Logs, Manage. A room shows:

  • The ID, status (running/stopped/paused), type (single/multi).
  • A source upload area (.zip, .tar.gz, .tgz, .tar) that updates this room only, preserving ports, domain, the .env file, and data on every update, plus an update history that fills in once a new archive is uploaded or a GitHub deploy happens.
  • The container's internal port and an upload-and-update button.
  • The number of containers, images, and volumes.
  • The storage quota used versus the cap, and the total project size (image + data/volumes).
  • A room-specific copyable password.
  • Live stats specific to that room: CPU, Memory, Disk, Load.
  • Project links (the domain bound to it, if any).
  • A room-specific backup: zipped into backup/<room_id>.zip containing the stack/containers, volumes, config, and .env file, running as a background job.
  • Port & domain: setting the host port, and binding a domain with an SSL status (Bind/HTTPS/Unbind), applied through nginx as a reverse proxy inside the project itself.
  • Identity & disk: editing the project's name and password, and adjusting the disk quota via a slider with quick buttons (+1G, +2G, +5G) up to a maximum based on available host space.

Below the open room's details, a list of all the other rooms on the same VPS also appears, each with quick actions (Open Room, Pause/Resume, Delete), along with quota used, a size breakdown (image/data/volumes), and its own password.

Root Shell

Direct access to the VPS shell with root privileges, right from the browser.

Logs

A central section for viewing room and container logs.

x5coder-agent

A dedicated HTTPS API that lets any AI agent inspect and manage the VPS: reading status, deploying projects, and managing containers, volumes, domains, and logs, all through predefined JSON calls instead of giving the AI raw access to the system shell.

  • A public discovery endpoint with no key needed: GET /x5coder-agent/v1/tools returns the full tools catalog along with the required schema for each tool.
  • A single Bearer key governs all control calls, it never expires automatically but can be regenerated at any time, and regenerating it instantly invalidates the old key everywhere it is used.
  • Every control call: POST /x5coder-agent/v1/tools/<tool_name> with an Authorization: Bearer <key> header and a JSON body.
  • A unified response shape: {success:true, data:{...}} on success, or {success:false, error:{code, message}} on failure, with HTTP codes: 400 (bad input or the operation failed), 401 (missing or wrong key), 404 (unknown tool), 405 (wrong HTTP method).
  • Safety rules built into the tools themselves: most tools are scoped by room_id, obtained first via the get_projects tool; destructive tools (delete_*) require explicitly passing confirm:true or they are refused; deploy_project and update_project tools accept a base64 zip archive up to 64MB and preserve ports, domains, the .env file, and data on update; secret values are never returned, only variable names; and all get_* tools are read-only and safe to call anytime.

Backup

  • Full Host Backup: a single archive containing all rooms, the panel's database, settings, proxy files, and env files, keeping only the newest archive.
  • Per-Project Backups: an independent backup for each project stored in backup/<room_id>.zip, runnable per room.

Settings

  • Root SSH password: changing the root SSH password directly from the panel.
  • Admin panel password: changing the panel's password, which signs out all active admin sessions.
  • Storage: showing actual free disk space, total quota reserved across all rooms, and the real free host space, clarifying that a room's quota caps only files, volumes, and container data — not Docker images — so host disk fill is mostly caused by images and build cache.
  • Access alerts: optional Telegram notifications (bot token + chat ID) that can be turned on or off, while the primary owner's chat ID stays fixed as entered during the first install.
Who Uses It

The project is fully open source, and anyone who owns a VPS and needs a tool to manage it can install it directly with the single command and start using it right away.


Problem

Managing a single VPS hosting several different projects, each in one or more Docker containers, usually requires separate manual handling of Docker, Nginx, SSH, and backup files. It is also hard to safely let an AI tool control the server without giving it full access to the system shell.

Solution

VPS Manager provides a single panel installed with one command that manages every project as an independent room (single container or a group of containers), with projects uploaded as an archive and the image built automatically, domain and certificate binding through nginx, backups for each project or the whole server, and an x5coder-agent interface that lets any AI agent control the server through a predefined set of tools instead of raw access, all behind a login system secured with a fixed Telegram account, a bot token, and a one-device-only code.


Highlights

  1. One-Command Install

    The entire project is installed through a single curl command that downloads and runs install.sh on any new VPS.

  2. /vps-manager

    Unified Install Path

    All of the project's files and components live inside one fixed path on the server.

  3. Multi-Layer Telegram Login Security

    Login requires a Telegram ID fixed since install, a bot token, and a temporary code valid for one device only, sent through that same bot.

  4. Instant Resource Dashboard

    The Server page shows quick cards for disk, CPU, memory, load, and network usage.

  5. Full VPS Details

    The VPS details section shows the server's identity, network, hardware, and platform (Docker and the Panel itself) in organized cards.

  6. Data-Only Storage Quota Model

    Each room's quota only counts files, volumes, and the container's writable layer, while Docker images stay shared at the host level.

  7. Host Disk Breakdown

    The VPS Storage & Host Disk Breakdown section shows total disk usage split between images, project data, build cache, container writable layer, the OS, and free space.

  8. Single and Multi Rooms

    Every project becomes an independent room: either a single Docker container (Single) or a group of linked containers (Multi) such as a full Supabase stack.

  9. Automatic Upload and Image Build

    A project is converted into a zip file, uploaded from the browser, and the panel builds and runs a Docker image from it automatically.

  10. Updates That Preserve Settings

    Uploading a new archive to the same room preserves its ports, domain, .env file, and existing data.

  11. Domain and SSL Binding

    A domain can be bound to each room with an SSL status (Bind/HTTPS/Unbind) applied through nginx as a reverse proxy.

  12. +1G / +2G / +5G

    Adjustable Storage Quota

    Each room's storage quota can be increased via a slider and quick buttons, up to a maximum based on available host space.

  13. Full and Per-Project Backups

    The project supports a full server backup (newest copy only) and independent backups for each project individually.

  14. Browser-Based Root Shell

    This section provides direct VPS shell access with root privileges without needing an external SSH client.

  15. x5coder-agent: Safe AI Control

    A dedicated API with allow-listed tools and a single Bearer key lets any AI agent manage the server without raw shell access.

  16. SSH and Panel Password Changes

    The root SSH password and the admin panel password can both be changed directly from the Settings section.

  17. Optional Telegram Alerts

    Telegram bot alerts can be enabled for any access or access attempt to the panel, while the primary owner's ID stays fixed.

  18. Open Source

    Fully Open-Source Project

    The complete project code is publicly available on GitHub and anyone can install it on their own VPS.


Features

  • One-command install that builds a complete management panel for any VPS on port 9090, with login secured through Telegram (a fixed ID, a bot token, and a one-time code valid for one device)
  • A room system that turns every project into a single Docker container or a Multi group of containers, with the project uploaded as an archive and the image built and deployed automatically
  • Precise storage management that separates each room's data quota from total host disk space (images, build cache, container writable layer), with domain and SSL binding per room through nginx
  • A dedicated x5coder-agent API with allow-listed tools and a single Bearer key, letting any AI agent deploy projects and manage containers and domains without raw access to the system shell
  • Full-server or per-project backups, a browser-based Root Shell, and optional Telegram alerts for any access attempt

Tech stack

HTMLCSSJavaScriptGoPythonSQLDockerNginxTelegram Bot API

Architecture

Multi-Layer Telegram Login System

Logging into the panel passes through three layers: a fixed Telegram ID entered at install time and never changed afterward, a Telegram bot token entered in the interface, and a temporary code that actually arrives through that same bot to that same ID and is valid for one device only, which prevents access by anyone who does not hold all three together.

Room Model and Automatic Image Building

Every project becomes a room of type Single (one container) or Multi (several linked containers, such as a Supabase stack). The user uploads the project's archive and the panel builds a Docker image from it and runs it, preserving ports, domain, data, and the .env file on any later update.

Data-Only Storage Quotas and Host Disk Breakdown

Each room's quota only counts files, volumes, and the container's writable layer, while Docker images stay shared at the host level and are not counted against the quota, and Multi-type rooms share the same image set. In parallel, the Server section shows a full breakdown of actual host disk usage across images, project data, build cache, container writable layer, the OS, and free space.

x5coder-agent as an AI Control Layer

A separate HTTPS interface exposes an allow-listed tools catalog through a public discovery endpoint, and executes every control call through a single Bearer key and a JSON body, with a unified response shape for success and failure, plus built-in safety rules such as scoping tools by room ID, requiring explicit confirmation for destructive operations, and never returning secret values, turning VPS control into a safe, callable tool set for any AI agent.

Backups and Domain Binding via nginx

The project provides a full server backup (newest copy only) covering rooms, the panel's database, settings, proxy files, and env files, alongside independent backups for each room. At the same time, domains and SSL certificates for each room are bound through an internal nginx reverse proxy within the project itself.



Users

A fully open-source project; anyone who owns a VPS and needs to manage it can install it directly