ProxMenux is a menu-driven Proxmox VE toolkit, licensed GPL-3.0, that pairs an interactive terminal interface for post-install and backup/restore work with a self-hosted web dashboard for continuous health monitoring, built for homelab operators who run Proxmox on their own hardware.

What it is

ProxMenux lives in the Proxmox VE ecosystem, which itself runs on Debian, and it presents itself as an interactive toolkit for that platform: a menu-driven CLI plus a web dashboard, covering post-install configuration, backup and restore, and continuous health monitoring of a homelab. The repository is classified as TypeScript, and its topic list includes bash, tui, dashboard, pwa, monitoring, self-hosted, backup, homelab and proxmox-ve, which reflects that mix of a terminal front end and a browser-accessible service. It is distributed as a GPL-3.0 project with roughly 2,978 stars, 155 forks and 15 open issues at the time of writing.

The concrete problem it solves is the manual, scattered work that follows a Proxmox VE installation. Instead of running individual post-install and backup commands by hand and then checking node health from a terminal, an operator launches menu and works through on-screen options. The integrated ProxMenux Monitor then answers the monitoring half of that problem: it provides real-time visibility into the Proxmox infrastructure from any browser on the network, explicitly without needing a terminal, and it is installed automatically as part of the standard ProxMenux installation.

Key capabilities

• Menu-driven terminal interface launched with the menu command after installation, built on the dialog package for interactive terminal menus.
• ProxMenux Monitor, a web dashboard served at http://:8008 and reachable from any browser on the network.
• The Monitor runs as a systemd service named proxmenux-monitor.service that starts automatically on boot, and its status and logs are inspected with systemctl status proxmenux-monitor and journalctl -u proxmenux-monitor -n 50.
• Real-time monitoring of CPU, RAM, disk usage and network traffic, alongside an overview of running VMs and LXC containers with status indicators.
• Login authentication plus Two-Factor Authentication with TOTP support.
• Reverse proxy support for Nginx and Traefik, with a dashboard designed to work across desktop and mobile devices.
• Backup and restore workflows as a core function, echoed by the backup topic, and a beta channel installed from the develop branch through install_proxmenux_beta.sh.

Who uses it and how

• Homelab operators on a single Proxmox VE node use the menu for post-install setup, then keep the Monitor open for day-to-day health checks.
• Operators who want status without a terminal open the dashboard in a desktop or mobile browser on the local network at port 8008.
• Teams exposing the dashboard beyond the LAN place it behind Nginx or Traefik and rely on login authentication plus TOTP.
• Beta testers run the develop branch build, accept that features may be incomplete, and file GitHub issues that include journalctl -u proxmenux-monitor -n 50 output.
• Contributors work against CONTRIBUTING.md, which documents the two-phase dialog / whiptail UI flow, message helpers and the translation policy.

Getting started

Installation is a single command run in the Proxmox server terminal: bash -c "$(wget -qLO - https://raw.githubusercontent.com/MacRimi/ProxMenux/main/install_proxmenux.sh)". After that, launch the toolkit by running menu; a separate install_proxmenux_beta.sh script installs the beta build from the develop branch.

How it compares

The registry entry supplies no list of paid products that ProxMenux replaces, and it names no directly comparable self-hosted tool in the same space. On the facts available, it stands alone in this registry as a menu-driven Proxmox VE post-install, backup and monitoring toolkit.

When to use it — and when not to

A self-hoster takes on the operating burden of the whole stack: the setup installs dialog, curl, jq, git and python3 with python3-pip for the Flask-based Monitor, and the dashboard runs as a systemd unit that must be started and inspected. Anyone unwilling to run a curl-piped installer, or to read the installer source first as the README advises, should not pick it. The honest weaknesses are that TLS on port 8008 depends on putting a reverse proxy in front, that the beta branch is stated to contain bugs and incomplete features, and that the project is a relatively small one at 155 forks with 15 open issues.

bash -c "$(wget -qLO - https://raw.githubusercontent.com/MacRimi/ProxMenux/main/install_proxmenux.sh)"

menu

http://<your-proxmox-ip>:8008

# Check service status
systemctl status proxmenux-monitor

# View logs
journalctl -u proxmenux-monitor -n 50

# Restart the service
systemctl restart proxmenux-monitor

bash -c "$(wget -qLO - https://raw.githubusercontent.com/MacRimi/ProxMenux/develop/install_proxmenux_beta.sh)"

journalctl -u proxmenux-monitor -n 50