Linode pricing

Our steady-workload scenario holds one Nanode, its instance-backup add-on, and a separately allocated 40 GB volume for twelve complete billed months. The monthly resource budget is $5 + $2 + (40 × $0.10) = $11. Year one = 12 × $11 = $132. At unchanged rates and resources, year two = $132, so the modelled difference is $0. Quantities and the unchanged-rate assumption are ours. This is neither a discounted first-year quote nor a guaranteed renewal tariff; a guaranteed future tariff was Not obtained.

A prepayment changes account balance, not the number of resource-months in this model. The official Billing FAQ says advance funds become a positive balance applied to later invoices. Do not count a deposit as an additional annual service fee, and do not assume it buys a renewal discount.

The $2 backup add-on does not protect the 40 GB Block Storage volume. The official Block Storage documentation explicitly excludes volumes from the instance Backups Service. Our $132 budget therefore covers the listed services, not a complete backup design for every byte. The cost of a separate volume-backup destination was Not obtained and is not invented.

Evidence: the official compute and backup cells above; Block Storage pricing, opening rate sentence and North America 40 GB row; Billing FAQ → Can I make a payment in advance?, paragraph 1; Block Storage → Limits and considerations, final backup-exclusion paragraph.

Akamai's billing guide says compute network transfer and Block Storage use binary units despite the GB/TB labels: one billed TB contains 1,024 billed GB. Preserve those labels when reconciling the provider's invoice; do not silently substitute decimal terabytes.

Our scenario uses two full-month Nanodes in the same eligible transfer pool, both at the checked North America rate. Each contributes 1 TB. Their assumed outbound usage is 1,300 GB and 900 GB. Pool allowance = 2 × 1,024 = 2,048 GB. Usage = 1,300 + 900 = 2,200 GB. Overage = max(0, 2,200 − 2,048) × $0.005 = $0.76. A separate full-month 40 GB volume costs 40 × $0.10 = $4. With two $5 Nanodes, the resource subtotal is $10 + $4 + $0.76 = $14.76, excluding backups and tax.

This does not mean every instance worldwide shares one allowance. The network-transfer document distinguishes the global pool, region-specific pools and distributed regions. Confirm the actual pool in Cloud Manager; a contribution to another pool cannot offset this example. Short-lived services also contribute a prorated allowance, so the full-month assumption is necessary.

Evidence: Shared CPU → North America, Nanode Transfer cell and following egress-overage sentence; Network transfer usage and costs → Transfer allowance, pooling and proration paragraphs; Billing → GB vs GiB conversion of bytes, paragraph 1. Traffic quantities are our scenario, not measured usage.

For a later complete billed month, model a Nanode and a 40 GB volume with no backup add-on, no transfer overage and no other resources. Powered off but retained: $5 + $4 = $9. Nanode already deleted, volume retained: $4. Both resources already deleted: no further charge for these two resources. The retained volume alone is $4 × 12 = $48 over twelve complete months at the checked rate. A shutdown button therefore does not accomplish the same budget change as deleting the services.

Amounts already accrued before deletion still appear on the later invoice. The volume documentation says volume data persists after deleting its attached Linode; the Billing FAQ says inactive services remain chargeable until deleted. These statements establish the separate cleanup check. They do not promise a refund for elapsed time or describe the deletion policy of every optional service.

Evidence: Billing FAQ → I'm not using services but I'm still being charged, paragraph 1; I deleted a service earlier this month, paragraph 1; Block Storage → Resilient and fault tolerant, paragraph 1; North America 40 GB monthly row.

For a Nanode that exists for 24 hours and one minute, our billable-time calculation is ceil(24 + 1/60) = 25 hours. At the displayed $0.0075/hour, the unrounded arithmetic result is 25 × $0.0075 = $0.1875, below the $5 monthly cap. Exactly 24 hours gives 24 × $0.0075 = $0.18. The extra partial hour adds $0.0075 before invoice rounding. We have not obtained the account's final currency-rounding result, so $0.1875 is a formula result, not a claim about a four-decimal invoice.

Evidence: Billing → Understand how billing works, service-accrual paragraph: usage is rounded up to the nearest hour; Nanode $/Hr and $/Mo cells. The runtime is our assumed job duration. A job's transfer allowance must be prorated separately.