Best Practices

Launch gradually

Start with a small number of plans, templates, and trusted beta users. Expand only after provisioning, reinstalling, billing actions, and support workflows have been tested repeatedly.

Template practices

• Keep separate templates for each supported OS version
• Test every template through VMNexor before selling it
• Document account and password behaviour per template
• Do not edit production templates without cloning and testing first
• Retire broken or old templates instead of patching them blindly

Plan practices

• Keep early plans simple
• Avoid too many template choices at launch
• Use clear reinstall rules
• Do not mix risky Windows and Linux assumptions on the same plan
• Test each plan with a disposable service

Networking practices

• Match IP pools to the real node routing design
• Test gateway, external IP, and DNS connectivity inside every OS family
• Document whether a plan uses bridged or routed networking
• Avoid selling routed /32 plans until each template has been validated

Storage practices

• Use consistent storage names where possible
• Monitor free disk capacity
• Test clone and delete behaviour
• Use shared template storage if it simplifies cluster operations
• Keep backups of critical shared configuration

Billing practices

• Treat billing systems as adapters, not the infrastructure source of truth
• Map products carefully to VMNexor plans
• Test create, suspend, unsuspend, terminate, and reinstall actions
• Keep billing status and VMNexor service state reconciled
• Do not let billing systems talk directly to Proxmox

Operational practices

• Review failed automation quickly
• Keep queue and scheduler services monitored
• Record manual recovery actions
• Back up the VMNexor database
• Back up shared environment and license files
• Restrict admin access to trusted staff

Customer support practices

• Ask for service ID, template, node, and exact error text
• Check VMNexor state before Proxmox state
• Avoid destructive actions without customer confirmation
• Use disposable services to reproduce template issues
• Keep common fixes documented

Release practices

• Test updates away from production first where possible
• Confirm signed update and integrity requirements are present
• Check sudo permissions for update scripts
• Keep rollback paths available
• Verify services after every update

Minimum public launch checklist

• Homepage and docs are live
• Customer portal works
• Admin portal works
• At least one Linux template is fully tested
• At least one Windows template is fully tested if Windows is sold
• Billing adapter lifecycle actions pass
• Support process is ready
• Backups are configured