Basic Regular plans: the price you are comparing
This table covers the Regular CPU option under Basic Droplets. Premium CPUs, v5 configurations and GPU plans are outside its scope. Monthly figures are published bundled-plan caps; hourly figures are the displayed rates, not prices calculated by dividing the cap.
| Memory | vCPU | SSD | Included transfer | USD/hour | USD/month cap |
|---|---|---|---|---|---|
| 512 MiB | 1 vCPU | 10 GiB | 500 GiB | $0.00595 | $4.00 |
| 1 GiB | 1 vCPU | 25 GiB | 1,000 GiB | $0.00893 | $6.00 |
| 2 GiB | 1 vCPU | 50 GiB | 2,000 GiB | $0.01786 | $12.00 |
| 2 GiB | 2 vCPUs | 60 GiB | 3,000 GiB | $0.02679 | $18.00 |
| 4 GiB | 2 vCPUs | 80 GiB | 4,000 GiB | $0.03571 | $24.00 |
| 8 GiB | 4 vCPUs | 160 GiB | 5,000 GiB | $0.07143 | $48.00 |
| 16 GiB | 8 vCPUs | 320 GiB | 6,000 GiB | $0.14286 | $96.00 |
Data from the DigitalOcean official pricing page, Basic Droplets → Regular, columns Memory, vCPU, Transfer, SSD, $/hr and $/mo. Checked . Read across one row; do not mix CPU tabs.
Backup options are separate from the compute cap
Percentage-based basic backups add 20% for weekly backups or 30% for daily backups. On a full-month $6 Droplet, our arithmetic is $6 × 20% = $1.20 extra for weekly backups, or $6 × 30% = $1.80 extra for daily backups. These are alternatives, not fees to add together. Usage-based backup plans have a different mechanism and are not estimated here. Source: Additional product pricing → Backups, weekly and daily entries; checked 2026-11-13 02:10 UTC.
Year one versus year two: separate a model from a renewal quote
Our scenario keeps one 1 GiB Basic Regular Droplet for twelve full billed months in each year. It excludes credits, taxes, backups and retained resources, and assumes the currently observed $6 monthly cap remains unchanged. It is a budgeting model, not a promise about next year's rate.
Year one: 12 × $6 = $72. Year two: 12 × $6 = $72. Modelled difference: $72 − $72 = $0. A separately guaranteed renewal-year tariff was Not obtained. Do not label the $6 list rate a first-year promotion, or treat the $0 modelled difference as a guaranteed renewal discount.
For a different future monthly rate R, the same model becomes year two = 12 × R and the increase over year one = 12 × (R − $6). R is deliberately left unknown. If checkout applies an account credit, record it separately from the recurring rate rather than reducing the base price in this table.
Rate evidence: Basic Regular table, 1 GiB row, $/mo cell. Billing evidence: Bundled CPU Droplet Billing, paragraphs 1–2. Quantities and unchanged-rate assumption are ours.
Extra transfer and storage: work out the resource subtotal
For this scenario, the team's actual outbound usage exceeds its accrued pooled allowance by 100 GiB. Separately, one 50 GiB Standard block volume exists for the full billing month. Those quantities are assumptions; they are not included benefits or measured usage.
Transfer overage = 100 GiB × $0.01/GiB = $1. Standard volume = 50 GiB × $0.10/GiB-month = $5. Resource subtotal = $6 + $1 + $5 = $12. This excludes tax, backups and snapshots. Extra block storage is a separate volume; it does not increase the plan's RAM or CPU. There is no claim here that a boot disk can silently overflow into paid capacity.
The threshold matters: use max(0, team outbound GiB − accrued team allowance GiB), not one Droplet's traffic minus its advertised full-month allowance. The billing documentation accrues allowance as a Droplet exists and pools it across the team. A short-lived Droplet therefore needs a prorated allowance check before this example can be reused.
Evidence: Bandwidth Billing → Droplets, paragraphs 1–2; Details and Examples, paragraph 1; Volume Pricing, first pricing paragraph and attachment statement. A separate automatic boot-disk overage tariff was Not obtained; no such charge is assumed.
Off, destroyed, or fully cleaned up: follow the surviving resources
Hold a 1 GiB Droplet, a 50 GiB Standard volume and one 20 GB Droplet snapshot for a complete billing month. Here 20 GB is assumed billable snapshot size, not the capacity of the source disk. Keep GB and GiB as the provider labels them.
| State for the modelled month | Droplet | Volume | Snapshot | Resource subtotal |
|---|---|---|---|---|
| Powered off; all resources kept | $6 | 50 × $0.10 = $5 | 20 × $0.06 = $1.20 | $12.20 |
| Droplet already destroyed; volume and snapshot kept | No further Droplet charge | 50 × $0.10 = $5 | 20 × $0.06 = $1.20 | $6.20 |
| All three resources already deleted | No further charge | No further charge | No further charge | $0 for these resources going forward |
Data from DigitalOcean official documentation, checked 2026-11-13 02:10 UTC. Published rates: Basic Regular table, 1 GiB monthly cell; Volume Pricing, pricing paragraph; Snapshots Pricing, pricing paragraph. Every subtotal is our calculation, not an invoice.
The second row models a later full month, not the month containing deletion. Already accrued charges still have to be paid. Deleting a Droplet is irreversible and is not the same as shutting down its operating system. Its associated resources are not deleted by default; choose what to retain and inspect those resources separately. Automatic backups have different retention rules and are outside this snapshot example.
State evidence: Bundled CPU Droplet Billing, paragraph 2; Destroy a Droplet from the Control Panel, associated-resource selection and final billing paragraph; Volume Pricing, duration and attachment statements.
A dated snapshot-copy change to include in next year's budget
The official Snapshots Pricing note says that, beginning 1 January 2027, additional-region copies of a Droplet snapshot are charged at the original snapshot rate. This is a published future rule, not a prediction that all Droplet prices will rise.
Scenario: one original 20 GB snapshot and one additional-region copy, each assumed to have 20 GB billable size, held for a complete billed month after that date. (20 + 20) GB × $0.06/GB-month = $2.40/month. The original alone is 20 × $0.06 = $1.20; the extra copy adds $1.20/month, or $14.40 over twelve complete months at the quoted rate. These assumed sizes are not a promise about actual incremental storage.
Evidence: Snapshots Pricing, first pricing paragraph and Note beginning “Beginning on 1 January 2027”. Very small or short-lived snapshots can incur the documented minimum charge; this full-month example is not a proration calculator.
Who should use this price table?
Use it when a bundled Regular CPU shape fits your workload and you want to inspect a monthly compute cap plus separately billed resources. For a storage-heavy workload, price the volume and transfer before selecting the smallest Droplet. If you need managed application administration, guaranteed dedicated CPU performance, or a custom v5 shape, this table alone does not answer that purchase decision.
What was not obtained
- Guaranteed year-two or renewal tariff: Not obtained; only an explicitly unchanged-rate scenario is shown.
- Account-specific credits and tax-inclusive checkout total: Not obtained; neither is subtracted from or added to the base table.
- Automatic boot-disk overage unit price: Not obtained; the storage calculation uses a separately provisioned Standard volume.
- Application-specific backup storage usage: Not obtained; it is not guessed from the boot-disk capacity.
Sources and check date
Official pages checked . These are dated observations, not live checkout quotes. The three worked budgets above use labelled assumed quantities. No competitor supplies a price or billing rule on this page.