Short answer: All three appear on the same pricing page, and they are not alternatives [S1]. A configuration is the thing being priced: each row binds a vCPU count, a memory size, a bandwidth allowance and a storage size to one set of figures [S1]. The hour is the meter, because an hourly column is printed on every compute table I could read [S1]. The month is a printed column on the Cloud Compute tables, while the VX1 tables carry an hourly column with no monthly column beside it [S1]. The same page names 672 hours as a ceiling it says does not bind its VX1 instances [S1]. Read in that order: choose a plan row, let an hourly figure accrue against it, then check whether that family's card also prints a monthly figure [S1]. I quote only the numbers printed on the pricing page read on 2026-11-11, I derive no conversion rule from them, and this page stays on that one question [S1].
The pricing page I read on 2026-11-11 was reachable through a read-only rendering channel [S1]. A direct request with the site's standard command-line user agent returned HTTP 403 and a challenge page instead of the plan tables [U1]. Both observations are recorded; the figures below come from the readable rendering, not from the blocked response [S1][U1].
The Cloud Compute section prints two money columns, headed Monthly Price and Hourly Price, for its Regular Performance rows and for the AMD Pricing and Intel Pricing rows under High Performance [S1]. The VX1 section prints a single money column, headed Hourly Price, for its General Purpose and Memory Optimized rows [S1]. That difference is visible on the page itself, before any interpretation is added [S1].
Here are four rows exactly as that rendering prints them, with the source marker in the last cell [S1]:
| Family | vCPU | Memory | Bandwidth | Storage | Monthly Price | Hourly Price | Source |
|---|---|---|---|---|---|---|---|
| Regular Performance | 1 | 2 GB | 2.00 TB | 55 GB | $10.00/mo | $0.015/hr | [S1] |
| Regular Performance | 2 | 4 GB | 3.00 TB | 80 GB | $20.00/mo | $0.03/hr | [S1] |
| High Performance AMD | 1 | 1 GB | 2.00 TB | 25 GB | $6.00/mo | $0.009/hr | [S1] |
| VX1 General Purpose | 2 | 8 GB | 5.00 TB | Block Storage | no monthly column | $0.060/hr | [S1] |
One row on the Cloud Compute table also carries an IPv6 Only label beside its hourly figure, and that qualifier belongs to the row rather than to the whole table [S1]. The VX1 General Purpose row quoted above prints no monthly figure in that rendering [S1].
Nothing on the readable tables prices a vCPU, a gigabyte of memory or a terabyte of transfer as a separate line item [S1]. Those four values are attributes of one row, and the money columns sit at the end of that same row [S1]. Changing the configuration therefore means selecting a different row, not adding a multiplier to an existing one [S1].
A comparison from the printed rows makes the point sharper. Regular Performance with 1 vCPU and 2 GB of memory prints $10.00/mo for the month and $0.015/hr for the hour [S1]. High Performance AMD with 1 vCPU and 2 GB of memory prints $12.00/mo for the month and $0.018/hr for the hour [S1]. The vCPU count and the memory size match; the family, the bandwidth allowance, the storage size and both money figures do not [S1]. So the configuration that gets priced is the whole plan row, family included [S1].
The hourly column is the one column present on both layouts [S1]. It appears on the Cloud Compute tables beside the monthly column, and it appears alone on the VX1 tables [S1]. That is why the fork between an hourly answer and a monthly answer is a false one: the page prints an hourly figure in both cases, and prints a monthly figure in one of them [S1].
The page does not print a sentence converting one column into the other [S1]. I checked the readable tables for a stated hour count, a rounding rule or a formula linking the two money columns and found none [S1]. I am not going to supply one from arithmetic, because a formula I invent would be an estimate dressed as a fact [S1]. A public plan endpoint returned HTTP 200 on 2026-11-11 and its hourly values differ from the printed figures on several rows [S2]. I report that mismatch and quote no number from that endpoint [S2]. Which of the two channels a bill follows is not settled by anything I read today [S2].
Take the Regular Performance row with 1 vCPU, 2 GB of memory, 2.00 TB of bandwidth and 55 GB of storage [S1]. It prints $10.00/mo and $0.015/hr [S1]. A reader who wants to know how this plan is charged can answer three separate questions from that row alone: what bundle is being priced, what hourly figure is attached to it, and what monthly figure is printed beside it [S1]. None of those questions requires a calculator [S1].
The same row also shows what the page declines to say. It prints no definition of an hour, no statement of when accrual begins or ends, and no threshold at which the monthly column takes over [S1]. Those are absent from the tables I read, and I mark them as absent rather than filling them in [S1]. The billing FAQ I opened lists payment methods, account credit, tax, invoice format, declined cards and promotional codes, and carries no hourly or monthly cap wording [S4]. The billing documentation index lists separate articles on payments, account limits, bandwidth usage, payment history and that FAQ [S3].
So the reading procedure is short and stays inside the page. Locate the family heading, find the row matching the bundle, copy the hourly figure, copy the monthly figure where one is printed, copy any row qualifier such as IPv6 Only, and write down the date and the channel used [S1]. That produces a quote another person can re-read, without producing a number the page never printed [S1].
The VX1 section carries a sentence on how those instances are billed [S1]. It charges them for the hours they run in a month, and it names 672 hours as a ceiling that does not apply to them [S1]. I am reporting that sentence as a statement on the page, not as a description of the vendor's internal ledger [S1].
Its consequence for this question is narrow and useful. On the VX1 tables there is no monthly column to copy, so a reader asking for a monthly figure has no printed one to take from those rows [S1]. On the Cloud Compute tables there is [S1]. A single answer to the hourly, configuration or monthly question would erase that difference, and the difference sits on the page in plain sight [S1].
I read the 672-hour phrase as a contrast with the rest of the page, and I label that as an inference [S1]. The chain is short: the phrase says VX1 is not capped at that hour count, the Cloud Compute tables print a monthly column that the VX1 tables lack, and so the two layouts describe different ceiling arrangements [S1]. I do not assert what the ceiling is for any specific plan, because the tables state no ceiling value and the billing FAQ states none either [S1][S4].
The direct command-line request to the pricing page returned HTTP 403 with a challenge page, so that response supplies no plan text here [U1]. A billing documentation path I tried returned a page saying it could not be found, and it supplies nothing either [U2]. The readable rendering of the pricing page is the basis for every figure printed above [S1].
The public plan endpoint is a machine-readable source rather than a page of printed prices [S2]. I used it only to establish that a discrepancy exists, and I quote none of its values [S2]. Where two official channels disagree, copying either one silently would be the mistake, so the disagreement is recorded and left unresolved [S2].
No conversion rule, rounding rule or ceiling value is derived here [S1]. No performance figure, no availability figure and no ranking appears in this article [S1]. No hedged wording is attached to any price: each figure above is either printed on the page or absent from it [S1]. Describing the pricing mechanism is the whole scope of this page; it is not an evaluation of the service, its speed, its support or its record [S1].
The three candidates in the question turn out to occupy three different slots [S1]. A configuration selects the row, an hour supplies the meter, and a month supplies a column that some families print and others do not [S1]. Asking which one is the billing model assumes they compete, when the page shows them nested [S1].
For a reader holding one plan row, the practical result is a short quote: the bundle, the hourly figure, the monthly figure if printed, the row qualifier, and the date of the read [S1]. That quote is reproducible by someone else opening the same page, which is more than a rounded estimate can offer [S1]. Anything beyond it needs a source that states the conversion, and I did not find one today [S1][S4].
The pricing page prints an hourly column on every compute table I read, and a monthly column on the Cloud Compute tables [S1]. Its VX1 section charges by the hours run in a month and names 672 hours as a ceiling that does not bind those instances [S1]. So the hour is the meter throughout, while the printed monthly column is not universal [S1].
The readable tables give no separate money column for any of those components [S1]. Each row binds vCPU count, memory, bandwidth and storage to one set of figures, so the row is the priced unit [S1]. Two families can print the same vCPU count and memory size with different money figures [S1].
The page prints both figures on the Cloud Compute tables but states no hour count, rounding rule or formula linking them [S1]. A separate official endpoint returned different hourly values for several of those rows on 2026-11-11 [S2]. I derive no conversion here and quote only the figures printed on the pricing page [S1][S2].
Source status below is as observed on 2026-11-11; two channels were used and are kept apart [S1][U1].