Depl0y

Proxmox VE Management Panel — Infrastructure at your fingertips

🌐 Website: depl0y.mspreboot.com

⭐ If Depl0y saves you time, give it a star — it helps others find the project!

Depl0y is a free, open-source web control panel for Proxmox VE. Manage VMs, clusters, nodes, storage, backups, networking, firewall, HA, and physical hardware from a single dark-mode interface.

---

Screenshots

A guided tour at depl0y.mspreboot.com covers more screens than fit here.

Login

Proxmox Datacenters & Hosts

Multi-datacenter view with node health, cluster join/unjoin, server-model chips, BMC poll selector, and ⚡ Power dropdown per host

VM List

Filter, search, bulk-select, and per-row actions — start/stop/migrate/clone/snapshot/delete

VM Detail

Per-VM lifecycle, config (CPU / RAM / disks / NICs), snapshots, firewall, console, and live charts

Create VM

Guided VM creation with cloud-init credentials, storage selection, and ISO/cloud-image picker

Federation Map

Live OpenStreetMap showing all datacenters as pins — green online, red offline

Cluster Status

Cluster-wide quorum, node membership, HA resources, and replication jobs

HA Management

HA group + resource CRUD with quorum/state monitoring

Backup

PBS datastore browsing, backup schedule CRUD, and manual triggers

Storage

Storage pools across nodes with content browsing

ISO & Cloud Images

Upload ISOs, configure cloud-image templates, manage on disk

iDRAC / iLO Dashboard

Hardware health, power, temperature, wattage for all BMC-equipped servers — Dell iDRAC + HPE iLO via Redfish

iDRAC Server Detail

Per-server CPU / DIMM / storage / firmware / network / SEL inventory + power actions

Deploy LLM

One-click LLM deployment — Ollama, llama.cpp, vLLM, LocalAI with optional GPU passthrough

Audit Log

Every user action and system change recorded with filtering

User Management

Role-based access — Admin, Operator, Viewer — with 2FA/TOTP

Settings

Cloud image setup, cluster SSH, HA enablement, integrations, and one-click system updates

API Explorer

Browse and test the depl0y REST API directly from the panel

---

Features

🖥️ Full Proxmox VE Management

• VMs — start/stop/reboot/suspend/resume, config editing (CPU, RAM, disks, NICs), snapshots, clone, migrate, firewall, VNC console, QEMU serial terminal
• LXC Containers — lifecycle, config editing, snapshots, terminal (xterm.js)
• Nodes — RRD metrics charts, VM + LXC list, storage browser, network config, task log, node terminal, OS-level shutdown / reboot via pvesh
• Cluster — status, node list, HA groups and resources, quorum monitoring
• Cluster Join / Unjoin — join any node to a cluster (fingerprint auto-fetched), remove nodes from cluster
• Replication — job CRUD, force-sync, log viewer
• Node Evacuation — migrate all VMs off a node to other online nodes
• Firewall — cluster, node, and VM-level rules; security groups; IPsets
• Backup — schedule CRUD, manual trigger, PBS datastore browsing
• Storage — pool management, content browsing, ISO and cloud image management
• Networking — bridge/bond/VLAN config with apply-pending support
• Offline-tolerant — host/node endpoints (status, vms, lxc, tasks) return clean empty payloads when a node is powered off so the dashboard doesn't blow up

📊 Dashboard

• Widget grid — drag-and-drop reordering with masonry (asymmetric column) layout
• 10+ widgets — CPU, RAM, storage, network traffic, disk I/O, VM status, alerts, activity feed, quick actions
• Clickable tiles — every widget links to its management view
• Per-widget refresh — each widget auto-refreshes independently

🗺️ Federation & Multi-Datacenter

• Multi-host — add and manage multiple Proxmox VE hosts with API token or password auth
• Live Map — OpenStreetMap/Leaflet with datacenter pins (blue = online, red = offline)
• Federated Summary — aggregate VM/node/storage stats across all registered hosts
• Federated Dashboard — cross-datacenter VM/node overview in one view

🖧 iDRAC / iLO Out-of-Band Management

• Redfish Dashboard — unified health, power, temperature, wattage for all BMC-equipped servers
• Two-section Power menu — surface a ⚡ Power dropdown on every host card, node card, and on the iDRAC management page. Top section runs through the Proxmox OS (graceful shutdown / reboot via pvesh), bottom section runs through iDRAC/BMC (Power On / Force Off / Graceful Off / Reset / Power Cycle / PXE) — the only path that can power on a fully-off machine
• Server model auto-detection — Redfish Model → Dell SystemPID → Dell SystemID → PCI subsystem lookup → manager generation tag, in that order. Resolves PowerEdge model names directly from the BMC even on 13G boxes where the standard Model field is blank
• Manual model override — pencil-edit on the host/node model chip; persists to system_settings and applies to the live cache instantly. Required for older (iDRAC 7) BMCs that don't expose model metadata at all
• Configurable poll interval — 1 / 2 / 5 / 10 minutes, persisted globally; backend live-reschedules the job and queues an immediate poll on change
• Continuous post-poll refresh — Refresh All / Poll Now drives a 1.5 s cache re-fetch loop for ~20 s, so per-server model/health/power-state updates appear as soon as each individual BMC responds (rather than waiting for the slowest)
• Hardware Inventory — CPUs, DIMMs, storage controllers & drives, firmware, NICs, SEL
• Daily firmware-update check — Dell catalog XML parsed daily; BIOS / iDRAC available-version chips with direct support links
• Multi-vendor — Dell iDRAC (iDRAC 7 / 8 / 9 / 14G+) and HPE iLO via Redfish v1; SSH-based hardware reporting for hosts without Redfish

