What is our primary use case?
It's an open-source solution for virtualizing. It’s a server virtualization software. Everything that's work or life is managed by Proxmox.
How has it helped my organization?
It's a tool that opens doors so that we don't need to pay any fees. This is a good thing. It's helping us to use its resources with the server we have. If there's none, especially it's increasing productivity, it's a handy tool to help manage things.
What is most valuable?
The virtualization is good.
It’s open-source and free to use.
The product helps us utilize resources better.
Proxmox is a good solution for on-premise managing service and with machines.
The solution is easy to set up.
What needs improvement?
We’d like them to ensure there is an easy migration towards the cloud, which is where we’re moving. Right now, we are on-premises. We’d like to have a nice, simple interface to synchronize through the cloud.
It might be interesting to have the ability to integrate with other cloud solutions.
For how long have I used the solution?
We’ve used the solution for the last five years now. It’s been a while.
What do I think about the stability of the solution?
I haven’t had any issues with stability just yet. We haven’t had any downtime from anything Proxmox has caused. There are no bugs or glitches. It doesn’t crash or freeze.
What do I think about the scalability of the solution?
It’s quite a scalable solution. We are happy with how much it can expand. It’s easy to add a new node.
We currently have three people using the product. They administer the solution.
We do not plan to increase usage right now. We already use it 100% in the places we can. We can’t use it any more than we do.
How are customer service and support?
I’ve never used customer service in the past. I can’t speak to how helpful or responsive they are.
Which solution did I use previously and why did I switch?
We did previously work with Citrix. We moved to this solution for a better user interface and stability. Citrix also changed the way it handled licensing. We preferred Proxmox’s licensing approach.
How was the initial setup?
The initial setup is quite straightforward. It isn't that complex. I’d rate it at a one or a two in terms of complexity, on a scale from one to five.
The deployment depends a bit on how many nodes or servers you have. You want to get into the cluster. This depends on the month's amount of time, however, we have half a day for a server. For me, it takes a little bit of time. You need a half-day per node, per server. Maybe even less.
While maintenance is always necessary, I would say we would invest more or less a day a month just to maintain it and that would entail checking logs and so on. It doesn’t require heavy maintenance.
What about the implementation team?
We handled the initial setup completely in-house. We didn’t need any outside assistance from any integrators or consultants.
What was our ROI?
ROI is hard to calculate. It’s a free solution and, as we do everything in-house, we have to measure the time we need to actually dominate the solution, however, it's really very little time.
What's my experience with pricing, setup cost, and licensing?
This solution is open-source. We use only open-source solutions without any services. We handled everything in-house. There are no licensing costs and no extra fees.
What other advice do I have?
I’m a customer and an end-user.
We’re about to migrate over to the 7.2 version from our current version. We have two clusters with servers we are managing with Proxmox.
I’d advise potential new users to just check it out and try it. The best thing to do is to set up a small installation or maybe mount it on a virtual box and play with it to see what t can do. It’s quite easy to start with.
I’d rate the solution a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.