Short answer: A virtual server rental is charged against the configuration you select, metered per second against an hourly rate, with a floor set at the greater of 60 seconds and $0.01 [S1][S2]. Neither of the two pages opened on 2026-11-12 prints a fixed rental term; the span is written as a boundary, with the charge opening at creation and closing at destruction [S2]. One line under the Bundled CPU Droplet Billing heading caps bundled usage at 672 hours (28 days) in a month, which is a ceiling on the meter rather than a commitment to hire for that long [S2]. The exit is the closing line of that same section, directing the reader to destroy the instance to halt the charge [S2]. The pricing page FAQ asks how to destroy resources and answers a separate refund question with a refusal [S1]. I quote only figures printed on the two pages opened today, derive no conversion between the hourly and the monthly columns, and keep this page on that single question [S1][S2].
The pricing page opens a table whose money columns are headed $/hr and $/mo [S1]. Each line of that table binds memory, vCPU count, transfer allowance and SSD size to one pair of figures [S1]. The table has no standalone line that sells one gigabyte of RAM [S1].
Three rows from that table follow, and the last column names the source for each [S1]:
| Memory | vCPU | Transfer | SSD | Hourly column | Monthly column | Source |
|---|---|---|---|---|---|---|
| 512 MiB | 1 | 500 GiB | 10 GiB | $0.00595 | $4.00 | [S1] |
| 2 GiB | 2 | 3,000 GiB | 60 GiB | $0.02679 | $18.00 | [S1] |
| 16 GiB | 8 | 6,000 GiB | 320 GiB | $0.14286 | $96.00 | [S1] |
A reader who selects the first of those rows is selecting a bundle, not a quantity of RAM plus a quantity of cores [S1]. In the v5 section those three resources are chosen separately instead of arriving as one fixed bundle [S1]. The documentation page says plainly that pricing depends on the configuration type, which is why the two layouts print their figures differently [S2].
That difference matters for the question this page answers. A bundle carries one pair of money figures for the whole row [S1]. A separately configured instance carries a rate for each resource that contributes to its total [S2]. Neither layout prints a line that charges for the act of renting itself [S1][S2].
For the separately configured family, the documentation prints an hourly rate for each resource and describes the instance total as a sum of the resources selected [S2]. Those four rates are copied here with their source in the last cell [S2]:
| Resource | Printed rate | Source |
|---|---|---|
| Shared vCPU, per vCPU | $0.0158219/hour | [S2] |
| General Purpose vCPU, per vCPU | $0.028/hour | [S2] |
| Memory, per GiB | $0.0040411/hour | [S2] |
| Boot disk, per GiB | $0.000137/hour | [S2] |
Both readable pages give the per-second meter the same floor, fixed at the larger of 60 seconds and $0.01 [S1][S2]. The pricing page dates its per-second change to January 1, 2026 [S1]. A rental that ends almost as soon as it begins still leaves a charge, because the documentation says the minimum applies even when an instance is destroyed inside 60 seconds [S2].
I copy the two money columns as separate printed values and do not turn either one into the other [S1]. No hour count, rounding instruction or linking rule appears beside those columns on the page [S1]. Supplying one from arithmetic would produce a figure the page never printed, which is an estimate rather than a quote [S1].
The question of how long the hire lasts has no dedicated answer line on either readable page [S1][S2]. I looked for a minimum term, a fixed contract length and a notice period for ending a CPU rental, and none of the three is stated [S1][S2]. The word contract does appear in the documentation, but only inside a GPU section whose price cells read Per contract after contacting sales, which is a different product [S2].
What the documentation prints instead is a boundary [S2]. In the section headed Bundled CPU Droplet Billing, the second paragraph sets the start of the charge at creation and its finish at destruction [S2]. That sentence is the nearest thing to a term on the page, because it defines a span by two endpoints instead of naming a duration [S2].
The paragraph just above it prints a monthly ceiling of 672 hours (28 days) for bundled usage [S2]. A ceiling limits how much usage can be charged inside a month; it does not oblige anyone to keep the machine for that span [S2]. Reading the ceiling as a minimum rental period would reverse what the line says [S2].
For separately configured instances the same documentation states that no monthly usage cap applies, and that a continuously running instance produces a total that moves with the hour count of that month [S2]. So the span sits in two places: the ceiling line for bundled rows, and the start-and-finish line directly beneath it [S2]. Neither line asks the reader to commit to a set number of weeks [S2].
On the pricing page, the FAQ contains a question that asks how to destroy resources, and its answer points the reader toward the documentation [S1]. A neighbouring question asks whether a refund is available; the answer reads "We do not offer refunds." [S1]. Those two FAQ entries are the pricing page's own contribution to the end-of-rental question [S1].
The documentation is more explicit [S2]. Under the same Bundled CPU Droplet Billing heading, the closing line of that paragraph directs the reader to destroy the instance in order to halt the charge [S2]. The same paragraph adds that switching a bundled instance off does not release its reserved compute capacity on the host [S2]. The printed exit is therefore a deletion, not a power state and not a date on a calendar [S2].
I found no line on either page requiring advance notice before that deletion, and no line offering money back for time left unused [S1][S2]. Where a policy is missing from the readable pages, this article records the gap instead of supplying one [S1][S2].
The figures here cover rental terms and exit clauses; for the part that follows, the dedicated server hosting page compares dedicated hardware with virtual plans on published specs.
If you came here for rental terms and exit clauses, the cheap Windows VM page shows which Windows plans are licensed and which expect your own key.
A third provider's pricing address returned HTTP 403 with an access-denied body, so it contributes no figure here [U1]. A legal terms address at another provider produced a challenge screen [U2], and a documentation path for closing an account came back with a missing-page response [U3]. Neither of those two supplies a line to this page [U2][U3].
No fixed rental term, no notice period and no conversion rule is derived or supplied here [S1][S2]. The two money columns are quoted as printed; nothing on this page multiplies an hourly figure by an hour count or divides a monthly figure [S1]. Speed measurements, service-level claims, league tables and support opinions sit outside the scope of this page [S1][S2].
The job of this page ends where the two printed lines end; I do not rate the product or recommend a plan [S1][S2]. Describing the charge unit and the location of the term and exit lines is the whole assignment [S1][S2].
Three slots are easy to conflate when asking what a rental costs: the thing priced, the meter that runs against it, and the span during which the meter runs [S1][S2]. The thing priced is the configuration; the meter is per-second time against an hourly rate; the span is the interval between creation and destruction [S1][S2]. A monthly figure printed beside an hourly figure is a column on the table, not a fixed length of hire [S1].
For a reader holding one quote, the useful record is short: the row, both printed columns, the floor, the ceiling line and the heading under which the exit instruction sits [S1][S2]. Someone else opening the same two pages on the same date can reproduce that record [S1][S2]. Anything framed as a minimum rental period needs its own printed line, and no such line surfaced in today's read [S1][S2].
The two pages opened on 2026-11-12 print no minimum term and no fixed contract length [S1][S2]. The documentation caps bundled usage at 672 hours (28 days) in a month and defines the charge span by creation and destruction [S2]. A ceiling on usage is not a commitment to keep the machine for that span [S2].
The documentation section headed Bundled CPU Droplet Billing closes with an instruction to destroy the instance to halt the charge [S2]. The pricing page FAQ asks how to destroy resources and answers a refund question with a refusal [S1]. Switching the machine off is not the action those lines name [S2].
The Basic Droplets table prints a $/hr column and a $/mo column on the same rows [S1]. Neither page supplies the arithmetic that would tie the two columns together [S1][S2]. I quote each column as printed and derive no conversion from them [S1].
Source status below is as observed on 2026-11-12; two direct channels and three blocked or missing addresses are kept apart [S1][S2][U1][U2][U3].