Hi everyone,
Full disclosure: I'm the developer of these plugins. I'm sharing them here because this community knows Proxmox better than anyone, and I'd like honest feedback from people who run it.
The idea: a lot of small hosting providers, labs and resellers already run WordPress for their site and billing. I wanted a way for customers to manage their own containers and VMs from that same site, without giving them access to the Proxmox interface itself.
There are two plugins that work together.
urZONE PVE Core is the engine. It talks to the Proxmox API and draws a customer panel inside WordPress.
- Containers and VMs with live status and resource charts
- Plans mapped to WordPress user roles (Starter, Business, Pro Reseller, Agency Reseller, Demo, Admin), each with a limit on how many instances a user can have
- Instance ownership, so each customer only sees and manages their own
- Snapshots on every plan, with Clone and Template on the higher plans
- Per-instance ceilings for CPU cores, memory and disk
- A public demo with automatic cleanup
- Multisite support
urZONE PVE Settings is the setup screen for it.
- Enter your API URL, user, token ID and token secret, then save and test the connection from the WordPress admin
- Set defaults for node, storage, network bridge, container template storage and ISO storage
- SSL verification, refresh interval and size limits
- It writes the values into wp-config.php for you and keeps a backup of the previous file, or shows the lines to paste yourself if the file isn't writable
Both have a free edition. The paid editions add a plans page in Core, where you change how many panels each plan gets, and a web shell tab and license tab in Settings. The web shell needs a separate bridge service that you set up yourself.
What I'd love to hear from you:
1. What permissions would you give a Proxmox API token used by a plugin like this? I want the recommended setup to follow least privilege.
2. Are there node, storage or network settings I'm missing that you'd expect in a panel like this?
3. Is there anything here that would make you uncomfortable running it in production?
Happy to answer questions about how it works. Thanks for reading, and for any feedback.
Full disclosure: I'm the developer of these plugins. I'm sharing them here because this community knows Proxmox better than anyone, and I'd like honest feedback from people who run it.
The idea: a lot of small hosting providers, labs and resellers already run WordPress for their site and billing. I wanted a way for customers to manage their own containers and VMs from that same site, without giving them access to the Proxmox interface itself.
There are two plugins that work together.
urZONE PVE Core is the engine. It talks to the Proxmox API and draws a customer panel inside WordPress.
- Containers and VMs with live status and resource charts
- Plans mapped to WordPress user roles (Starter, Business, Pro Reseller, Agency Reseller, Demo, Admin), each with a limit on how many instances a user can have
- Instance ownership, so each customer only sees and manages their own
- Snapshots on every plan, with Clone and Template on the higher plans
- Per-instance ceilings for CPU cores, memory and disk
- A public demo with automatic cleanup
- Multisite support
urZONE PVE Settings is the setup screen for it.
- Enter your API URL, user, token ID and token secret, then save and test the connection from the WordPress admin
- Set defaults for node, storage, network bridge, container template storage and ISO storage
- SSL verification, refresh interval and size limits
- It writes the values into wp-config.php for you and keeps a backup of the previous file, or shows the lines to paste yourself if the file isn't writable
Both have a free edition. The paid editions add a plans page in Core, where you change how many panels each plan gets, and a web shell tab and license tab in Settings. The web shell needs a separate bridge service that you set up yourself.
What I'd love to hear from you:
1. What permissions would you give a Proxmox API token used by a plugin like this? I want the recommended setup to follow least privilege.
2. Are there node, storage or network settings I'm missing that you'd expect in a panel like this?
3. Is there anything here that would make you uncomfortable running it in production?
Happy to answer questions about how it works. Thanks for reading, and for any feedback.