Stating all of the prices as "per 30 days" has a bad smell to it.
Why not state them as monthly if that was the intent?
Or why not state it as hourly or annually if the intent is to slice it that way?
The only reasons I can think to state it per 30 days is that there is a dark pattern for revenue optimization hidden in there. Don't be different for the sake of being different when it comes to pricing, especially on something where folks are trying to compare your pricing to competitors.
I also think the "meh" acronym for memory hours is pretty unfortunate given the negative connotations. "meh" is about the last thing you want people to associate with your service.
Prices are stated per 30 days to make them easier to evaluate. Since actual pricing is per use and even pro-rated to the second the numbers would be really small and not really helpful otherwise.
It's semi-common in the cloud space, although some just go ahead and use the word "month" anyway, and then in the fine print define a month as equalling 720 hours. Some of AWS's pricing calculators do that, for example.
Comments
Stating all of the prices as "per 30 days" has a bad smell to it.
Why not state them as monthly if that was the intent?
Or why not state it as hourly or annually if the intent is to slice it that way?
The only reasons I can think to state it per 30 days is that there is a dark pattern for revenue optimization hidden in there. Don't be different for the sake of being different when it comes to pricing, especially on something where folks are trying to compare your pricing to competitors.
I also think the "meh" acronym for memory hours is pretty unfortunate given the negative connotations. "meh" is about the last thing you want people to associate with your service.
Prices are stated per 30 days to make them easier to evaluate. Since actual pricing is per use and even pro-rated to the second the numbers would be really small and not really helpful otherwise.
But only in September, April, June and November!
It's semi-common in the cloud space, although some just go ahead and use the word "month" anyway, and then in the fine print define a month as equalling 720 hours. Some of AWS's pricing calculators do that, for example.