Nevatal Cloud Proxmox VE Control Plane & VPS Orchestrator: Architecture & Performance Benchmark

The Engineering Challenge: Why Nevatal Cloud (Proxmox VE Control Plane & VPS Orchestrator) Was Architected

Traditional Proxmox VE management consoles are built for system administrators, exposing raw cluster topologies and storage LUNs that are intimidating—and dangerous—for end customers. At the same time, commercial panels like cPanel and WHMCS impose hefty licensing fees and lack tight integration with modern e‑commerce ecosystems.

Nevatal Cloud solves these pain points by delivering a purpose‑built control plane that brings enterprise‑grade multi‑tenant isolation, self‑service provisioning, and real‑time telemetry to a single Dell PowerEdge R640 hypervisor. The result is a self‑hosted AWS/DigitalOcean alternative with zero per‑seat licensing and automated fulfillment via WooCommerce.

Core Architecture & Technical Stack Deep‑Dive

System Architecture Overview

The architecture is a clean, decoupled design that separates client interaction, API orchestration, state management, and the underlying hypervisor layer.

• Client & Management Layer – React 19 SPA, WordPress/WooCommerce store, and AI coding agents (MCP/OpenClaw) consume the API.
• Gateway Layer – Nginx reverse proxy handles SSL, static assets, and HTTP routing while enforcing rate limits.
• Backend Layer – Go 1.23 REST API with JWT‑based RBAC, service layer (instance, quota, game, Android, MCP), and an asynchronous worker queue for heavy tasks.
• State Layer – PostgreSQL 16 provides ACID‑compliant storage for users, quotas, instances, audits, and jobs.
• Hypervisor Layer – Dell PowerEdge R640 runs Proxmox VE; QEMU/KVM VMs (Cloud‑Init), LXC containers (Waydroid, game servers), and storage pools (ZFS/LVM‑Thin/MinIO S3) are orchestrated via the Proxmox VE REST API v2.

The flow is visualized in the architecture diagram (see PRD). Clients call the Go API; services read/write state to PostgreSQL, emit jobs to Redis‑backed workers, and execute Proxmox API calls for VM creation, cloning, and configuration.

Tech Stack Highlights

\ Semin

Key Features Breakdown & Practical Benefits

1. Proxmox VE Hypervisor Automation

• Cloning QEMU templates with Cloud‑Init IP/SSH configuration.
• Programmatic booting of instances.
• Support for both QEMU VMs and LXC containers (Waydroid Android, game servers).

2. WooCommerce Integration

• nevatal-cloud-manager plugin triggers immediate VPS provisioning on checkout.
• Seamless order‑to‑resource mapping with webhook‑based fulfillment.

3. Client Portal Shortcode

• WordPress shortcode [nevatal_instances] enables users to reboot, terminate, and monitor VMs directly from their dashboard.

4. Enterprise Dell PowerEdge R640 Telemetry

• Real‑time CPU core loads, memory allocation, and storage pool metrics exposed via the control plane.

5. Secure Backend

• JWT authentication + RBAC access controls.
• Rate‑limited Proxmox API connection pooling for high‑throughput operations.

Real‑World Deployment & Production Topology

Nevatal Cloud runs on a single Dell PowerEdge R640 node (IP: 100.86.61.70) in a production environment. The hardware is equipped with multiple CPU cores, 256 GB RAM, and a ZFS storage pool that supports thin‑provisioned volumes and MinIO S3 buckets for object storage.

Typical deployments include:

• Web hosting providers offering automated VPS plans via WooCommerce.
• Engineering teams provisioning internal development and staging VMs on‑prem.
• Developers seeking a zero‑cost, self‑hosted alternative to AWS/DigitalOcean.

The control plane scales horizontally by adding more Proxmox VE nodes; each node registers with the central PostgreSQL state, and the Go orchestrator manages cross‑node resource allocation.

Data Flow & How It Works: Step‑by‑Step Workflow

1. Customer Checkout – User purchases a VPS plan on the WooCommerce store. The nevatal-cloud-manager plugin fires a webhook to the Go API.
2. Order Validation – API validates quota, checks available hypervisor resources, and creates a user record in PostgreSQL.
3. VM Provisioning Job – An asynchronous job is pushed to Redis; the worker clones a pre‑configured QEMU template, injects Cloud‑Init metadata (IP/SSH), and issues a start vm command via the Proxmox API.
4. State Update – PostgreSQL is updated with the new instance ID, IP address, and status “running”.
5. Client Portal Sync – The React SPA polls the API for instance status and reflects real‑time telemetry (CPU, memory) to the user via the [nevatal_instances] shortcode.
6. Support for Specialized Workloads – For Android instances, the worker launches a Waydroid LXC; for game servers, it configures port forwarding; for MCP agents, it spins up a dedicated container with OpenClaw.

Architectural Comparison: Nevatal Cloud (Proxmox VE Control Plane & VPS Orchestrator) vs Traditional Approaches