Proxmox pricing
-
I seem to be missing something. With the pricing structure above, it seems to make more sense to stick with Hyper-V and the numerous other backup software products on the market at cheaper price points.
If in an SMB with fewer than 10 VM's, Hyper-V with Veeam Free could be a better, lower priced solution...
If going a little larger, while not every feature is available, Vmware ESXi essentials starts to look similar in pricing.
-
@pmoncho said in Proxmox pricing:
I seem to be missing something. With the pricing structure above, it seems to make more sense to stick with Hyper-V and the numerous other backup software products on the market at cheaper price points.
If in an SMB with fewer than 10 VM's, Hyper-V with Veeam Free could be a better, lower priced solution...
If going a little larger, while not every feature is available, Vmware ESXi essentials starts to look similar in pricing.
None of that pricing is required though, Only if you want support. JB has recently posted a thread with instructions on how to get you PM setup with the open source repos and how to remove the nag screens.
Personally, the hassles of Hyper-V aren't really worth it anymore, not sure they ever really were. If you have a large environment, Hyper-V might make sense, but a single host - talk about a nightmare ensuring you can access the Hyper-V host itself if your AD vm's are all down.
-
@Dashrender said in Proxmox pricing:
Hyper-V host itself if your AD vm's are all down.
Don't join your Hyper-V hosts to the domain if you have only a single host and single DC.....
-
@DustinB3403 said in Proxmox pricing:
@JaredBusch From their FAQ document
3.4. How many subscriptions do I need? You will need a subscription for each physical server or virtual instance with Proxmox Backup installed. Each subscription key is bound to the unique "Server ID" of your server/instance.Just adding this for clarity: This is where you run the backup server, not the guests that are being backed up.
-
Also worth noting, the backup server is GPLv3 licensed, so you could run it without support if you wanted.
-
Just for some comparison on a similar product, below is xcp-ng (the xen hypervisor) paid support options:
-
@Pete-S said in Proxmox pricing:
Just for some comparison on a similar product, below is xcp-ng paid support options:
This is just for the hypervisor and not the management/backup solution. Xen Orchestra pricing is additional just like with Proxmox. Backup.
-
@DustinB3403 said in Proxmox pricing:
@Pete-S said in Proxmox pricing:
Just for some comparison on a similar product, below is xcp-ng paid support options:
This is just for the hypervisor and not the management/backup solution. Xen Orchestra pricing is additional just like with Proxmox.
Yes, good point. I was just editing my post for clarification as you posted this.
-
@DustinB3403 said in Proxmox pricing:
Also worth noting, the backup server is GPLv3 licensed, so you could run it without support if you wanted.
ProxMox is AGPL so all of the scripts that anyone creates to disable the nagging screen, etc need to be made available to anyone using the tool on your network. Just a heads up to anyone using it.
-
@stacksofplates said in Proxmox pricing:
ProxMox is AGPL so all of the scripts that anyone creates to disable the nagging screen, etc need to be made available to anyone using the tool on your network.
This part is a bit confusing to me with how you stated it. Presumably anyone setting up and managing Proxmox on the LAN would already have this information. But in addition to that @JaredBusch has already posted the information
abovein a separate thread, publicly. -
@stacksofplates If what you are referring to is this piece of the AGPL license
The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.The nag screen changes are already public domain has @JaredBusch pulled them from another website. This also doesn't require that @JaredBusch or anyone else publish the source code they have on their LAN since the LAN is private, only if the source system was publicly hosted would publishing of the source code be required.
In addition to that, one doesn't need to publish the entire source code for their modified version, but only the changes to it. Which has already been done by numerous others.
-
@JaredBusch just in case you missed all the other tags.
-
@IRJ said in Proxmox pricing:
@JaredBusch just in case you missed all the other tags.
He'd actually only get tagged once iirc. But yeah
-
@DustinB3403 said in Proxmox pricing:
@IRJ said in Proxmox pricing:
@JaredBusch just in case you missed all the other tags.
He'd actually only get tagged once iirc. But yeah
Per post, not per topic.
-
@JaredBusch Yeah, not multiple times per post like @IRJ was implying.
-
@DustinB3403 said in Proxmox pricing:
@stacksofplates If what you are referring to is this piece of the AGPL license
The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.The nag screen changes are already public domain has @JaredBusch pulled them from another website. This also doesn't require that @JaredBusch or anyone else publish the source code they have on their LAN since the LAN is private, only if the source system was publicly hosted would publishing of the source code be required.
In addition to that, one doesn't need to publish the entire source code for their modified version, but only the changes to it. Which has already been done by numerous others.
You still need to publish it for the LAN. That was my point. You need to make it available to any users on your LAN.
Section 13 states:
Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source
A LAN is a computer network and they are accessing the service through the network. So while your don't need to provide the full source (which I never stated) you do need to provide the changes to the users on the network.
-
This was discussed somewhere else a long time ago. But same with the Asterisk, XenOrchestra, etc. Any scripts that modify or add to installations needs to be made available. So your script for XO is public, but users on your LAN need a link or some way of knowing it exists (if it changes or modifies anything, I forget if it does or not).
-
@stacksofplates said in Proxmox pricing:
but users on your LAN need a link or some way of knowing it exists
Users of the things running on it do not.
-
@JaredBusch said in Proxmox pricing:
@stacksofplates said in Proxmox pricing:
but users on your LAN need a link or some way of knowing it exists
Users of the things running on it do not.
If they're interacting with the hypervisor. Not like windows users. But anyone using the hypervisor would. Should have been a little clearer.
