I suppose it's the elastic nature of the pricing that you find complex? I can't disagree with you, it is less straightforward than flat monthly plans. However it is what litteraly thousands of developers have been asking us for over the last year. Our previous pricing was focused on simplicity... but ended up sweeping the reality of our product under tbe rug.
I think you're right that we don't explain enough on the pricing page. Our concern was text overload., but there's probably a balance to be found.
What about the content - any opinion on our actual pricing?
Not the elastic nature, more that it takes longer than it should to understand what the drivers are. If everything is related to memory and memory only goes up in 32MB chunks, have a slider/radio/dropdown/whatever that moves memory and related resources simultaneously, with a per-hour and monthly charge that's auto-updated.
I think it's important to note that the page is about pricing, but 99% of the info isn't a price. Above the fold there's only one price, which you have to use in calculating the actual value yourself. Way, way down are the examples, but they might or might not represent what a customer's workload will look like, so they still don't really have what they came to the page for. Getting the customer their own price, super-fast, (assuming it's a good one) is the path to showing why you guys are so fantastic.
What you're getting is the ability to deploy linux containers with very fine-grained control over resource allocation. Maybe you're using redis as a job queue, or to hold a handful of counters. Maybe you're running nginx to serve static assets with custom rewrite rules. You can run it dotCloud and pay peanuts - knowing that you're one "dotcloud scale" away from all the gigabytes of ram you can eat.
But that's just my gut reaction. What you really need is a webdesigner who can lay down an approachable visualization for such a complex pricing scheme (which will probably involve sliders, and also big honking tooltips).
As for your actual pricing - I don't know. It wasn't obvious from the page what a small/medium/large deployment would cost and I didn't bother to fire up excel to figure out a number that you should absolutely spoon-feed me.
I saw them but those are but single datapoints (and apps seems to vary wildly in requirements). would be handy to have a slider so you could answer the 'what-ifs'.
also, was an early beta signup, really liked dotcloud, but have to agree this pricing is pretty complicated :(
Yes, but as lalmalang said, these are not very useful and not discoverable at all.
I don't want to click through 5+ random scenarios to perhaps find one that comes close to what I have in mind.
Well, at the risk of repeating myself. You seem to be generating revenue already, so I would seriously look into hiring a designer for this (or make a contest or such).
My gut feeling is that you're so deep into all this (which is generally good!) that you have a hard time reviewing it through the eyes of a first-time visitor.
I suppose it's the elastic nature of the pricing that you find complex? I can't disagree with you, it is less straightforward than flat monthly plans. However it is what litteraly thousands of developers have been asking us for over the last year. Our previous pricing was focused on simplicity... but ended up sweeping the reality of our product under tbe rug.
I think you're right that we don't explain enough on the pricing page. Our concern was text overload., but there's probably a balance to be found.
What about the content - any opinion on our actual pricing?