🚀 Prosmox: Smart Cloud-to-Proxmox Migration with AI

🌱 Inspiration

As cloud bills continued to rise and vendor lock-in became a common pain point, I realized many businesses were overpaying for underutilized cloud services on AWS and Azure. At the same time, robust local virtualization platforms like Proxmox VE offered a cost-effective, flexible, and performant alternative. I envisioned a solution that could analyze live cloud infrastructure, suggest optimized migration paths, and automate the transition to Proxmox — minimizing both downtime and risk.

🧩 Why "Prosmox"?

The name Prosmox is a blend of:

The Greek word "πρός" (pros), meaning towards or in the direction of
And "mox", a nod to Proxmox VE, the powerful open-source virtualization platform

Together, they reflect the essence of the project: a smart migration journey towards Proxmox.

🧠 What I Learned

Deep understanding of AWS and Azure service metadata, billing, and architecture.
Proxmox API capabilities, including VM creation, cloud-init, and storage/network planning.
Best practices for minimal-downtime infrastructure migration.
Designing event-driven, scalable systems using FastAPI, Python, and Jinja templating.
Integrating observability tools to track and simulate migration paths.

🛠️ How I Built It

Data Collection Agent: Uses AWS and Azure APIs to extract current infrastructure details (instances, storage, IPs, services).
AI Recommendation Engine: Evaluates multiple migration scenarios using cost analysis, dependency graphs, risk scoring, and downtime simulations.
FastAPI Backend: Exposes endpoints to trigger plans, fetch reports, and control migration.
Jinja2 Templates: Dynamically render HAProxy and Proxmox configs per scenario.
Web UI (WIP): Displays reports, risk scores, and proposed timelines interactively.
WHMCS Hook (Optional): Enables integration into hosting panels for automated provisioning.

⚔️ Challenges Faced

Normalizing metadata across AWS and Azure — wildly different APIs and terminologies.
Designing accurate dependency graphs between cloud services and resources.
Maintaining data integrity and rollback paths during migrations.
Creating a unified model for cloud vs. on-prem resource capabilities (CPU, disk IOPS, network).
Keeping the system flexible and extensible without hardcoding provider-specific logic.