🤖 LLM Deployment

• Simple + Advanced modes — 4 questions to deploy, or full control over engine/model/GPU/OS/storage
• 4 Engines — Ollama, llama.cpp (GGUF), vLLM (OpenAI-compatible), LocalAI (Docker)
• 15+ Models — Llama 3.x, Mistral, Phi-4, Gemma, Qwen, DeepSeek, Code Llama, and more
• GPU Passthrough — NVIDIA (CUDA) and AMD (ROCm) with automatic driver install
• Add-ons — Open WebUI, ComfyUI (Stable Diffusion), AI auto-tuning, RAG, conversation logging

📥 VM Import

• File upload — OVA, OVF, VMDK, VHD, VHDX, QCOW2, RAW via drag & drop
• VMware direct — connect to ESXi or vCenter, browse and pull VMs over the network
• Auto-parse — OVF descriptors extracted for name, CPU, RAM, disk, OS type
• Disk conversion — VMDK/VHD/VHDX → qcow2 via qemu-img automatically

⚡ Cloud Image Deployment

• 30-second deployments — Ubuntu, Debian, Rocky, AlmaLinux (after one-time template setup)
• Cloud-Init — hostname, user, SSH key, static IP, DNS, package injection

🔐 Security & Access Control

• Role-based — Admin, Operator, Viewer with route-level enforcement
• 2FA / TOTP — authenticator app support with QR code setup
• Encrypted storage — all passwords and API tokens encrypted at rest (Fernet)
• Audit log — every user action and system change recorded
• Rate limiting — 100 req/min globally with security headers

🔄 VM Update Management

• One-click updates — check and install updates on any managed Linux VM via SSH
• Real-time streaming — live terminal output as apt/dnf runs
• Auto-scheduled checks — configurable interval (6h–7d) for automatic checks

---

Quick Start

One-Line Installation

curl -fsSL http://deploy.agit8or.net/downloads/install.sh | sudo bash

Installs all dependencies, configures nginx, and creates a systemd service — ready in ~30 seconds.

Post-Installation

1. Open http://your-server-ip — default credentials: admin / admin (change immediately)
2. Enable 2FA — Settings → User Profile → Enable TOTP
3. Add a Proxmox host — Proxmox Hosts → Add Datacenter → test connection
4. Deploy or import a VM

Updating

cd /opt/depl0y && git pull origin main && sudo bash deploy.sh

Or: Settings → System Updates → Check for Updates → Install

---

Configuration

Environment Variables (/etc/depl0y/config.env)

SECRET_KEY=your_jwt_secret_key_minimum_32_chars
ENCRYPTION_KEY=your_fernet_encryption_key
DATABASE_URL=sqlite:////var/lib/depl0y/db/depl0y.db
DEBUG=false
LOG_LEVEL=INFO

Storage Locations

Path	Contents
/var/lib/depl0y/db/depl0y.db	SQLite database
/var/lib/depl0y/isos	ISO images
/var/lib/depl0y/cloud-images	Cloud image templates
/var/lib/depl0y/ssh_keys	SSH key pairs
/var/log/depl0y/	Application logs
/tmp/depl0y-imports/	Temporary VM import working directory

---

Architecture

┌─────────────────────────────────────┐
│         Frontend (Vue.js 3)         │
│   SPA · Axios · Chart.js · Leaflet  │
│   Dark Mode · Widget Grid · xterm   │
└──────────────┬──────────────────────┘
               │ HTTP REST (/api/v1)
┌──────────────▼──────────────────────┐
│       Backend (FastAPI + Python)     │
│  Auth · VMs · Cluster · Import      │
│  LLM · HA · Backup · iDRAC · Alerts │
└──────┬──────────────┬───────────────┘
       │              │
┌──────▼──────┐ ┌────▼────────────────┐
│   SQLite DB  │ │   Proxmox VE API    │
│  (users/VMs/ │ │  nodes/qemu/cluster │
│  settings)   │ │  + Redfish / SSH    │
└─────────────┘ └─────────────────────┘

Key dependencies: proxmoxer, pyVmomi, paramiko, SQLAlchemy, Pydantic, APScheduler, python-jose, Leaflet

---

API Documentation

• Swagger UI: http://your-server/api/v1/docs
• ReDoc: http://your-server/api/v1/redoc
• In-App API Explorer: Sidebar → API Explorer

---

Development

# Backend
cd backend && python3 -m venv venv && source venv/bin/activate
pip install -r requirements.txt
uvicorn app.main:app --reload

# Frontend
cd frontend && npm install && npm run dev

# Production build + deploy
sudo bash /opt/depl0y/deploy.sh

---

Troubleshooting

Cannot connect to Proxmox host

• Verify credentials and network connectivity
• Disable verify_ssl for self-signed certificates
• Ensure Proxmox API port (8006) is reachable

VM import fails

• Ensure local storage exists with enough space on the target node
• SSH must be configured between Depl0y server and Proxmox host (Settings → SSH Setup)

Cluster join fails

• Ensure the root@pam password is correct for the cluster master node
• The fingerprint is auto-fetched — if it fails, fetch it manually: pvecm status on the master

Backend logs

sudo journalctl -u depl0y-backend -f

For more help: GitHub Issues

---

Contributing

Pull requests welcome. For major changes, open an issue first to discuss what you'd like to change.

---

License

MIT — see LICENSE for details.