DigitalOcean Basic 512 MiB: Per-Second Billing, 1 vCPU

Plan details (official data)

Inclusions and features (official data)

• Flat monthly price (no intro discount)

Prices were checked on DigitalOcean's official pricing page on Oct 1, 2026. The renewal price listed there is the same as the sign-up price (no intro discount). Prices change, so confirm on the official site before you buy.

Compare plans in this category (official data)

Swipe the table to see more →

All values in this table come from each host's official pricing page. This plan was checked on Oct 1, 2026; every compared plan was checked within the last 60 days.

What the official data lists for this plan

The pricing page lists four resources for DigitalOcean Basic 512 MiB: 1 vCPU, 512 MiB of RAM, 10 GiB SSD storage and 500 GiB of bandwidth. The category is Cloud VPS, which means a self-managed server: the provider supplies the virtual machine, and the operating system, web server, runtime, database and security are configured and maintained by the person who signs up.

The only feature named in the data is a flat monthly price with no intro discount. The data does not list server locations, available operating system images, backup or snapshot options, IPv6 availability, support channels or uptime figures, so none of those can be confirmed from this page. Anyone who needs a specific region or a managed backup product should verify those details with DigitalOcean before paying.

How billing works: per second, up to a monthly cap

The billing field reads: USD per month; billed per second up to the monthly price (capped at 672 hours a month). In practice, the charge for a Droplet builds up second by second, and once the Droplet has accrued 672 hours in a month, the charge for that month stops rising and equals the monthly price shown in the table. The listed term of 1 month is the billing cycle for that monthly cap, not a period the reader is signed up for.

Because the features field says flat monthly price while the billing field says per second, the billing field is the one to read literally: the monthly price is the most a single Droplet of this size can cost in a month, not an identical charge that posts every month regardless of use. The data does not say what happens to charges when a Droplet is powered off, so do not assume that stopping it reduces the bill; check the provider's billing documentation for that.

The renewal price is the same as the first-term price, so there is no intro discount that ends later. The price table on this page shows the verified monthly figure.

Matching 1 vCPU, 512 MiB and 10 GiB to a web app

Memory is usually the first limit a developer hits on this size. 512 MiB has to hold the kernel, the web server, the application runtime and anything else running on the box. A single lightweight process, such as a small Node, Go or Python service behind Nginx, or a static site generator's output, is the kind of workload that fits. Running an application server and a database engine on the same 512 MiB Droplet leaves little headroom, and memory-heavy build steps are better run elsewhere and deployed as artifacts.

1 vCPU means requests are handled on a single core. That is adequate for low-concurrency apps, API endpoints that mostly wait on I/O, cron jobs, webhooks and staging environments. CPU-bound work such as image processing, compiling on the server or serving many simultaneous dynamic requests will queue behind that one core.

10 GiB SSD covers the operating system, the app code and logs for a small project, but it is tight once a database grows, uploads accumulate or package caches are left in place. Log rotation and keeping user uploads in object storage are the usual ways to stay inside 10 GiB.

500 GiB of transfer is generous relative to the compute size. A small app serving HTML, JSON and modest assets rarely approaches it; large downloads or video delivery would, and those workloads are a poor match for this size for memory reasons as well. The data does not say how overage beyond 500 GiB is charged, so confirm that with DigitalOcean if the app serves large files.

Resizing later and what the data does not confirm

For a developer who expects an app to grow, the practical question is whether to start small and move up. The official data for this page does not describe a resize feature, whether a resize requires downtime, or whether storage can be grown separately from CPU and memory. Those are questions to confirm in DigitalOcean's documentation before building a growth plan around them.

What the data does show is the next size in the same product line: DigitalOcean Basic 1 GiB, with 1 vCPU, 1 GiB of RAM, 25 GiB SSD and 1,000 GiB of transfer, billed the same way per second up to its own monthly price. If the app is already near 512 MiB in local testing, starting on the 1 GiB size avoids a migration soon after launch. If the app is small and the budget matters more than headroom, the 512 MiB size is the lower-cost starting point, and keeping the deployment reproducible (a script or image that rebuilds the server from scratch) makes a later move to a larger Droplet a matter of redeploying rather than hand-migrating.

How it compares with the other small cloud VPS plans

Vultr Cloud Compute 0.5 GB is the closest match in the data: 1 vCPU, 0.5 GB of RAM, 10 GB SSD and 0.5 TB of bandwidth, billed in USD per month and billed hourly up to the monthly price, with a flat monthly price and no intro discount. Its features field describes it as Regular Performance (previous-gen Intel, regular SSD). The main differences visible in the data are the billing granularity (hourly at Vultr versus per second at DigitalOcean) and the fact that Vultr names its CPU generation and disk type while the DigitalOcean data does not. Because the two providers list sizes in different units (GB and TB versus GiB), this page does not rank them as larger or smaller.

Vultr Cloud Compute 1 GB steps up to 1 GB of RAM, 25 GB SSD and 1 TB of bandwidth on the same Regular Performance hardware and the same hourly billing up to the monthly price. It is the Vultr counterpart to DigitalOcean Basic 1 GiB for anyone whose app needs more than half a gigabyte of memory from the start.

Vultr High Frequency 1 GB is the only plan in the set that names faster hardware: High Frequency (3GHz+ Intel Xeon, NVMe SSD), with 1 vCPU, 1 GB of RAM, 32 GB NVMe SSD and 1 TB of bandwidth, also billed hourly up to the monthly price. A developer whose app is limited by single-core speed or disk latency rather than memory may prefer it; a developer who mostly needs a cheap always-on endpoint for a small service may not need it.

None of these plans lists an intro discount, and all four alternatives show a 1 month term with the renewal price the same as the first-term price. The choice therefore comes down to memory and storage needs, whether named hardware matters, and preference between per-second and hourly accrual. The price table on this page shows the verified monthly cap for each.

What to check before signing up

Confirm the memory budget of the full stack, not just the app process. If the sum of web server, runtime and database is close to 512 MiB, the 1 GiB size is the safer starting point.

Confirm with DigitalOcean the details the official data leaves open: available regions, operating system images, backup and snapshot options, how transfer beyond 500 GiB is charged, and how a Droplet can be resized or how charges behave when it is powered off. Because the plan is self-managed, assume that patching, firewalling and backups are the operator's responsibility unless the provider documents otherwise.

Read the billing field as written: charges accrue per second and stop rising at the monthly price once 672 hours are reached in a month. The monthly price in the table is the cap, and the renewal price is the same as the first-term price.