Proxmox VE Client Self-Service Portal Developer — Proven Experience Required

We are looking for an experienced developer or small team to build a secure VPS client self-service portal integrated with a Proxmox VE cluster. This is not a generic web development project. Proven experience working directly with the Proxmox VE API is a key requirement. ## Project objective The portal will allow each customer to securely manage only the VPS instances assigned to their account, without giving them direct access to the Proxmox administration interface. Our current infrastructure includes a three-node Proxmox VE cluster using QEMU virtual machines, HA, and VM migrations between nodes. ## MVP scope ### Customer portal Customers must be able to: * Log in securely. * View only their assigned VPS instances. * See VPS status and assigned resources. * View basic CPU, memory, disk, and network metrics. * Start a VPS. * Perform a graceful shutdown. * Stop a VPS, with a clear warning. * Reboot a VPS. * Access a secure temporary noVNC console. * View the status and result of submitted actions. * View a basic activity history. ### Administration portal Administrators must be able to: * Create and manage customer accounts. * Enable or disable customer access. * Assign one or more VPS instances to each customer. * Enable or disable specific actions per customer. * Review audit logs. * Review integration errors and failed operations. ## Proxmox integration requirements The backend must: * Integrate through the official Proxmox VE API. * Support a multi-node cluster. * Locate a VM correctly after migration between nodes. * Handle Proxmox asynchronous tasks and UPIDs. * Poll or process the real result of each task. * Prevent conflicting actions while another operation is running. * Avoid showing stale or assumed VM states. * Handle temporary API or cluster connectivity failures. * Use secure API tokens and least-privilege permissions. * Never expose Proxmox administrative credentials to customers. The noVNC implementation must securely handle: * VM-specific authorization. * Temporary console tickets. * Proxmox `vncproxy`. * WebSocket connectivity. * Ticket expiration. * VM migration between cluster nodes. ## Security requirements Customer isolation must be enforced by the backend, not only by the frontend. The solution must include: * Role-based access control. * Strict customer-to-VPS authorization. * Secure session management. * Protection against common web vulnerabilities. * Secure secret management. * Rate limiting for sensitive operations. * HTTPS support. * Complete audit logging of user actions. * No hardcoded credentials. ## Preferred architecture We are open to technical recommendations. Possible technologies include: * Node.js and TypeScript or Python with FastAPI. * React or Next.js. * PostgreSQL or MySQL. * Docker and Docker Compose. * REST APIs. * Linux. * GitHub or GitLab. The selected developer must explain and justify the proposed architecture. ## Deliverables * Complete backend and frontend source code. * Repository hosted under an account controlled by us from the beginning. * Database schema and initialization scripts. * Docker-based deployment or an equivalent documented installation process. * Technical architecture documentation. * Installation and administration documentation. * Example configuration files without real credentials. * Deployment in a test environment. * Assistance with the initial production deployment. * Automated or documented tests for critical functions. * Bug-fix warranty period after delivery. * Full rights to use, maintain, and modify the delivered source code. ## Out of scope for the initial MVP The following features may be added later, but are not required in the first version: * Automated VPS provisioning. * Operating system reinstallation. * Customer-managed snapshots. * Backup management. * Billing and payment integration. * Automatic service suspension. * Resource upgrades. * Support ticketing. * WHMCS integration. The architecture should allow these capabilities to be added in future phases. ## Working model We prefer milestone-based development: 1. Architecture and technical design. 2. Small paid Proxmox integration proof of concept. 3. MVP development. 4. Testing and production deployment. 5. Optional ongoing support and future development. Communication should be clear and regular. We expect progress demonstrations at the end of each milestone. ## Mandatory first screening requirement Please provide concrete evidence of previous work with Proxmox VE. Acceptable evidence includes: * A short video demonstration. * Screenshots with sensitive information hidden. * A live demo. * A public repository or relevant code sample. * A verifiable customer reference. * A detailed technical explanation of a real Proxmox project you personally implemented. We understand that previous projects may be confidential. Sensitive information can be removed or anonymized. Generic proposals that do not demonstrate real Proxmox VE experience will not be considered. Please also answer: 1. What Proxmox VE integrations have you previously developed? 2. Have you worked with multi-node clusters, HA, and VM migrations? 3. How would you track asynchronous Proxmox tasks using UPIDs? 4. How would you guarantee that one customer can never access another customer’s VPS? 5. How would you implement secure noVNC access? 6. What architecture and technology stack do you recommend? 7. What timeline and milestone structure do you propose? 8. What support and warranty do you provide after delivery?