XCP-ng pricing
-
And if simplicity is the winner, no tier system, then some kind of market-y number around $200 per socket per year is good.
Best support for all!Example:
All support is $195 / socket / year.
-
@obsolesce so you would favor the existing support model that many businesses already do.
Per socket or tiers of support.
-
@dustinb3403 said in XCP-ng pricing:
@obsolesce so you would favor the existing support model that many businesses already do.
Per socket or tiers of support.
Well, if someone has a server with 4 sockets, and each CPU has 32 physical cores, and they are running some crazy system or number of VMs... that has the potential to be one hell of a support case.
Not necessarily tiers, but it covers the kind of support you may expect.
That everyone no matter what the use case is, should pay the same price of support, I think, isn't 100% fair.
-
@obsolesce said in XCP-ng pricing:
And if simplicity is the winner, no tier system, then some kind of market-y number around $200 per socket per year is good.
Best support for all!Example:
All support is $195 / socket / year.
I also support this method, even taking into account for what I said above... It's not expensive, but not so cheap it makes the product and/or support look bad.
I think it's fair, and if/when we would run the entire infrastructure with XCP-ng, that's reasonable enough we'd pay it to cover all of our hosts.
-
@obsolesce said in XCP-ng pricing:
@dustinb3403 said in XCP-ng pricing:
@obsolesce so you would favor the existing support model that many businesses already do.
Per socket or tiers of support.
Well, if someone has a server with 4 sockets, and each CPU has 32 physical cores, and they are running some crazy system or number of VMs... that has the potential to be one hell of a support case.
Not necessarily tiers, but it covers the kind of support you may expect.
That everyone no matter what the use case is, should pay the same price of support, I think, isn't 100% fair.
And that is my argument as well for the pricing I proposed.
The customers that exist with massive servers paying for support would end up with a system like you describe would essentially get support at little to no cost compared to a well designed and balanced support plan.
-
@dustinb3403 said in XCP-ng pricing:
@obsolesce said in XCP-ng pricing:
@dustinb3403 said in XCP-ng pricing:
@obsolesce so you would favor the existing support model that many businesses already do.
Per socket or tiers of support.
Well, if someone has a server with 4 sockets, and each CPU has 32 physical cores, and they are running some crazy system or number of VMs... that has the potential to be one hell of a support case.
Not necessarily tiers, but it covers the kind of support you may expect.
That everyone no matter what the use case is, should pay the same price of support, I think, isn't 100% fair.
And that is my argument as well for the pricing I proposed.
The customers that exist with massive servers paying for support would end up with a system like you describe would essentially get support at little to no cost compared to a well designed and balanced support plan.
Right, a socket-based server pricing is fine for now, and could change in 5-10 years and go to core based...
Really, core based is best NOW..... but the general population can't figure out how to do core based pricing for some reason, so I can see that being a put-off.
-
@dustinb3403 said in XCP-ng pricing:
At $1000/host/year I wouldn’t purchase support as it’s just insanely expensive
This is not expensive.
-
@jaredbusch said in XCP-ng pricing:
@dustinb3403 said in XCP-ng pricing:
At $1000/host/year I wouldn’t purchase support as it’s just insanely expensive
This is not expensive.
It is if you consider the pricing that already exists from xenserver.org which is around $350 per socket.
But my pricing is what I would think of expensive, give me your answers to the questions above.
-
@jaredbusch said in XCP-ng pricing:
@dustinb3403 said in XCP-ng pricing:
At $1000/host/year I wouldn’t purchase support as it’s just insanely expensive
This is not expensive.
When comparing to VMWare support pricing, it's far from expensive, true.
But do you think XCP-ng wants to compete with VMWare support?
We wouldn't use VMWare becasue it's WAY too expensive... so even at half the price, too expensive.
Something like $200 per socket is fair... if it's too much, people may just go with VMWare or Hyper-V instead.
VMWare's basic is like $2k per host per year. (for 2 cpus)
$400 would be a lot cheaper, and in comparison very cheap. Where to start is a slippery slope.
I could see $300 / socket / year... that's also very reasonable.
-
@dustinb3403 said in XCP-ng pricing:
@jaredbusch said in XCP-ng pricing:
@dustinb3403 said in XCP-ng pricing:
At $1000/host/year I wouldn’t purchase support as it’s just insanely expensive
This is not expensive.
It is if you consider the pricing that already exists from xenserver.org which is around $350 per socket.
But my pricing is what I would think of expensive, give me your answers to the questions above.
These answers are just worthless.
Expensive is a relative value to all people.
The cost of this service should be based on what the market will support.If the closest competitor is $350 per socket, then that means that you start there and figure out what differentiates your service from the competitor and if that makes it worth more or less.
Then you go and calculate loss leader values based on attempting to enter a market and disrupt existing competitors.
The thing you do not do is ask the fucking internet.
Especially people with no business skills to tell you how much to charge for your services.
-
@jaredbusch said in XCP-ng pricing:
@dustinb3403 said in XCP-ng pricing:
@jaredbusch said in XCP-ng pricing:
@dustinb3403 said in XCP-ng pricing:
At $1000/host/year I wouldn’t purchase support as it’s just insanely expensive
This is not expensive.
It is if you consider the pricing that already exists from xenserver.org which is around $350 per socket.
But my pricing is what I would think of expensive, give me your answers to the questions above.
These answers are just worthless.
Expensive is a relative value to all people.
The cost of this service should be based on what the market will support.If the closest competitor is $350 per socket, then that means that you start there and figure out what differentiates your service from the competitor and if that makes it worth more or less.
Then you go and calculate loss leader values based on attempting to enter a market and disrupt existing competitors.
The thing you do not do is ask the fucking internet.
Especially people with no business skills to tell you how much to charge for your services.
Dont get pissy with me, I didn't create the questions.
-
@JaredBusch what do you think support from the devs would be worth?
Do you think that the current plan (as far as I've seen) being a flat cost per host is a good way to go about it?
-
I can't see myself asking my boss for $1000 per year for something I likely wont ever use.
I feel like a price per ticket or hourly rate is more realistic for this type of support, but at the same time a single ticket could easily cost $1000 if being charged per hour?
I don't know. I've never paid for support unless it was bundled with a license that I had to purchase.
-
@bnrstnr said in XCP-ng pricing:
I can't see myself asking my boss for $1000 per year for something I likely wont ever use.
I feel like a price per ticket or hourly rate is more realistic for this type of support, but at the same time a single ticket could easily cost $1000 if being charged per hour?
I don't know. I've never paid for support unless it was bundled with a license that I had to purchase.
This is the rub for SMB. They pretty much "buy" updates and get free support. And enterprises (at least according to Scott - I have no first hand experience) Pay for support and may or may not get free updates.
-
@bnrstnr said in XCP-ng pricing:
I can't see myself asking my boss for $1000 per year for something I likely wont ever use.
And here is the rub - The XCP-ng guys can't survive on only open tickets.. they need to sell support contracts to ensure income. At least that's my guess.
-
@dashrender said in XCP-ng pricing:
And here is the rub - The XCP-ng guys can't survive on only open tickets.. they need to sell support contracts to ensure income. At least that's my guess.
Right, and the same exact thing applies to XOA, it seems ridiculously expensive for SMB, but is probably easily justified for enterprises. They're seemingly pricing it to land a few big spenders to pay the bills and they will continue to provide enough support in the forums to keep the small guys happy too.
-
@dashrender said in XCP-ng pricing:
@bnrstnr said in XCP-ng pricing:
I can't see myself asking my boss for $1000 per year for something I likely wont ever use.
And here is the rub - The XCP-ng guys can't survive on only open tickets.. they need to sell support contracts to ensure income. At least that's my guess.
But comparing this to the existing XOA pricing they're essentially trying to get every customer of theirs to purchase a Ferrari for each of em.
I'm all for support, but at a realistic cost. The $6000 a year for the XOA features that I was using for free previously would immediately eliminate that solution in the SMB world.
And while I understand that "support costs a lot" this isn't that support needs to be 24/7 phone and email with SSH access to a client.
You'd easily be able to setup tiers of support.
Tier 1 - Basic 8-5 hours phone & email support with 12 hour response window.
Tier 2 - Standard 8-5 hours phone & email support with 4 hour response windows
Tier 3 - Pro 24/7 hours " " with a 4 hour response windowetc.
-
IE you would setup a per socket or core license costs and then apply a support level fee on top of it.
This way everyone would pay the same per socket/core rate and get to choose the level of support that they want.
You could even have minimums of support based on environment size requirements.
1-4 hosts with less than 32 cores - Tier 1 support
4-8 hosts - Tier 2 supportetc
-
Going along the idea of the per socket/core and tiers if you opt to not add on higher support tiers you'd automatically fall into the Tier 1 category.
Unless of course there were support minimums based on the number of sockets or cores.
-
Going on another point, have an emergency rate for people to opt to not purchase support at all. Simply have a flat "Call in rate" for the first hour.
Something like $500 for the first hour and then $250 per hour after. Just pulling numbers out of the air.
This would then highlight to the customer that support is key if there is a critical issue that costs more than what a support contract would cost regularly.
