DigitalOcean Basic 16 GiB: Per-Second Billing, 8 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 15, 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 15, 2026; every compared plan was checked within the last 60 days.

What the official listing shows

The resources listed for DigitalOcean Basic 16 GiB are 8 vCPU, 16 GiB RAM, 320 GiB SSD and 6,000 GiB bandwidth. For a developer, that is enough room to run an application server, a database and a background worker on the same machine, keep logs and database files on local SSD storage, and serve API traffic without thinking much about the monthly transfer allowance for a small project.

The category is Cloud VPS, which means a self-managed server. DigitalOcean provides the virtual machine; installing the runtime, web server, database, firewall rules and backup jobs is your job. The only feature in the listing is Flat monthly price (no intro discount), and the term is 1 month. There is no mention of a managed stack, a control panel or a managed database, so plan to administer the server over SSH from the first login.

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 this means charges build up by the second while the server exists, and they stop growing once they reach the monthly price shown in the price table. The listing expresses that ceiling as 672 hours a month. The 1 month term is the billing cycle of that cap, not a commitment: it describes how often the cap resets, not a period you are signing up for.

The feature Flat monthly price (no intro discount) together with the renewal information means the cap is the same at renewal as it was at the start. There is no introductory rate that later changes. Because billing is per second, what you actually pay in a given cycle is the accumulated per-second usage up to that cap rather than a single fixed charge.

The official data does not say what starts, pauses or lowers charges beyond the per-second accrual and the cap. It does not state how a powered-off server is charged, or whether destroying a server ends charges. If you intend to spin servers up and down for short experiments, confirm with DigitalOcean how those situations are billed before relying on that approach to keep costs low.

Who this plan suits

This plan fits a developer who wants a single server with headroom: a side project that has grown past a tiny instance, an API that runs a database and a queue alongside the app, or a staging and production pair of containers on one host. 8 vCPU and 16 GiB RAM leave space to run several services at once without squeezing memory, and 320 GiB SSD gives room for database growth, build artifacts and local backup archives before they are shipped off the server.

It is less suited to someone who wants the provider to patch, monitor and back up the machine for them. Nothing in the listing points to managed operations, and the per-second billing model rewards people who are comfortable creating, configuring and tearing down servers themselves. If your project is small enough that the resources above are more than you expect to use, the DigitalOcean Basic 8 GiB alternative described below uses the same billing wording with smaller listed resources.

What a self-managed server needs: SSH, updates, a firewall and backups

SSH access: as a self-managed Cloud VPS, this server is administered over SSH. The usual approach is to log in with a key pair rather than a password, create a non-root account with sudo rights for daily work, and then turn off password authentication and direct root login in the SSH daemon configuration. Keep a second key on another device so a lost laptop does not lock you out.

Updates: a server that faces the internet needs security patches applied without you remembering to do it. Enable your distribution's automatic security updates, schedule a reboot window for kernel updates, and keep the application's own dependencies pinned and updated through your deployment pipeline rather than by hand on the box.

Firewall: run a host firewall on the server itself and allow only what the project needs, typically SSH for administration and HTTP and HTTPS for the site or API. Everything else, including the database and any internal queue, should listen only on localhost or a private interface. If your API is only consumed by a front end you control, consider restricting access further at the application layer.

Backups: the official data for this plan does not mention provider-side backups, snapshots, a cloud firewall, monitoring, available operating system images, data center locations or support, so check those on the provider's site before signing up, and plan to handle backups yourself on the server either way. Dump the database on a schedule, copy the dump and the application files to storage outside this server, and actually test a restore on a fresh machine so you know the procedure works before you need it.

Alternatives in the same category

DigitalOcean Basic 8 GiB is the closest comparison because it uses the same billing wording, USD per month; billed per second up to the monthly price (capped at 672 hours a month), the same 1 month cycle, the same feature of a flat monthly price (no intro discount) and the same renewal position. It lists 4 vCPU, 8 GiB RAM, 160 GiB SSD and 5,000 GiB bandwidth. Because the units match, a direct comparison is fair: the 16 GiB plan lists more of each resource. A side project that runs a single app and a small database may be fine on the 8 GiB plan; one that runs several services, a memory-hungry database or heavier background jobs is the case for the 16 GiB plan.

Vultr lists three plans in this category, each with a 1 month cycle, a flat monthly price (no intro discount) and the same renewal price, but billed in its own words: USD per month; billed hourly up to the monthly price. Vultr High Frequency 8 GB / 3 vCPU carries the feature High Frequency (3GHz+ Intel Xeon, NVMe SSD) and lists 3 vCPU, 8 GB RAM, 256 GB NVMe SSD and 4 TB bandwidth. Vultr High Performance AMD 8 GB / 4 vCPU carries the feature High Performance (AMD EPYC, NVMe SSD) and lists 4 vCPU, 8 GB RAM, 180 GB NVMe SSD and 6 TB bandwidth. Vultr Cloud Compute 16 GB / 6 vCPU carries the feature Regular Performance (previous-gen Intel, regular SSD) and lists 6 vCPU, 16 GB RAM, 320 GB SSD and 5 TB bandwidth.

Vultr's figures are written in GB and TB while DigitalOcean's are written in GiB, so the storage and bandwidth numbers should not be treated as equal or ranked against each other. What the Vultr listings add is a description of the hardware class (CPU family and NVMe versus regular SSD), which the DigitalOcean listing does not provide. A developer whose API is bound by single-threaded CPU work may want to read the Vultr High Frequency feature wording closely; one who wants the largest listed vCPU count among these options with per-second rather than hourly accrual will look at DigitalOcean Basic 16 GiB; one who wants the same 16 GB memory class with a described hardware generation will look at Vultr Cloud Compute 16 GB / 6 vCPU. Which fits depends on the workload, not on a single winner.

What to check before signing up

Read the monthly price in the table and treat it as the cap on per-second charges for each 1 month cycle. Since the renewal price is the same as the intro price, there is no later price change to watch for; what varies is only how much of the cap you consume in a cycle.

Confirm with DigitalOcean the items the listing leaves open: how charges behave for stopped or destroyed servers, whether snapshots or automated backups are available for this plan, which regions and operating system images can be chosen, whether IPv6 is assigned, and what happens to traffic beyond the 6,000 GiB bandwidth allowance. None of those are stated in the official data, and each one affects how you design backups, networking and cost control for a self-managed project.